A field service work order defines the job before the visit begins.

The short answer

A clear work order reduces questions by carrying the job context to the assigned visit.

• Use one work order for a defined service outcome, not as a general customer note.
• Keep the work order and field visit related but separate: one defines scope, the other records execution.
• Close the work order only after required visit evidence and follow-up have been reviewed.

Move the job through four explicit decisions.

The state map prevents “scheduled” from meaning “ready” and “visited” from meaning “complete.” Each transition has a practical review question.

• Defined: Is the requested outcome clear? Name the customer, site, asset, service reason, priority and work boundary in language the field team can use. Working output: A job that can be reviewed before scheduling.
• Prepared: Is the visit ready to assign? Add the planned time, expected duration, checklist, asset documents and previous context needed for the work. Working output: A visit package with the required context.
• Assigned: Does one technician own the visit? Confirm the named technician, site access information and any office decision that remains open before arrival. Working output: Clear field responsibility.
• Closed: Does the evidence support completion? Review time, checklist results, findings, actions, photos, confirmation and the final report. Prepare follow-up separately when required. Working output: A completed record or an explicit next action.

Prepare follow-up work from a finding on a fictional pump.

The previous visit is complete, but one finding needs a separate inspection. The new work order keeps that boundary visible.

• The service manager reviews the finding and decides that separate work is required.
• The dispatcher creates a new work order against the same pump instead of editing the completed visit.
• The planned visit carries the previous finding and the approved inspection scope.
• The technician records the new evidence against the follow-up visit.
• Result: The original visit remains complete and unchanged while the follow-up has its own scope, owner and evidence.

Review the work order before assignment.

A dispatcher should be able to answer every item without translating a private message or searching another spreadsheet.

• The customer, site and exact asset are selected.
• The work title states the service outcome in plain operational language.
• Priority and planned visit time reflect an explicit office decision.
• The assigned technician and expected duration are present.
• The correct checklist and relevant asset documents are available.
• Previous findings needed for this job are linked or summarized accurately.
• Site access or customer coordination notes are current.
• The completion evidence and follow-up rule are understood.

Do not use status as a substitute for scope.

Labels such as open, planned and complete help teams sort work, but they do not explain the job. The title, asset, service reason and expected evidence must still stand on their own. Define who may change priority, assignment and planned time. A clear owner prevents silent changes from becoming field surprises.

Preserve the completed record when follow-up appears.

A finding discovered during one visit should remain part of that completed evidence. If it requires more work, prepare a separate work order with its own scope and visit. This keeps the history accurate and makes responsibility visible.