Field Service Work Order Checklist for Dispatch Handoffs

The foundation of any dispatch handoff is a clear description of the task. When creating the work order, ensure the title field accurately reflects the issue. In the "Work Order Form Fields | MaintainX Help Center," the only mandatory field is the title (What needs to be done?) (MaintainX). This means the handoff must include a title that explicitly states what needs to be done, because that field is mandatory. Without this, the technician may not understand the primary objective of the visit.

Additionally, consider the scope of the location. A work order can only have one assigned location, as documented in the "Work Order Form Fields | MaintainX Help Center" (MaintainX). If a customer has multiple sites, you must create separate work orders for each location to maintain this rule. Putting a single site on the work order is essential since only one location can be assigned. This prevents confusion in the field and ensures the technician is sent to the correct physical address for the specific asset or problem.

To begin your handoff process, verify that the work order title is descriptive and that the assigned location is singular. If the job involves multiple sites, split the work into distinct orders. This approach aligns with the documented structure of work orders and ensures the technician receives a clear, single-focus task.

• Recommendation: Use the mandatory title field to describe the specific problem, not just the asset name.
• Recommendation: Create separate work orders for each distinct location if the job spans multiple sites.

The dispatch handoff checklist serves as the primary record for transferring job details from the office to the field technician. It ensures that the person performing the work has the specific inputs required to begin safely and efficiently. The following fields represent editorial guidance for structuring this handoff. These selections are recommendations for your internal workflow and do not constitute a universal standard.

Core Handoff Inputs

When populating the checklist, capture the specific elements that define the job. The asset that needs maintenance, the location where the work will happen, and who is responsible for completing the work are fundamental components of a work order, as documented in the "About Work Orders | MaintainX Help Center" at MaintainX. This source also identifies which parts you need to do the work, when the work should start, when it should be completed by, and how long the work should take. Including these specific data points helps prevent ambiguity when the technician arrives on site.

For the location field, the service address and information about where to find the asset at the address, known as the functional location, should be included. Providing this spatial context helps the technician locate the specific equipment without relying on guesswork or additional phone calls.

Authorization and Safety Boundaries

The handoff must clearly identify the responsible person who authorised the work. The "Permit to Work Systems - HSE" page states that the work permit system should identify whether the employees responsible for control of the maintenance work are identified and that the work is properly authorised by a responsible person, as documented at HSE. Naming this individual in the checklist ensures accountability is clear before the technician begins.

Safety control decisions must remain with the qualified operator. An authorized person is defined as a person who is qualified to engage in hazardous energy control because of knowledge, training, and experience and has been assigned to engage in such control, according to "CCOHS: Lockout/Tag out" at CCOHS. The office should not dictate specific repair methods or safety procedures in the checklist. Instead, record the assigned qualified person for energy control.

Keep access or safety decisions with the qualified operator; do not include repair instructions in the dispatch handoff.

Work orders and bookings have independent lifecycles, but a booking's state influences the work order's status (Microsoft). For example, changing the booking status to Traveling automatically changes the work order system status to In Progress (Microsoft). Additionally, the creation of a booking automatically changes the work order system status to Scheduled (Microsoft). If there are multiple bookings for a single work order and one booking is in progress, the related work order status gets updated (Microsoft). The related work order system status changes to Completed when all related bookings are completed or canceled (Microsoft). However, regardless of status settings, the booking status has no impact on the status of Resource Requirements (Microsoft). By default, the system sets work orders to completed when the associated booking gets completed, but you can create or edit a booking status and set the Status completes work order toggle accordingly to change this default logic (Microsoft). For instance, a custom booking status with the Status completes work order toggle set to Off allows completing the booking to return the work order to an earlier stage for follow-up instead of marking it Completed (Microsoft). When you deactivate a parent record, such as a work order in Field Service, the system doesn't automatically deactivate its child records (Microsoft).

In contrast, "Track Field Service Jobs for Efficient Management" states that setting the status of a service appointment doesn’t change the status of the work order line item or work order that it’s associated with (Salesforce). This means that in this environment, the appointment and the work order operate as separate status tracks. For example, the status Dispatched means the service resource is traveling to the work site (Salesforce). The status Cannot Complete means the service resource was unable to finish the work (Salesforce). The status Closed means all work and associated activity is complete (Salesforce).

Similarly, "Activity and Work Order Status Update Work Flow" documents that when an activity is in 'Pending' or 'Started' status in Oracle Fusion Field Service, the work order operation is in 'Ready' status, and there's no change in the initial work order status (Oracle). This indicates that starting field activity does not, by default, alter the initial work order status in this system. When an activity is completed in Oracle Fusion Field Service, the corresponding operation status is changed to 'Completed'; when all the operations associated with the work order are completed, the status of the work order changes to 'Completed' (Oracle).

These differences matter for dispatch planning. If your platform does not automatically propagate status changes, you must manually update the work order to reflect field progress. If your platform does propagate changes, you must verify that the automatic updates align with your actual field conditions. For instance, if a technician is traveling but has not yet begun work, an automatic "In Progress" status might mislead office staff into thinking work is underway.

Editorial recommendation: Verify your specific platform’s status propagation rules before relying on automatic updates. If your system does not link appointment and work order statuses, add a manual step to your dispatch checklist to update the work order when the appointment status changes. If your system does link them, test the propagation with a sample job to ensure it matches your workflow expectations. Do not add, remove, or edit the option set values for Work Order System Status; instead, consider creating meaningful Work Order Substatus records (Microsoft).

The visit record documents the actual work performed and the materials consumed. In the "About Work Orders | MaintainX Help Center" guide, a work order summary is defined as a written or recorded voice note added to a work order to document how it was completed (MaintainX). You can use this field to capture the specific actions taken, such as parts replaced or adjustments made.

Parts usage must be recorded with precision. In the "Track Field Service Jobs for Efficient Management" resource, products consumed are defined as products used to complete a work order or work order line item, and the mobile workforce can record which part and how many were used to complete the work (Salesforce). In the "Work Order Form Fields | MaintainX Help Center" documentation, when you add a part, you must also specify the Amount Used (MaintainX).

Editorial recommendation: Use the following blank fields to capture the visit record. Do not pre-fill these values; they must be completed by the technician on-site.

When a technician returns from a site without finishing the job, the record must capture why the work stopped so the next dispatch is not a guess. In "Processing and Updating the Activity Information to Work Order," the "not done" action indicates that the activity couldn't be completed that day for various reasons, such as unavailability of parts, lack of time to finish, and so on (Oracle). Similarly, in "Track Field Service Jobs for Efficient Management," the status "Cannot Complete" means the service resource was unable to finish the work (Salesforce).

Do not let the system automatically mark the job as finished just because the technician arrived and left. If you treat a partial visit as a completed booking, the work order may incorrectly move to Completed. To prevent this, you can configure a custom booking status with the Status completes work order toggle set to Off, so that completing the booking returns the work order to an earlier stage for follow-up instead of marking it Completed (Microsoft). By default, the system sets work orders to completed when the associated booking gets completed, but you can change this default logic by going to the Field Service tab and setting the Status completes work order toggle accordingly (Microsoft).

In "Activity and Work Order Status Update Work Flow," when an activity is completed, the corresponding operation status is changed to 'Completed'; when all the operations associated with the work order are completed, the status of the work order changes to 'Completed' (Oracle). This means the work order moves to Completed only after every associated operation is completed.

Use the following blank record to document the exception before the next dispatch is scheduled. Fill in each field based on what the technician reported.

Verify the completed work and formally return the site to its operational state. This step ensures the field technician’s actions are documented accurately and the site owner or operator is aware the maintenance or repair is finished.

This verification step occurs before the record moves to a posted state. When a work order is posted, it generates invoices for used work order products and services for the billing account of the work order (Microsoft). Ensure line items and labor entries are accurate before triggering this status change.

Manually review and close related sub-records to ensure the job file is fully archived. When you deactivate a parent record, such as a work order in Field Service, the system doesn't automatically deactivate its child records (Microsoft). Additionally, the documentation advises not to add, remove, or edit the option set values for Work Order System Status; instead, consider creating meaningful Work Order Substatus records as a best practice (Microsoft). Use these substatus fields to capture specific office notes or final verification details without altering the core system status.

For sites with complex equipment, consider the principles outlined in Permit to Work Systems - HSE, which asks whether the work permit system involves a formal procedure whereby the maintained plant or equipment is handed back to operation (HSE). If your business operates under such a regime, the handback is not just a software click but a physical and procedural confirmation that the site is safe for normal use. The same source notes whether the employees responsible for control of the maintenance work are identified within the work permit system and that the work is properly authorised by a responsible person (HSE). Name that responsible person in your closure record.

The dispatch handoff checklist ensures the technician receives the customer reference, access details, asset information, reported problem, authorized scope, parts list, and next action before leaving the office. This structured approach supports the typical work order lifecycle, which moves from creation and scheduling to dispatch, service execution, supervisor review, and finally invoice and inventory adjustment (Microsoft). By separating appointment tracking from work order status, you maintain clear records for both the schedule and the actual labor performed. When work cannot be finished, recording the specific missing input and responsible role allows for efficient resolution during the next review cycle.

What is a work order?

A work order is a standardized document detailing a maintenance task or other work.

Does changing the appointment status change the work order?

In the Salesforce field service system, setting the status of a service appointment doesn’t change the status of the work order line item or work order that it’s associated with (Salesforce). Treat these as separate records in your dispatch notes.

What does 'Dispatched' mean?

According to Salesforce documentation, "Dispatched" means the service resource is traveling to the work site (Salesforce).

What is the difference between Completed and Closed?

In Salesforce field service tracking, "Completed" means the work is complete, while "Closed" means all work and associated activity is complete (Salesforce).

How do I record an incomplete visit?

If work cannot be finished, use the "Cannot Complete" status, which indicates that the work couldn't be completed (Salesforce).