Every building runs on them. A tap is leaking on level four. The car park roller door has stopped halfway. The fire panel threw a fault at 2am. Somewhere between the person who noticed the problem and the person who fixes it sits a work order — and how well that work order is written usually decides whether the job gets done once or three times.
Most building managers have a working sense of what a work order is without ever having had it defined. That is fine until an insurer, a municipal building surveyor or an incoming committee asks you to produce twelve months of maintenance records, and the answer is scattered across an inbox, a WhatsApp thread and a spiral notebook.
The short answer. A work order is a documented instruction to carry out a specific piece of maintenance or repair work. It records what needs doing, who is responsible, when it is due, and what was actually done.
In Australian building and facility management a work order does two jobs at once: it coordinates the job, and it creates the maintenance record that regulators, owners corporations and insurers can ask to see.
A work order is the instruction and the evidence in a single record. It begins when someone authorises work to be done and it closes when that work is verified as complete.
The distinction that matters in practice is between the request and the order. A resident reporting a broken light is making a request. It becomes a work order when someone with authority decides the work will happen, assigns it, and sets a due date. That decision point is where accountability starts — and it is the step most often skipped in buildings still running on email.
A work order that cannot answer these questions six months later is not a record, it is a note. At minimum it should capture:
| Field | Why it matters |
|---|---|
| Unique work order number | The reference everyone quotes — contractor, invoice, committee minutes, insurance claim |
| Asset or location | Which pump, which door, which level. Ties the job to your asset register |
| Description of the fault | What was reported, in the reporter's words, before anyone diagnosed it |
| Priority | Emergency, urgent, routine or scheduled — drives the response clock |
| Raised by and date | Who reported it and when the clock started |
| Assigned to | The trade, contractor or in-house team member responsible |
| Due date or SLA | The commitment being made, and what gets breached if it slips |
| Work performed | What was actually done, by whom, on what date — not what was requested |
| Parts, cost and sign-off | Materials used, cost against budget, and who verified completion |
The last two fields are the ones that get dropped, and they are the ones that matter later. A work order closed without a record of what was performed proves that someone was asked to do something — not that it was done.
These terms get used interchangeably and it causes real problems in reporting. A maintenance request is an input. A work order is a committed job. One building can generate four hundred requests a year that resolve into two hundred and eighty work orders, because duplicates get merged and some requests are declined or referred to a lot owner as their own responsibility.
If your system treats every request as a work order, your completion statistics will look worse than your building is actually performing, and you will not be able to show a committee how much of the workload is being absorbed before it becomes a job.
Most buildings run some version of six stages:
Stage five is where buildings lose the most money. Closing a work order because a contractor said they attended, rather than because someone confirmed the outcome, is how the same fault gets paid for twice in one quarter.
A reactive work order responds to something that has already failed. A preventive one is generated on a schedule before failure — quarterly pump servicing, annual fire equipment testing, six-monthly gutter clearing ahead of storm season.
The ratio between them is the single most useful number a building manager can report. A portfolio running ninety per cent reactive is being managed by whatever breaks next. Shifting that ratio is slow work, and it only happens if preventive tasks are raised as real, assignable, trackable work orders rather than living in someone's calendar.
This is the part that separates building management from generic maintenance work, and it is where the definition stops being academic.
In New South Wales, AS 1851-2012 became mandatory on 13 February 2026 under the Environmental Planning and Assessment (Development Certification and Fire Safety) Regulation 2021, covering class 1b and class 2 to class 9 buildings — both new and existing. Building owners, which the guidance explicitly includes owners corporations and strata committees, must ensure essential services are maintained in accordance with the standard. (Building Commission NSW, February 2026)
In Victoria, building owners must keep records of maintenance checks, safety measures and repair work so they can be inspected by a municipal building surveyor or chief officer of the fire brigade, and must produce them on request after 24 hours' notice. Owners must also prepare an Annual Essential Safety Measures Report. (Building and Plumbing Commission Victoria, 2026)
Twenty-four hours. That is the practical test of a maintenance system. If a surveyor asked today for the servicing history on your fire doors, could you produce it tomorrow — with dates, contractor names and sign-offs — without calling three trades and searching an inbox? If the answer is no, the gap is not a filing problem. It is a records problem, and the work order is the record.
The failure modes are consistent across buildings of very different sizes:
Each of these is survivable on its own. Together they are why a building can spend heavily on maintenance for years and still have nothing to show a committee asking what the money bought.
Work order software exists to close the gap between the instruction and the evidence. The useful capabilities are unglamorous: a unique number on every job, a link to the asset register, a due date that is visible to more than one person, a mobile record of what was actually done on site, and a history that survives a change of building manager.
None of that requires a large system. It requires that every job — reactive, preventive, resident-reported or contractor-initiated — enters the same place and leaves a record behind.
Once the basics are in place, these habits keep work orders moving and downtime short.
A documented instruction to carry out a specific maintenance or repair task, recording what needs doing, who is responsible, when it is due, and what was actually completed.
A request is a report of a problem. It becomes a work order once someone with authority commits to the work, assigns it and sets a due date. Not every request becomes a work order.
A unique number, the asset or location, the reported fault, a priority, who raised it and when, who it is assigned to, a due date, a record of the work performed, and cost and sign-off.
Usually the building or facility manager, acting on a resident report, a contractor's finding, a scheduled preventive task, or an inspection defect.
The unique reference for the job. It is what ties the request, the contractor's attendance, the invoice and the maintenance record together.
There is no single national retention period. Requirements vary by state and building class, and in Victoria records must be available to a municipal building surveyor on 24 hours' notice. Check the obligations for your state and building class rather than assuming a default.
See how MYBOS handles work orders. MYBOS raises, assigns, tracks and records every work order against the asset it belongs to — so the maintenance history stays with the building, not with whoever happens to be managing it.