A building work order template is a reusable form for recording a maintenance, repair, inspection, or improvement task from request through completion. Use the printable template below to capture the problem, location, work scope, priority, access and safety notes, assigned person, materials, and closeout details in one place.
A clear work order helps a building owner, manager, maintenance team, or contractor understand what needs attention and what has been done. It is useful for anything from a dripping tap to a damaged door closer, but it is not a substitute for a detailed project specification when work is extensive or technically complex.
What a Building Work Order Is For
A work order turns a reported need into an actionable, trackable task. A tenant or employee may notice a fault, a caretaker may identify an issue during an inspection, or a manager may schedule preventive maintenance. The form records the request and gives the person responsible enough context to assess and carry it out.
Work orders are especially helpful when a building has multiple rooms, systems, occupants, or people handling maintenance. A note that says “fix the leak” may not tell a technician which room is affected, whether water is still running, or who can provide access. A good order narrows that uncertainty without assuming a cause that has not been confirmed.
Use one order for a defined task or closely connected group of tasks. If a reported ceiling stain leads to a separate plumbing investigation and later ceiling repair, documenting the stages distinctly can make responsibility, approvals, and completion status clearer.
Building Work Order Template
Copy or print this blank form. Leave a field empty if it does not apply, or write not applicable so the next person knows it was considered. Add a page if the scope or work notes need more room.
| Field | Entry |
|---|---|
| Work order number | |
| Date and time reported | |
| Requested by and contact details | |
| Building, floor, room, or asset | |
| Issue or requested work | |
| Observed condition and impact | |
| Priority and reason | |
| Requested completion date | |
| Access arrangements or restrictions | |
| Safety notes or required coordination | |
| Assigned person or team | |
| Work scope and completion criteria | |
| Materials, equipment, or outside support | |
| Approval or authorization, if required | |
| Work started and completed dates | |
| Work performed and findings | |
| Parts used and follow-up needed | |
| Actual time and cost, if tracked | |
| Completed by and review | |
| Requester notified and date |
Short filled-in sample
| Field | Sample entry |
|---|---|
| Work order number | WO-1042 |
| Reported | November 3, 2026, 9:15 a.m. |
| Location | Fictional Pine Court, building B, second-floor kitchen |
| Issue | Water dripping below the sink while the tap is running |
| Priority and reason | Routine; no standing water reported, confirm condition on arrival |
| Access | Contact fictional resident Mina Lee before entry |
| Scope and completion criteria | Inspect source, address authorized repair, test for visible leakage, report any further work needed |
| Closeout | Fictional technician Alex Reed; record date, work performed, parts, and resident notification after completion |
Fields to Include and Why They Matter
Start with identification and location. A unique work order number prevents two requests from being confused, while the reported date and requester details help the team ask follow-up questions. Record the most precise location available: building, floor, room, and, where relevant, an equipment or asset label. A room name alone may be ambiguous in a large property.
Describe what was observed, not just the presumed repair. For example, “water appears at the base of the radiator when the heating is on” is more useful than “replace radiator.” The first statement gives the technician a symptom to verify; the second may prescribe a fix before the cause is known. Include the effect on occupants or building use, such as a room being unavailable or a door not latching.
State the scope and what counts as complete. A request to inspect an entry door could mean checking the latch and reporting the result, or adjusting the door and confirming it closes. Distinguishing those outcomes reduces disagreement. Note materials, access needs, approvals, and any dependencies, but avoid writing technical instructions unless the person preparing the order is qualified to define them.
Finally, include closeout fields. Record what was actually done, what was found, any parts used, whether further work is recommended, and who reviewed or received the update. A blank closeout makes it hard to tell whether a task was completed, deferred, or could not be accessed.
How to Set Priority and Schedule Work
Priority should describe urgency and impact, not simply who asked first. Organizations often use labels such as emergency, urgent, routine, and planned, but the labels have no universal meaning. Define each category locally, including who can assign it and how the team should respond. Do not promise a response time on a template unless the organization has established and can meet that commitment.
Useful considerations include whether there is an immediate safety concern, active damage, loss of an essential building function, effect on occupants, and whether the problem is getting worse. A reported odor, exposed wiring, active leak, or blocked exit may need prompt assessment under the building’s procedures. A cosmetic paint touch-up may be schedulable. The form should capture the reason for a priority so staff can review it rather than relying on a label alone.
Separate urgency from the requested completion date. A requester may prefer work by a certain date, but that preference does not automatically set the maintenance priority. If the task depends on a part, access appointment, or specialist, note the dependency and update the requester when the schedule changes.
A Practical Work Order Workflow
A consistent process keeps requests from disappearing between the report and the repair. The exact workflow varies by building, but a practical sequence is:
- Receive and log: Record the report promptly, assign an identifier, and confirm the exact location and contact route.
- Review and classify: Check for missing information, assess the reported impact, and apply the organization’s priority definitions.
- Authorize and assign: Confirm any required approval, then route the task to a person or team with the appropriate responsibility.
- Plan access and work: Arrange entry, identify coordination needs, and clarify the intended scope and completion criteria.
- Perform and document: Record the work, findings, parts, time, and any issue that prevents completion or changes the scope.
- Review and close: Confirm the stated outcome, flag follow-up tasks, notify the requester, and retain the record according to local procedures.
If inspection reveals a different problem or a larger repair than expected, pause and document the finding. The responsible person can decide whether to revise the scope, seek approval, or create a linked follow-up order. This is more reliable than silently expanding the original task.
Safety, Access, and Coordination
A work order is a coordination record, not a complete safety plan. Use it to flag known hazards, restricted areas, occupant needs, required notifications, or work that may affect other trades or building operations. Examples include a room that must remain available, a noisy task near a quiet area, or a system that needs coordination before being taken out of service. The assigned worker must follow the applicable site procedures and use appropriate expertise for the task.
Do not treat a requester’s description as a safety assessment. If someone reports a potentially immediate hazard, follow the building’s escalation process rather than waiting for routine form processing. Do not include unnecessary personal or sensitive details; record only the information needed to arrange the work and communicate responsibly.
Access instructions should be specific but handled carefully. Note whether an appointment is needed, who will provide entry, and any permitted access window. Avoid distributing keys, entry codes, or other sensitive access information more widely than necessary. If the work affects occupants, state who is responsible for notification and when it should happen.
A work order is an operational record, not a substitute for specialist advice; if a situation raises legal, tax, medical, or financial-planning questions, ask a qualified professional.
Common Problems and How to Avoid Them
Vague descriptions are a frequent source of delay. “Broken light” leaves open whether one lamp is out, a fixture is damaged, or an entire area has lost power. Ask the reporter to describe what they saw, where it happened, when it began, and whether the condition is ongoing. A photo can help when the organization permits it, but it should not replace a clear written location and description.
Another problem is mixing several unrelated requests into one order. Combining a leaking sink, a loose handrail, and a hallway paint repair may make it unclear which item is complete. Split unrelated work into separate records, or use clearly numbered tasks when they genuinely belong to one coordinated job.
Other avoidable issues include:
- No completion criteria: State the observable result expected, such as confirming that a repaired fixture operates, rather than only naming an action.
- Unclear ownership: Record who is assigned and who can approve a scope change.
- Missing updates: Note delays, access failures, and parts dependencies so requesters are not left guessing.
- Closing too early: Distinguish work completed from work inspected, deferred, or awaiting a follow-up.
- Overly rigid forms: Keep essential fields easy to find and allow an explanation when a task does not fit a standard category.
A work order can also become a maintenance history. Consistent location names and asset identifiers help staff recognize recurring issues, but only if entries are accurate. Do not infer a recurring defect from similar wording alone; review the actual observations and history.
Paper, Digital Forms, and Recordkeeping
A printable paper form can work well for a small operation, a site visit, or a task where staff need to write notes by hand. It is easy to carry and does not depend on a device at the point of work. Its limitations are practical: handwriting can be hard to read, pages can be misplaced, and tracking status across many forms takes deliberate filing and review.
A digital form can make it easier to search, route, update, and attach permitted photographs or documents. It still needs clear field names, access controls appropriate to the information, and a process for retaining and finding records. A digital form that is difficult to use on site may produce poorer descriptions than a simple paper form.
Whichever format is used, keep the same core information: identity, location, problem, priority reasoning, assignment, scope, work performed, and outcome. Establish a naming convention for locations and assets, and decide who may edit, approve, or close an order. Follow the organization’s document-retention and privacy practices rather than assuming that every record should be kept indefinitely.
Frequently Asked Questions
What should a building work order include?
Include a request identifier, report date, requester and contact route, precise location, observed issue, impact, priority and reason, access and safety notes, assigned person, scope, completion criteria, and closeout notes. Add approval, parts, time, or cost fields when they are useful to your process.
Is a work order the same as a maintenance request?
Not always. A maintenance request is commonly the initial report of a problem, while a work order is the record used to assess, assign, perform, and close the work. Some organizations use one form for both stages; if so, include fields for status and follow-up so the stages remain clear.
Who should complete the work order?
The person receiving the request can log the initial facts, and a supervisor or coordinator may classify, authorize, and assign it. The person doing the work should record findings and completion details. Local responsibilities differ, so the form should identify who owns each decision.
How do I decide whether a request is urgent?
Use the building’s documented priority definitions and consider immediate hazards, active damage, impact on occupants, and loss of building function. If the report suggests an immediate danger, follow the site’s escalation procedure instead of treating the issue as a routine queue item.
Can one work order cover multiple repairs?
It can cover related tasks that share a location, assignment, and completion plan. For unrelated tasks, separate orders usually make status, responsibility, and closeout easier to follow. If a job expands after inspection, document the change or create a linked order.
Should the template include cost fields?
Include estimated and actual cost fields if the organization tracks them and has a process for entering reliable figures. Keep estimates distinct from final recorded costs, and do not treat a blank field as evidence that the work had no cost.