Work order lifecycle in Dynamics 365 Field Service

The work order is the core operational record in Dynamics 365 Field Service. Everything — schedules, technician dispatch, parts consumption, customer billing — revolves around the work order's lifecycle. A clean lifecycle is the difference between a smooth field operation and constant firefighting.

Where work orders originate.

• Manually created by a dispatcher or customer service agent.
• From a case — service escalation creates a related work order.
• From an asset — preventive maintenance schedules generate work orders automatically.
• From IoT alerts — connected device anomalies create work orders.
• From a service agreement — recurring scheduled visits.
• Self-service portal — customer requests via Power Pages.

The work order's source informs its priority, routing, and SLA expectations.

Work order anatomy.

• Work Order Number — unique identifier.
• Service Account / Billing Account — who's served, who's billed.
• Customer Asset — the equipment being serviced.
• Work Order Type — installation, maintenance, repair, inspection.
• Status — system status (Open – Unscheduled, Open – Scheduled, In Progress, Completed, Closed).
• Sub-status — granular reasons.
• Priority — High/Medium/Low.
• Service Territory — geographic assignment.
• Date Window From/To — when work must happen.
• Incident Types — what specifically needs doing.
• Service Tasks — checklist items.
• Products — parts consumed or to be used.
• Services — labour line items.

The lifecycle.

1. Created — work order exists; not yet scheduled.
2. Scheduled — a resource and time slot assigned (manual or auto via Resource Scheduling Optimization).
3. In Progress — technician en route or on site, time tracked.
4. Completed — technician finished; service report generated.
5. Closed - Posted — final review by office; products and services posted to inventory and billing.
6. Invoiced — billing generated.

Some lifecycles compress (no formal "posted" stage); others extend (intermediate "Customer Approval" before posting).

Bookings and scheduling. The link between a work order and a resource is a booking. Bookings have their own status:

• Scheduled — assigned, not started.
• Travelling — technician en route.
• On Site — arrived.
• In Progress — working.
• Completed — finished.

Bookings can be split (technician on site for 4 hours but lunch break in middle) and rescheduled.

Scheduling assistant. Dispatcher uses the Schedule Board to:

• See open work orders requiring scheduling.
• Drag onto resources / time slots.
• Apply constraints (skills, territory, certifications).
• Optimise routes manually or with Resource Scheduling Optimization (RSO).

RSO automates this with ML-based optimisation considering travel, skills, urgency.

Technician execution. Field technicians use the Field Service mobile app:

• See assigned bookings.
• Tap to start travelling; arrive; start work.
• Complete service tasks.
• Capture photos.
• Record parts used and labour.
• Customer signature.
• Submit service report.

The mobile app works offline — bookings sync down, completed data syncs up when connectivity returns.

Service reports. A summary of the work performed, parts used, time spent, customer signature. Emailed to the customer; saved on the work order. Some industries require structured reports (regulated compliance, warranty); the report template generates accordingly.

Inventory and parts. Parts consumed:

• Pulled from technician's truck stock (a sub-warehouse).
• Posted as inventory consumption.
• May trigger replenishment (truck restock).
• Costed to the work order.

Truck inventory is mini warehouse management — without discipline, parts walk away.

Billing. Most work orders bill the customer:

• Time and materials — invoice for actual hours + parts.
• Fixed price — pre-quoted amount regardless.
• Warranty — covered by warranty, no customer charge.
• Service contract — covered by contract, no charge.

Billing rules on the work order determine which model applies; invoice generation follows posted work orders.

Service agreements and preventive maintenance. Recurring work orders generated automatically:

• Service agreement — annual or quarterly contract.
• Maintenance plan — defines schedules per asset.
• Auto-generation — system creates work orders ahead of due date.
• Routing — auto-scheduled to appropriate territories.

This generates the maintenance volume that fills the dispatcher's schedule.

Common pitfalls.

• Unscheduled work order backlog. Created but not scheduled; aging fast.
• No closure discipline. Completed work orders never posted; reporting wrong; revenue not recognised.
• Parts not captured. Technician forgot to log; inventory wrong; billing low.
• Service report not sent. Customer doesn't see what was done; disputes follow.
• Wrong work order type. "Repair" used when it should be "Warranty Repair"; billing wrong.
• Schedule board overcrowded. Too many open work orders without filtering; dispatcher overwhelmed.

Quality and feedback. Post-completion:

• Customer survey (Customer Voice integration).
• Net Promoter Score (NPS) per technician, per work order type.
• Coaching feedback flows back to technicians.

Strategic positioning. Field Service work orders bridge several domains — service operations, inventory, billing, scheduling, customer experience. Discipline at every transition makes the chain efficient; gaps anywhere cascade. The most mature field service operations have clear status definitions, clean handoff procedures, and dashboards that surface stuck or aging work orders before they become customer issues.