A work order is the operational record for a maintenance task: description, site, trade, priority, assignee, status, timestamps, costs and attachments. Everything auditors care about should hang off this job number — not a thread title. Reactive jobs, PPM instances and RFQ conversions become work orders on the same system.
OpsChase work orders bind preferred assignment, response clocks, chase attempts, proof requirements and eventual invoice hooks. Status is explicit — open, accepted, in progress, awaiting proof, complete — and the job cannot be marked complete until proof checks pass. That prevents “marked done” without evidence.
Raise from site staff or ops triage. Assign trade and contractor. Let chase run. Review proof. Export the history when someone asks what happened last Tuesday at site 14.
Your demo walkthrough can cover RFQ, onboarding and the tradie portal on the same call.
OpsChase turns this into a working flow: chase your preferred contractors to done, require proof before a job closes, and RFQ with compliance onboarding when you need the market. Book a demo to see it on your sites — one location or many.
- Can store or unit occupiers raise work orders?
- Request intake can start from occupier channels; ops controls assignment.
- Does each company only see its own work orders?
- Yes. Your company data stays separate from other operators on the platform; marketplace rules apply when you go to market.
- Can one job link to an asset?
- Yes. Assets, rooms and locations attach for PPM and history.