How do you make sure the right field service technician arrives at the right customer site, with the right parts, at exactly the right time? Work Order Management and Scheduling is the core of Dynamics 365 Field Service that solves this problem, ensuring that service calls are tracked, assigned, and completed efficiently — a crucial topic for the MB-910 exam that tests your understanding of how field service organisations operate in the real world.
Jump to a section
A simple way to picture Work Order Management and Scheduling
Because you cannot serve a steak before it is cooked, a restaurant cannot fulfil an order without first preparing it. This cause-and-effect chain is exactly how Dynamics 365 Field Service manages work orders.
Think of a busy restaurant kitchen. A customer places an order (the work order). The order includes the table number, the dish requested, and any special instructions like 'no onions' — this is the work order details, including the customer location, the service required, and any parts needed. The head chef (the dispatcher) looks at the incoming orders on a big screen above the pass — this screen is the scheduling board. Orders appear as tickets, each showing the dish, the time it was received, and any notes. The head chef assigns each ticket to a specific chef based on their speciality — this is scheduling the work order to a technician. If the order is urgent, like a burnt steak needing an immediate replacement, the head chef can 'drag and drop' the ticket to the fastest chef available — this corresponds to drag-and-drop scheduling on the board. The head chef also considers the kitchen's workload; if the grill is backed up and the fryer is idle, the head chef might assign a fried dish next to balance the workflow — this is the optimisation logic, which considers factors like technician skills, travel distance, and part availability to suggest the best assignment automatically. Once assigned, the chef cooks the dish and the order is marked as complete — this is completing the work order in the system. The entire system, from order to completion, runs without paper tickets or shouting across the kitchen.
The scheduling board and optimisation logic replace the frantic, error-prone manual process with a clear, data-driven workflow that improves customer satisfaction and reduces wasted time.
Work Order Management is the process of creating, tracking, and completing a service request from a customer. Think of a work order as a digital folder that holds everything related to a single service job. When a customer calls to report a broken heating system, for example, a work order is created. This work order captures the customer’s name and address (the service account), a description of the problem (the service request), the type of equipment involved (the asset), and any agreements like a warranty (the service contract). Every action taken on that job is logged inside this digital folder.
In Dynamics 365 Field Service, a work order can be created in several ways. A customer service agent might create one manually after a phone call. Alternatively, a customer could submit a request through a web portal, which automatically generates a work order using Microsoft Power Automate workflows. Another common method is through scheduling optimisation: if a system is due for preventive maintenance (like an annual boiler check), Dynamics 365 can automatically generate work orders on a recurring schedule.
Once a work order exists, the next step is scheduling it. Scheduling means assigning a specific technician (or a team of technicians) to the work order at a specific time. Dynamics 365 Field Service provides a visual tool called the scheduling board. The scheduling board looks like a grid: rows represent technicians, and columns represent time slots (hours or days). Each work order appears as a coloured block (a requirement) that can be dragged and dropped onto a technician’s row to assign it. The scheduling board shows each technician’s availability, their current location (using GPS from their mobile device), and their skills (like 'gas safe registered' or 'electrician').
The scheduling board is powerful, but for organisations with many work orders, manually dragging each one is inefficient. This is where optimisation logic comes in. Dynamics 365 Field Service includes a feature called Resource Scheduling Optimisation (RSO). This is an artificial intelligence engine that automatically assigns work orders to the best technician. The optimisation logic considers several factors simultaneously. It looks at each technician’s skills to ensure the right person is assigned. It considers travel distance and traffic conditions to minimise travel time. It checks the technician’s current workload to avoid burnout and ensure fair distribution. It also respects customer preferences (for example, a customer might request only senior technicians). The optimisation engine then produces a suggested schedule, which a dispatcher can review and approve with one click.
Why does all this matter? Before digital systems like Field Service, scheduling was done manually using paper diaries and whiteboards. Dispatchers would call technicians on the radio to give them their next job. This was slow, error-prone, and led to long travel times and frustrated customers. Work Order Management and Scheduling in Dynamics 365 Field Service replaces this chaos with a centralised, automated system that improves first-time fix rates (the percentage of jobs resolved on the first visit) and reduces fuel costs. For the MB-910 exam, you need to understand that work orders are the central record for any field service job, the scheduling board is the visual interface for assigning work, and optimisation logic is the AI that automates smart scheduling decisions.
Work Order Creation
A work order is created when a customer request comes in, either through a phone call, a web portal submission, or automatically from a maintenance schedule. This step captures the customer account, the service location, the problem description, and any relevant equipment details.
Requirement Generation
When a work order is created, the system generates one or more requirements — these are the signals that a technician is needed. Each requirement specifies what skills are needed, how much time the job should take, the territory (geographic area), and the priority of the job.
Scheduling (Assignment)
The dispatcher uses the scheduling board to assign the requirement to a specific technician. This can be done manually by dragging the requirement onto a technician’s timeline, or automatically using the Schedule Assistant or Resource Scheduling Optimisation. The result is a booking — a confirmed time slot for the technician.
Dispatch and Execution
The technician receives the booking on their mobile device via the Field Service mobile app. They travel to the customer site, perform the service (repair or maintenance), log the parts used and the labour time, and update the work order status to 'In Progress' and then to 'Completed'.
Post Completion and Closure
After the technician marks the work order as completed, the office team reviews the details for accuracy. The work order is then 'posted' — this action updates inventory (reducing stock for parts used), calculates labour costs, and creates the basis for an invoice. The work order status changes to 'Closed' or 'Posted'.
Let us walk through a realistic scenario at a company called 'GreenHome Heating', a small firm that installs and repairs boilers. GreenHome has five field technicians and receives about 30 service calls per day. Before implementing Dynamics 365 Field Service, the office manager, Sarah, used a paper diary to write down each job and called technicians on their mobile phones to tell them where to go next. This led to several problems: technicians sometimes arrived at the wrong address, jobs with urgent needs were not prioritised, and the company had no way to track how many jobs were completed each week.
After implementing Dynamics 365 Field Service, the process changes completely. Here is how a typical morning now works:
A customer calls at 8:15 AM to report that their boiler has completely stopped working, and they have no hot water. The customer service agent (Louise) creates a new work order in Dynamics 365 Field Service. She enters the customer’s address, selects 'Boiler Repair' as the work order type, and marks the priority as 'High' because it is an emergency during winter.
The system immediately shows this new work order on the scheduling board. Sarah, the dispatcher, opens the scheduling board on her computer screen. She sees all five technicians on the left side, each with their current appointments shown as coloured blocks. She notices that the nearest available technician, Mark, is finishing a job about 15 minutes away from the customer’s house.
Instead of manually assigning the job, Sarah uses the 'Schedule Assistant' feature. She right-clicks on the unassigned work order and selects 'Find Availability'. The Schedule Assistant automatically checks Mark’s skills (he is certified for boiler repairs), his current location (via GPS from the Field Service mobile app on his phone), and the travel time (considering current traffic data). It suggests a time slot in 30 minutes. Sarah accepts the suggestion with one click.
Mark receives an automatic notification on his mobile device. The mobile app shows him the work order details, including the customer’s address, the problem description, and any notes Louise added (e.g. 'Customer is elderly, please be patient'). Mark also sees a route map with directions. He drives to the customer’s house, completes the repair (replacing a faulty thermocouple), and uses the mobile app to update the work order status to 'Completed'. He also logs the parts used (a thermocouple part number TC-100) and the time spent (1.5 hours).
Back in the office, Sarah can see a real-time dashboard showing that the job is done, the parts used, and the total labour hours. The system automatically generates an invoice for the customer based on the work order data. The customer receives a satisfaction survey by email.
At the end of the month, GreenHome’s manager reviews reports on first-time fix rates, average travel time, and technician utilisation. Using the optimisation logic, she reconfigures the scheduling preferences to reduce travel time by 20%, saving the company money on fuel.
This scenario shows that an IT professional does not just click buttons — they configure the system to make these workflows happen. They set up work order types, define technician skills, configure the scheduling board views, and tune the optimisation engine’s goals (e.g. minimise travel time versus maximise coverage). The IT professional ensures that data flows correctly from the work order to the mobile app to the invoicing system, so the business runs smoothly without paper.
The MB-910 exam tests your foundational understanding of Work Order Management and Scheduling. You are not expected to configure the system yourself — you must recognise the purpose and high-level features. Here is exactly what you need to know.
Exam topics you will definitely see:
Work order lifecycle: You must know the stages a work order passes through: Created -> Scheduled -> In Progress -> Completed -> Posted. A common trap question asks: 'When does a work order affect inventory?' The correct answer is when it is completed, not when it is created or scheduled.
Scheduling board purpose: The question might ask: 'What is the primary purpose of the scheduling board?' The correct answer is: 'To visually assign and manage work orders to technicians based on availability and skills.' Distractors include 'To send invoices' or 'To track customer feedback'.
Resource Scheduling Optimisation (RSO): You will be asked what RSO does. The correct answer is that it automatically suggests the best technician based on skills, location, and availability. A common trap is to confuse RSO with the Schedule Assistant — RSO is the full optimisation AI; Schedule Assistant is a manual tool within the scheduling board that finds availability for one work order at a time.
Work order components: Know that a work order can include service tasks (a checklist of things to do), product (parts used), service (labour time), and incident types (predefined problem categories). A question might ask: 'Which of these is NOT a part of a work order?' with options like 'Product', 'Service', 'Invoice' — the correct answer is 'Invoice' because the invoice is generated after the work order is completed.
Scheduling methods: Know the difference between drag-and-drop scheduling (manual), Schedule Assistant (semi-automated, finds one fit), and Resource Scheduling Optimisation (fully automated, optimises the entire schedule). The exam loves to ask: 'Which method would you use to automatically assign all new work orders at midnight?' — Answer: Resource Scheduling Optimisation.
Key definitions to memorise:
Work order: A digital container capturing all details of a service job, including customer, location, problem, parts, labour, and status.
Scheduling board: A visual grid that displays technicians and their assigned time blocks, used to manually or semi-automatically assign work.
Resource Scheduling Optimisation (RSO): An AI engine that automatically creates optimal schedules by considering skills, location, availability, and business rules.
Requirement: The representation of the need for a technician — a work order generates one or more requirements.
Booking: The resulting assignment when a requirement is matched to a specific technician at a specific time.
Trap patterns to watch for:
The exam may ask: 'Where do you manage the list of technician skills?' The answer is 'In the resource's record, under Characteristics', not from the work order itself.
Another trap: 'Which of the following can automatically generate a work order?' The correct answer is a recurring work order (for preventive maintenance) or a Power Automate flow. A distractor might say 'The scheduling board' — that is false, because the scheduling board is for assignment, not creation.
A question might present a scenario: 'A dispatcher needs to see which technicians are available in the next hour. Which tool should they use?' Answer: The scheduling board (filtered by time range). A tempting wrong answer is 'Resource Scheduling Optimisation' because it sounds advanced, but RSO is for automated assignment, not simple visualisation.
Study these carefully. The MB-910 exam phrasing often presents real-world scenarios rather than theoretical definitions. Practise recognising which feature matches the described need.
A work order is the central digital record that captures all information about a single field service job, including customer details, the problem, parts used, and labour time.
The scheduling board is a visual tool where dispatchers can see technician availability and assign work orders by dragging and dropping requirement blocks.
Resource Scheduling Optimisation (RSO) is an AI engine that automatically assigns work orders to the best technician by balancing skills, travel distance, and workload.
Work orders can be created manually, automatically from a customer portal, or on a recurring basis for preventive maintenance.
Technician skills are stored in the resource record (called Characteristics) and are matched against skill requirements in the work order.
Completing a work order does not automatically generate an invoice; invoicing is a separate step that happens after the work order is marked complete.
These come up on the exam all the time. Here's how to tell them apart.
Work Order
A record of the entire service request including customer, problem, parts, and labour.
Can contain multiple tasks and multiple required resources.
Exists independently of any technician assignment.
Booking
A specific time slot assigned to a single technician.
Links a single requirement to a single resource at a specific time.
Created only after scheduling is completed.
Schedule Assistant
A manual tool accessed from the scheduling board for one work order at a time.
Finds the next available time slot for a single requirement.
Does not consider the impact on other work orders.
Resource Scheduling Optimisation (RSO)
An automated engine that optimises all work orders in a batch.
Runs on a schedule (e.g. every 30 minutes) or is triggered manually.
Balances multiple factors like travel time, skills, and workload simultaneously.
Service Account
The customer location (e.g. a house or business address) where service is delivered.
Represents the billing and contact relationship.
Is the primary entity linked to a work order.
Asset
The specific piece of equipment or device being serviced (e.g. a boiler model XYZ).
Can be installed at a service account and can have a service history.
Is optional on a work order, but provides detailed context.
Work Order Type
Categorises the business purpose of the work order (e.g. Emergency Repair, Scheduled Maintenance).
Determines default values and processes for the work order.
Set at work order creation and applies to the entire job.
Incident Type
A predefined problem template (e.g. Boiler No Heat, Leaking Pipe).
Includes default service tasks, products, and labour estimates.
Can be added to a work order to quickly populate details.
Mistake
The scheduling board and Resource Scheduling Optimisation are the same thing.
Correct
The scheduling board is a visual interface for manual or semi-automated scheduling; Resource Scheduling Optimisation is a separate AI engine that automatically optimises assignments across multiple work orders.
Both appear in the scheduling context, and beginners assume 'board' and 'optimisation' are interchangeable when they serve different purposes.
Mistake
A work order is only created when a customer calls.
Correct
Work orders can be created manually, automatically from a portal, or automatically generated on a recurring schedule for preventive maintenance.
Beginners often think of work orders as reactive only, overlooking the preventive automation aspect commonly tested.
Mistake
Completing a work order automatically sends the invoice.
Correct
Completing a work order updates its status, but invoicing is a separate action that must be performed, often manually or through a separate automatic process.
The exam tests lifecycle stages, and beginners blur the boundary between completion and posting/invoicing.
Mistake
Technician skills are defined inside the work order.
Correct
Technician skills are defined in the resource (technician) record under Characteristics; the work order specifies the required skills via a requirement.
Beginners think everything lives inside the work order object, but skills are attached to the resource and matched to the requirement.
Mistake
Resource Scheduling Optimisation works instantly when you save a work order.
Correct
RSO typically runs on a schedule (e.g. every 15 minutes) or is triggered manually; it does not run instantly with every work order creation by default.
The exam may test this nuance, and beginners assume real-time automation covers all scenarios.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A work order is the full record of a service job, including customer info and tasks. A booking is the specific time slot assigned to a technician — a work order can have multiple bookings if the job is revisited.
Yes, a work order can generate multiple requirements, each assigned to different technicians, allowing a team to work on the same job at the same time or sequentially.
Technicians use the Field Service mobile app which sends GPS data to the system. The scheduling board shows this location so dispatchers can see who is closest to a new job.
Yes, it can be configured to run on any day and time, including weekends, if the organisation operates around the clock for emergency services.
The technician can reopen the work order and reschedule it. A new requirement is created, and the scheduling board will show it again for reassignment.
Yes, Dynamics 365 Field Service integrates with Dynamics 365 Sales, so you can convert a quote or opportunity into a work order automatically when a deal is closed.
You've finished Work Order Management and Scheduling. Continue through the MB-910 study guide to build a complete picture of the exam.
Done with this chapter?