Overview
Schedule and dispatch work orders accounted for 15–20% of MB-240. It is built on Universal Resource Scheduling (URS), the scheduling engine shared by Field Service and other Dynamics 365 apps. The domain covers scheduling with the schedule board and the schedule assistant, fulfillment preferences that limit arrival windows, quick scheduling, multi-day requirements, and including appointments in availability.
It also covers configuring schedule boards themselves: tabs, views, the Requirements panel, board settings and board-level customization. A third group deals with the schedule assistant's settings, filters and troubleshooting, and the last group goes under the hood of URS: enabling scheduling for a custom table, configuring geocoding for that table, and using booking timestamps, booking journals and actuals to record what happened and what it cost.
How it's tested
Expect scenario questions that describe what a dispatcher sees, or fails to see, and ask which setting, filter or view explains it. Others ask how to schedule a type of work, such as multi-day installations or customer time windows, and expect a URS feature rather than custom development.
-
Missing result diagnosis
Resources or time slots are missing from schedule assistant output, and you identify the constraint, geocode or working hours issue causing it.
-
Board configuration
A dispatcher wants a different view, filter default or Requirements panel layout, and you choose tab settings, board settings or customization.
-
Extending scheduling
A custom table must be scheduled on the board, and you enable it for URS and configure metadata and geocoding.
A dispatcher reports that work orders for a new housing estate never show travel time and the schedule assistant returns resources in random order. The common factor is location: the new addresses were never geocoded, so latitude and longitude are empty. Geocoding the service accounts and enabling auto-geocoding in Field Service settings restores distance-based sorting and travel calculations without touching resource configuration.
Functional groups 4
Official functional groups from the Microsoft outline, in outline order.
3.1 Manage scheduling optionsSchedule board and assistant, fulfillment preferences, quick book, multi-day requirements and appointments.
- What it means
- This group covers the ways work is booked: dragging requirements on the schedule board, using the schedule assistant, applying fulfillment preferences, configuring quick scheduling, handling requirements that span several days, and including Dataverse or Outlook appointments when calculating availability.
- What to understand
- The schedule assistant reads the requirement's duration, territory, characteristics, role and time window and returns ranked resources and slots. Fulfillment preferences define time groups, such as morning or afternoon windows, that limit start times. Multi-day requirements use an allocation method (for example full capacity or hours per day) to split work across days. When appointments are included, existing calendar items reduce resource availability.
- How it shows up
- Look for a customer time window or a three-day installation and a question on which feature handles it.
- Common confusion
- Fulfillment preferences limit when work starts; they do not change the requirement's duration.
3.2 Configure, customize, and manage schedule boardsBoard tabs and views, Requirements panel, board settings and customization.
- What it means
- This group covers how dispatchers see work: creating and sharing schedule board tabs, choosing hourly, daily, weekly or monthly views, configuring the Requirements panel beneath the board, changing board settings and customizing the board's appearance and queries.
- What to understand
- Each tab has its own settings, such as which resources show, default filters, map display and booking colors. The Requirements panel can show several views, for example unscheduled work orders or requirements for a territory. Board settings control details like the time scale and whether travel time displays. Customization can change templates and the queries that select resources and requirements. Tabs can be shared so a regional team uses the same view.
- How it shows up
- Expect a dispatcher preference and a choice between tab settings, default settings and customization.
- Common confusion
- Changing default board settings affects new tabs, not tabs a dispatcher has already customized.
3.3 Configure the schedule assistantSchedule assistant settings, filtering constraints and troubleshooting.
- What it means
- This group covers the search engine behind booking suggestions: its settings, the constraints and filters that narrow results, and how to diagnose results that are empty or unexpected.
- What to understand
- Constraints come from the requirement (territory, characteristics, roles, organizational unit, time window, resource preferences) and the dispatcher can adjust filters at search time. Resource preferences can mark resources as preferred, restricted or mandatory for an account. Troubleshooting follows a checklist: working hours, geocodes, territory membership, characteristic ratings, roles, existing bookings and whether the resource is enabled for scheduling.
- How it shows up
- Look for an empty result list and a question on the most likely configuration cause.
- Common confusion
- Removing a filter at search time does not change the requirement; the constraint returns next time.
3.4 Configure Universal Resource SchedulingEnabling tables for scheduling, geocoding custom tables, booking timestamps, journals and actuals.
- What it means
- This group covers URS administration: enabling a table for scheduling and configuring its booking setup metadata, setting up geocoding for a custom table, and configuring booking timestamps, booking journals and actuals.
- What to understand
- Enabling a table for scheduling adds a relationship to resource requirements and bookings, and metadata defines booking statuses and default settings for that table. A custom table needs latitude and longitude columns mapped so URS can calculate distance. Booking timestamps record each status change. Booking journals, created when a booking completes, split time into working, travel, break and overtime pay types. Actuals record cost and billing amounts for completed work.
- How it shows up
- Expect a question on scheduling a non-standard table, or on where time and cost records come from.
- Common confusion
- Booking journals record time by pay type; actuals record cost and billable amounts derived from that time.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Universal Resource Scheduling
Shared scheduling engine across Dynamics 365 apps.
- Remember
- Field Service builds on it rather than replacing it.
- Tested as
- Architecture questions.
- Trap
- Assuming it only works for work orders.
-
Resource requirement
The record the scheduler books against.
- Remember
- Created automatically for each work order.
- Tested as
- Booking questions.
- Trap
- Booking the work order directly.
-
Schedule assistant
Search for best-fit resources and slots.
- Remember
- Reads constraints from the requirement.
- Tested as
- Booking and troubleshooting questions.
- Trap
- Expecting it to ignore working hours.
-
Fulfillment preference
Time groups that limit arrival windows.
- Remember
- Controls start time, not duration.
- Tested as
- Customer window scenarios.
- Trap
- Using it to restrict days of the week only.
-
Allocation method
How a multi-day requirement is split.
- Remember
- Options include full capacity and hours per day.
- Tested as
- Multi-day questions.
- Trap
- Creating several separate work orders.
-
Resource preference
Preferred, restricted or mandatory resource for an account.
- Remember
- Affects schedule assistant results.
- Tested as
- Customer preference scenarios.
- Trap
- Using territory to exclude one technician.
-
Requirements panel
Lower pane of the board listing work to book.
- Remember
- Can show several configured views.
- Tested as
- Board configuration.
- Trap
- Expecting it to show only work orders.
-
Schedule board tab
Saved board configuration.
- Remember
- Has its own settings and can be shared.
- Tested as
- Dispatcher preference questions.
- Trap
- Editing defaults to change an existing tab.
-
Geocoding
Latitude and longitude on addresses.
- Remember
- Required for travel and distance sorting.
- Tested as
- Missing travel time scenarios.
- Trap
- Blaming the map provider.
-
Enable table for scheduling
Makes a custom table bookable through URS.
- Remember
- Uses booking setup metadata.
- Tested as
- Extensibility questions.
- Trap
- Building a custom scheduling app.
-
Booking timestamp
Record of each booking status change.
- Remember
- Feeds journals and reporting.
- Tested as
- Time tracking questions.
- Trap
- Expecting timestamps from work order status changes.
-
Booking journal
Time breakdown by pay type for a booking.
- Remember
- Generated at completion.
- Tested as
- Payroll and cost questions.
- Trap
- Confusing journals with actuals.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Schedule board vs. schedule assistant vs. quick book
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Schedule board | Visual planning surface for resources and bookings | Dispatcher drags and drops work | Expecting automatic ranking |
| Schedule assistant | Constraint-based search for slots | Ranks resources by fit and distance | Ignoring that constraints come from the requirement |
| Quick book | Streamlined booking from a single requirement | Fastest path for simple bookings | Using it for complex multi-resource jobs |
Booking timestamps vs. booking journals vs. actuals
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Booking timestamp | Status change log for a booking | Captures when each status was set | Treating it as a cost record |
| Booking journal | Time split by pay type | Created when the booking completes | Expecting it before completion |
| Actual | Cost and billing amount record | Used for financial reporting | Confusing it with time entry |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Map provider at fault
- What candidates pick
- Change the map provider when travel time is missing.
- Why it looks right
- Travel time involves maps.
- Why it's wrong
- Missing latitude and longitude on the service account is the usual cause; geocoding fixes it.
Clue to watch for Only recently created addresses are affected.
-
Filter removal is permanent
- What candidates pick
- Remove a territory filter in the assistant to fix all future searches.
- Why it looks right
- It works for this search.
- Why it's wrong
- Filters adjusted at search time do not change the requirement, so the constraint reappears next time.
Clue to watch for The problem recurs on new work orders.
-
Separate work orders for long jobs
- What candidates pick
- Create one work order per day for a three-day install.
- Why it looks right
- Each day is easy to book.
- Why it's wrong
- A multi-day requirement with an allocation method keeps one job and spreads capacity across days.
Clue to watch for One job spans several days.
-
Territory to exclude a technician
- What candidates pick
- Move a technician out of the territory because a customer rejected them.
- Why it looks right
- It removes them from results.
- Why it's wrong
- A restricted resource preference on the account excludes that technician only for that customer.
Clue to watch for One customer has a preference about one person.
-
Custom app for scheduling
- What candidates pick
- Build a canvas app to schedule inspections on a custom table.
- Why it looks right
- It seems flexible.
- Why it's wrong
- Enabling the table for URS gives the board, assistant and bookings with configuration rather than code.
Clue to watch for A custom table needs to appear on the schedule board.
Answer framework
When a Domain 3 question describes a scheduling symptom or need, work through these checks.
- Identify whether the question is about booking work, configuring what dispatchers see, diagnosing results or extending URS to another table.
- For empty or odd results, check working hours, geocodes, territory, characteristic ratings, roles and resource preferences in that order, since any one of them can silently filter resources out.
- For customer time windows use fulfillment preferences, and for long jobs spanning several days use a multi-day requirement with the right allocation method.
- For dispatcher views decide between tab settings, the Requirements panel, default board settings and board customization.
- For custom tables enable scheduling, configure booking setup metadata and map latitude and longitude fields for geocoding on the schedule board map.
Practice question
Want more like this? The MB-240 practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Learn this domain on the schedule board itself. In a trial, create a handful of work orders in two territories, then book them three ways: drag from the Requirements panel, use the schedule assistant, and use quick scheduling. Change one variable at a time, such as removing a resource's working hours, clearing a geocode or raising a characteristic rating, and note how results change. That builds the troubleshooting order the exam rewards.
Next, configure the board. Create a new tab, change its view and filters, add a Requirements panel view for urgent work, and share the tab. Then change default board settings and confirm which tabs pick up the change.
For URS administration, enable a simple custom table for scheduling, map latitude and longitude, and book a record on the board. Complete a work order booking and open the booking timestamps, booking journals and actuals it produced. Finish by reading about fulfillment preferences and multi-day allocation methods, and write a short list of symptoms with their likely causes to review before practice tests.
FAQ
How much of MB-240 was Schedule and dispatch work orders?
Schedule and dispatch work orders carried 15–20% of the exam in the September 2025 outline, the third-largest domain.
What is Universal Resource Scheduling?
It is the shared scheduling engine behind the schedule board and schedule assistant. Field Service uses it for work orders, and other tables can be enabled for it.
Why are no resources returned by the schedule assistant?
Usually working hours are missing, the requirement or resources lack geocodes, territories do not match, or characteristic ratings and roles do not meet the requirement.
How do I schedule a job that takes several days?
Use a multi-day requirement and choose an allocation method, such as full capacity or hours per day, so the work is spread across days on one job.
What are fulfillment preferences?
They define time groups, such as morning or afternoon windows, that limit when a booking can start, typically to honor a customer's preferred arrival window.
Where does booking time for payroll come from?
Booking timestamps record each status change, and when the booking completes a booking journal splits the time into pay types such as work, travel and break.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 3 knowledge
You have covered the schedule board, schedule assistant, fulfillment preferences, multi-day work and URS setup. See whether you can diagnose scheduling symptoms quickly.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the MB-240 AI tutor Get any concept explained your way