Workflow Template
Work Order Workflow
End-to-end work order workflow covering request intake, asset/location capture, priority-based approval routing, scheduling and assignment, work execution with labour and materials tracking, completion evidence, verification, and closure.
Untracked work orders, missed approvals, and no visibility into job status create costly delays and compliance gaps for operations and facilities teams. This workflow covers the full work order lifecycle — from request intake and priority-based approval routing through scheduling, execution, labour and materials tracking, verification, and closure. Operations managers, maintenance supervisors, and technicians all run their assigned steps directly inside assess.one.
Business Outcomes
- Reduce work order cycle time by eliminating manual handoffs and email chasing
- Ensure every high-priority job gets approved before work begins
- Capture labour and materials costs against each work order at point of execution
- Provide requesters with real-time status updates from open through to closure
- Create a complete audit trail from intake to verified completion for compliance and reporting
Workflow Steps
Steps
- 1Create Work Order Recordcreate record
Creates the work order record and sets initial status to Open.
- 2Set Status to Openupdate record
Sets the work order status to Open upon creation.
- 3Send Confirmation to Requestersend email
Sends an acknowledgement email to the requester with the work order reference.
- 4Route by Priority
Routes high/critical priority work orders for approval; low/medium proceed directly to scheduling.
priority: "Critical"→Request Approvalpriority: "High"→Request ApprovalDefault→Schedule and Assign Work Order - 5Request Approvalrequest approval
Pauses workflow for manager approval on high or critical priority work orders.
- 6Route on Approval Outcome
Routes approved work orders to scheduling; rejected orders are closed with notification.
approval_status: "approved"→Schedule and Assign Work Orderapproval_status: "rejected"→Notify Requester of RejectionDefault→Schedule and Assign Work Order - 7Notify Requester of Rejectionsend email
Sends an email to the requester advising the work order was not approved.
- 8Set Status to Rejectedupdate record
Closes the work order record with a Rejected status.
- 9Schedule and Assign Work Ordercreate task
Planner schedules the work, sets the planned date, and assigns a technician.
- 10Set Status to Scheduledupdate record
Updates the work order status to Scheduled and persists the planned date and technician.
- 11Notify Technician of Assignmentsend email
Sends an email to the requester confirming scheduling; technician is notified via task assignment.
- 12Record Work Performed, Labour and Materialscreate task
Technician records work performed, labour hours, materials used, and uploads completion evidence.
- 13Set Status to In Progress / Pending Verificationupdate record
Updates the work order status to Pending Verification and persists labour and cost data.
- 14Route on Work Status
Routes completed work to verification; partial or unable-to-complete work triggers a rescheduling loop.
technician_work_status: "Completed"→Verify Work and Close Work Ordertechnician_work_status: "Partially Completed - Further Work Required"→Reschedule Incomplete Worktechnician_work_status: "Unable to Complete"→Reschedule Incomplete WorkDefault→Verify Work and Close Work Order - 15Reschedule Incomplete Workrestart from step
Planner reviews the incomplete work report and reschedules for a follow-up visit.
- 16Verify Work and Close Work Orderrequest approval
Supervisor or planner verifies the completed work against the evidence and either closes or rejects for rework.
- 17Route on Verification Outcome
Closes the work order if verified; loops back to rework if rejected.
approval_status: "approved"→Set Status to Completedapproval_status: "rejected"→Return to Technician for ReworkDefault→Set Status to Completed - 18Return to Technician for Reworkrestart from step
Verification failed — restarts from the work execution step so the technician can redo and resubmit.
- 19Set Status to Completedupdate record
Marks the work order as Completed in the record.
- 20Notify Requester of Closuresend email
Sends a closure confirmation email to the requester with a summary of work performed.
Fields
- Requester Name*
- Requester Email*
- Requester Phone
- Asset or Location*
- Asset ID / Tag Number
- Work Type*
- +10 more fields
Forms
Work Order Request
11 fields
Data Views
All Work Orders
work_order_ref, requester_name, asset_location, work_type +6 more
Open & Scheduled Work Orders
work_order_ref, requester_name, asset_location, priority +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Categories
FAQs
How long does it take to get this workflow live?
You can publish the template and run your first live work order in minutes. There is no implementation project, no external software to install, and no developer required. Once published, your team starts submitting and processing work orders immediately inside assess.one.
How do I set up priority-based approval routing?
Approval routing logic is configured directly inside assess.one using the workflow builder. You define which priority levels require approval, which roles or individuals are approvers, and what happens on approval or rejection — all without writing code. Changes to routing rules take effect immediately when you update and republish the workflow.
What do I need to customise before going live?
At minimum, you should configure your priority categories, assign approver roles, and set up technician assignment rules to match your team structure. You can also customise the asset and location capture fields, notification messages, and scheduling logic. All of this is done inside assess.one — no external tools or dev work needed.
Who needs access to run this workflow?
Different steps are assigned to different roles — requesters submit work orders, managers or supervisors handle approvals, schedulers assign jobs, and technicians record work performed and submit completion evidence. Each person only sees and acts on the steps relevant to their role. You configure role assignments inside assess.one when setting up the workflow.
How does the approval step work, and what happens if a work order is rejected?
When a work order reaches the approval step, the designated approver is notified and reviews the request inside assess.one. If approved, the workflow routes automatically to scheduling and assignment. If rejected, the requester is notified with the rejection outcome and the work order status is set to Rejected — creating a clear record of the decision.
How do technicians record labour and materials during execution?
Technicians complete the labour and materials step directly inside assess.one as part of the workflow — logging time, resources used, and any relevant notes against the work order record. This keeps cost and effort data captured at the point of execution rather than entered retrospectively into a separate system.
What happens if work is incomplete or fails verification?
The workflow includes a verification step where a supervisor or designated verifier reviews the completed work and submitted evidence. If the work does not meet the required standard, the workflow routes back to the technician for rework before closure. This loop continues until verification passes, ensuring no work order is closed prematurely.
How are notifications handled for requesters and technicians?
Notifications are configured inside assess.one and trigger automatically at key points — confirmation on submission, rejection notice if not approved, assignment notification to the technician, and closure notification to the requester. You can customise notification content and delivery channels, including email and Slack, within the platform without any third-party development work.
Can I track work order status in real time?
Yes. Status fields update automatically as the workflow progresses — from Open through Scheduled, In Progress, Pending Verification, and Completed or Rejected. This gives operations managers a live view of where every work order sits in the process at any point in time, all within assess.one.
Does this workflow support compliance and audit requirements?
Every step, decision, approval, and status change is recorded inside assess.one, creating a timestamped audit trail for each work order from intake to verified closure. This supports maintenance compliance requirements, internal audits, and any reporting that requires evidence of process adherence.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
