A work order is the record of one maintenance job: what is wrong, where, which trade, how urgent, who was assigned, what happened and what it cost. Reactive repairs, planned services and work awarded from a quote request all use the same kind of record, so one job number tells the whole story.
OpsChase work orders carry the contractor, response times, tracking and proof rules, and a job cannot close until its proof checks pass.
Why multi-site teams care about work orders
When jobs live in email threads, finding out what happened at site 14 last month takes an afternoon of searching. A proper work order answers that in seconds, and lets you compare sites, trades and contractors on the same terms. It is also the unit everything else hangs from: costs, invoices, compliance checks, the asset history and the evidence that the work was done.
What a good work order holds
- A clear description a contractor can act on without ringing the site first.
- The site, the exact location within it and any access or induction notes.
- The trade and priority, which set how quickly the contractor must respond and attend.
- The assigned contractor and every status change with a timestamp.
- The proof required to close, and the proof actually uploaded.
Common work order mistakes
- One fault raised three times by three different people at the same site.
- Descriptions like “fix the thing out the back” that guarantee a wasted first visit.
- Closing jobs when the invoice arrives rather than when the evidence does.
- Splitting a return visit into a new job, so the original fault looks fixed.
- Keeping planned services off the system because they are “just routine”.
How work orders fit contractor tracking
In OpsChase, a work order is raised by site staff or by an operations team triaging requests. It goes to a contractor from your regular list for that site and trade, and tracking runs if they do not confirm or attend in time. Status moves from open through awaiting proof to complete, and each step is recorded. With Assets and planned maintenance switched on, planned services create their own work orders on a schedule and attach to the asset, so the history covers every visit, not just breakdowns.
Where to start
Agree a short set of priorities and what each one means for response and attendance. Write two or three job templates for your most common trades, with the proof each needs. Then ask every site to raise jobs the same way for a month, and look at what is still open at the end of it.
Read CMMS for how work orders build an asset history, and service level agreement (SLA) for setting times.
On OpsChase: one queue for your team and contractors, each job tracked until the work is done, then photos or sign-off. Book a demo — one site or many.
- Can store or unit occupiers raise work orders?
- Requests can start from occupiers or site staff, and your operations team decides what becomes a job and who it goes to.
- Does each company only see its own work orders?
- Yes. Your company’s jobs stay separate from every other operator on the platform, and contractors see only the jobs assigned to them.
- Can one job link to an asset?
- Yes. With Assets & planned maintenance switched on, jobs attach to assets and rooms, so each one adds to that asset’s service history.
- What is the difference between a work order and a request?
- A request is someone reporting a problem. A work order is the job you create from it, with a trade, a priority and a contractor assigned.
- Should planned services be work orders too?
- Yes. A planned visit that never happened looks the same as one that did unless it has its own job, its own tracking and its own proof.
- What happens when a job needs a second visit?
- Keep it on the same work order and record the return visit, for example when parts are on order. The job stays open with a next step rather than closing early.
