Comparison · Field service basics
Work order vs service request: what changes between them?
A request describes a need. A work order authorises and organises the work that will address it.
Published · Updated · 4 min read · By Servenzo Operations Team.
The short answer
A service request captures what a customer, tenant or site says they need. A work order turns an accepted request into controlled work with scope, priority, owner, schedule and completion evidence. Keeping them as two records preserves the original demand, including requests you decline, while letting operations plan the response through work order management.
Service request vs work order, side by side
| Criterion | Service request | Work order |
|---|---|---|
| Purpose | Records a need as the requester described it | Authorises and controls the work performed in response |
| Who creates it | Customer, tenant, site contact or help desk | Operations, dispatch or a maintenance planner |
| Trigger | Something is broken, needed or due | The request is accepted, or a contract schedule falls due |
| Core fields | Requester, site, description, urgency as claimed | Scope, priority, assignee, schedule, materials, cost, evidence |
| Can it be declined | Yes: out of scope, duplicate or not chargeable | No; once raised it is tracked to completion or cancellation |
| Completion | Closed when the requester is answered | Closed when work is done and evidence is attached |
| Who it protects | The requester, by recording what they asked for | You, by proving what was actually authorised and delivered |
Bottom line: Do not collapse the two. The request is your record of demand and the work order is your record of delivery, and the gap between them is where scope disputes, duplicate call-outs and unbilled work are caught.
Conversion is a decision, not a copy action
Accepting a request means someone judged scope, priority, contract coverage and whether it duplicates open work. Recording that decision, including a rejection and its reason, is what makes the history useful six months later, and it is the point where tenant and site requests become schedulable work.
Close the loop with the requester
The person who raised the request rarely sees your work order. Telling them what was done, when and by whom prevents the duplicate request that arrives a week later. If the work is billable, the completion evidence on the work order is what settles the query.
Where the two records meet the schedule
Once a request becomes a work order it needs a date, an owner and a site. That handover is the practical link between intake and field service scheduling: everything before it is demand, everything after it is capacity.
A practical process
- Capture the request in the requester's own words.
- Triage responsibility, priority, access and contract coverage.
- Create the work order with an owner and completion requirement.
- Return the final outcome to the original request record.
Sources and further reading
This article provides operational education, not legal, employment, accounting, safety or regulatory advice. Requirements vary by contract, industry and jurisdiction.
Questions about work order vs service request: what changes between them?
Can a service request be rejected?
Yes. It may be outside scope, duplicated, missing information or the responsibility of another party. Record the reason and communicate it to the requester.
Can one request create multiple work orders?
Yes. A complex issue may need separate trades, visits or approvals. Keep each work order linked to the same request so the overall outcome remains understandable.
Should a work order include cost?
Include the commercial basis that operations needs, such as an approved quote, contract rate or not-to-exceed amount. The exact requirement depends on the business process.