Work order statuses

A work order moves through a series of statuses as the job progresses. Statuses group into a few fixed stages — reporting, SLAs, and your board columns key off the stage, so the picture stays consistent even after an administrator renames a status or adds their own.

The default statuses

Default status	Stage	What it means
Open	Open	Raised and ready to be picked up. New work orders start here.
Assigned	Open	Given to a technician or vendor, but not yet started.
In progress	In progress	Someone is actively working on it.
Awaiting quote	On hold	Paused until a vendor quote comes back.
On hold	On hold	Paused for another reason — see the hold reason.
Pending approval	On hold	Waiting on a cost approval before work continues.
Resolved	Done	The work is finished; a resolution note is required.
Verified	Done	A manager has checked the completed work.
Closed	Done	Fully wrapped up. Reached only after Verified.
Cancelled	Cancelled	Called off. Used instead of deleting.

An administrator can rename these statuses or add new ones to match how your team works, and can control which roles are allowed to make each move.

Holds

When a job is paused, it carries a hold reason so everyone knows what it is waiting on:

• Awaiting quote — a vendor price is needed.
• Awaiting approval — a cost sign-off is needed.
• Awaiting parts — a part has to arrive first.
• Awaiting access — the team can’t get to the location yet.

Priority

Every work order has a priority: Low, Medium (the default), High, or Urgent. Priority is one of the inputs Belrald Assets uses to order the work technicians see, so reserve Urgent for safety or business-critical faults.

Note

Priority is separate from your board status. A work order can be Urgent and still be On hold — for example, an urgent repair waiting on a part.

Closing out with codes

When you resolve a work order, your workspace may ask you to record close-out codes against each asset:

• Failure code — what went wrong.
• Reason code — why it happened.
• Repair code — what you did to fix it.

These codes build the history that powers reliability reporting over time, so fill them in accurately. An administrator sets which codes are required before a work order can be resolved.

Procedures block resolution

If a work order has a procedure attached, the technician must complete it before the work order can be resolved. This is how you make sure a safety check or inspection actually happens rather than being skipped under time pressure.