A maintenance work order checklist: request to verified closure

At intake: capture enough to act

Keep the reporter’s original description, then add operational detail. A report such as ‘water near the lift’ needs a precise location and triage before it can be assigned. Use your site’s emergency procedure when there is an immediate safety concern; a software queue is not an emergency response.

• Request reference, reported time and source channel
• Property, building, level and exact location
• Asset ID if known, with photos that help locate the issue
• Fault description, affected area and operational impact
• Priority, response expectation and responsible dispatcher

At assignment: make ownership explicit

Name the responsible technician or vendor and the supervisor who will review the outcome. Keep access arrangements, the work scope and approval requirements with the job. If scope changes, record the change instead of silently replacing the original instruction.

• Assigned owner, target date and acknowledgement
• Clear scope and referenced instructions
• Access contact and agreed attendance arrangements
• Required approvals for scope or expenditure
• Checklist and evidence expected at completion

At completion: retain evidence that answers the question

The evidence should show what was found, what was done and whether follow-up is needed. More photos do not automatically mean better evidence: label the relevant area and connect the record to the correct asset.

At closure: separate completion from acceptance

A technician may mark work complete before a supervisor accepts it. Keep those events separate when your workflow requires review. Reopening a job should retain the earlier record and explain what was missing.

Where relevant, update the requester with an appropriate summary. Keep internal costs, staff discussions and other restricted information out of public-facing updates.

During shift or managing-agent handover

Review open work, pending approvals, deferred tasks and repeated faults. A successor should be able to understand the current state without searching through a former colleague’s personal messages.

• Open jobs grouped by property, priority and owner
• Outstanding evidence and acceptance decisions
• Vendor commitments and next attendance dates
• Asset history and related service documents
• A named owner for every unresolved exception

Use the checklist in a Wisbid walkthrough

Bring one anonymised request and its completion record to a demonstration. Ask Wisbid to show intake, assignment, evidence capture and supervisor acceptance using that example. This makes it easier to evaluate the workflow against the way your team actually works.

Common questions