MB-240 · Domain 2 of 6

MB-240 Domain 2: Manage work orders and customer assets

The heaviest MB-240 area: work order types and statuses, incident types, agreements that generate recurring work and invoices, inspections, and the customer assets and functional locations that service history attaches to.

Exam weight
25–30%
Official functional groups
6
Estimated questions estimate
12–15
Suggested study time estimate
20–26 hrs

About 14 min read Reviewed October 2026

Overview

Manage work orders and customer assets was the largest share of MB-240, at 25–30%. It follows a job from creation to closure. You configure work order types, resolutions, booking statuses and work order sub-statuses, then create work orders manually, from Microsoft 365 Copilot in Outlook, or automatically from agreements. Incident types act as templates that add service tasks, products, services, durations and requirement groups to a job in one step.

Agreements schedule recurring maintenance, generate work orders ahead of time, raise recurring invoices and carry entitlements. Inspections capture structured checklists against work orders or customer assets, and can also run without a work order. Customer assets, child assets, functional locations, 3D models and property templates describe the equipment being serviced, so that every job builds a usable service history.

How it's tested

Domain 2 questions usually describe a service process and ask which template, status or automatic behavior delivers it. Pay attention to whether the scenario is a one-off job, a repeating commitment, or a checklist, and to whether the work is tied to a specific piece of equipment or a location in a site hierarchy.

  • Status mapping

    You decide which booking status or system status a technician action produces, and what that does to the parent work order.

  • Template choice

    A repeated job pattern is described and you choose incident type, agreement, requirement group template or inspection template.

  • Asset structure

    You choose between customer asset, child asset and functional location to model equipment that sits inside a building or larger system.

Reasoning it through

A hospital wants monthly filter changes on 40 air handlers, with each visit invoiced quarterly. Creating 40 recurring work orders by hand fails the scale test. An agreement with booking setups and an incident type for the filter change generates work orders ahead of each date, and an agreement invoice setup raises the quarterly invoice. Linking the air handlers as customer assets keeps per-unit history.

Functional groups 6

Official functional groups from the Microsoft outline, in outline order.

2.1 Configure the work order lifecycleWork order types, resolutions, booking statuses and sub-statuses.
What it means
This group covers the reference data that shapes a work order's journey: work order types, work order resolutions, booking status values and work order sub-status values.
What to understand
A work order type sets defaults such as price list, whether an incident type is required and whether the job is taxable. System statuses are fixed (Unscheduled, Scheduled, In Progress, Completed, Posted, Canceled); sub-statuses are custom labels mapped to one system status. Booking statuses are what technicians change, and each maps to a Field Service status that rolls up to the work order. Resolutions record how a job ended and can be required before closure.
How it shows up
Expect a question about adding a business-specific label without breaking the lifecycle, which points to a sub-status.
Common confusion
System statuses cannot be added; new labels must be sub-statuses or booking statuses mapped to existing values.
2.2 Create and manage work ordersCreating work orders, statuses, geography, price lists, SLAs, entitlements, closure and Copilot in Outlook.
What it means
This group covers the day-to-day handling of work orders: creating them, setting status and sub-status, organizing work by geography, attaching price lists, service-level agreements and entitlements, closing with a resolution, and creating a work order from Outlook through Microsoft 365 Copilot.
What to understand
Creating a work order generates a resource requirement for scheduling. Service account address and territory drive geography and travel. Entitlements apply discounts or alternate price lists to qualifying lines, and SLAs add KPI timers such as time to first arrival. When the last booking completes, the work order becomes Completed; reviewing and setting it to Posted locks it and finalizes billing records. Copilot in Outlook drafts a work order from an email.
How it shows up
Look for questions on what happens at Completed versus Posted and how entitlements change price.
Common confusion
Completed means the work is done; Posted means it has been reviewed and financially finalized.
2.3 Manage incidentsIncident types, suggestions, requirement group templates, service tasks, products and services.
What it means
This group covers incident types, which describe a problem or job type, including incident type suggestions, assigning requirement group templates, and adding service tasks, products and services to them.
What to understand
Adding an incident type to a work order copies its service tasks, estimated products and services, characteristics and estimated duration onto the job. Only the primary incident type sets the work order's duration and skills by default. A requirement group template on the incident type produces a multi-resource requirement. Incident type suggestions analyze completed work order history and propose updates, such as a more realistic duration or a commonly used part.
How it shows up
Expect scenarios asking how to standardize a repeated job so that every work order is pre-filled.
Common confusion
Additional incident types add tasks and lines but do not change the primary requirement unless configured to.
2.4 Create and manage agreementsAgreements, automatic work order generation, booking setup, invoicing and entitlements.
What it means
This group covers agreements for recurring service: configuring them, generating work orders automatically, defining booking setups and recurrence, setting up recurring invoices and creating entitlements tied to the agreement.
What to understand
An agreement must be Active to generate anything. Booking setups define recurrence and the incident types, products and services for each visit. With auto-generate enabled, work orders are created a set number of days before each date, a value controlled in Field Service settings or on the booking setup. Invoice setups create invoices on their own recurrence regardless of whether work happened. Agreement entitlements apply pricing benefits to work under that agreement.
How it shows up
Look for a recurring maintenance contract and a question on what generates work and invoices.
Common confusion
Invoice recurrence is independent of booking recurrence; they are configured separately.
2.5 Manage inspectionsInspection templates, linking to work orders and assets, and inspections without work orders.
What it means
This group covers digital inspections: building inspection templates, associating them with work orders and customer assets, and running inspections that are not tied to a work order.
What to understand
Inspection templates are built in a drag-and-drop designer and published. A template is linked to a service task type, so adding that task to a work order adds the inspection. Asset-based inspections attach the same template to several customer assets on one job, giving per-asset results. Responses are stored with the task and can be analyzed later. Published templates should be versioned rather than edited in place.
How it shows up
Expect a question on attaching a checklist to every job of a certain type, which means linking the template to a service task type.
Common confusion
Editing a published template changes future use; existing completed responses stay with the earlier version.
2.6 Configure customer assetsCustomer assets, automatic creation, child assets, 3D models, functional locations and properties.
What it means
This group covers modeling serviced equipment: creating customer assets, configuring products to create assets automatically, building parent-child hierarchies, adding 3D asset models, defining functional locations, and setting up properties and property templates.
What to understand
A customer asset records equipment at a service account. Setting a product's Convert to Customer Asset option creates an asset when that product is used on a work order. Child assets describe components under a parent, and the top-level asset is tracked automatically. Functional locations describe the place, such as a building or floor, where assets sit. Property templates define readings, like pressure or meter values, for asset categories, and values are logged over time.
How it shows up
Expect a choice between modeling a place and modeling a piece of equipment.
Common confusion
Functional locations are places in a site hierarchy; customer assets are equipment and can sit at a functional location.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Work order system status

    Fixed lifecycle values from Unscheduled to Posted or Canceled.

    Remember
    Cannot be extended; use sub-statuses.
    Tested as
    Lifecycle questions.
    Trap
    Trying to add a custom system status.

  • Work order sub-status

    Custom label mapped to one system status.

    Remember
    Gives business detail without breaking automation.
    Tested as
    Status customization questions.
    Trap
    Mapping a sub-status to the wrong system status.

  • Booking status

    Technician-facing status mapped to a Field Service status.

    Remember
    Drives work order system status changes.
    Tested as
    Mobile and dispatch questions.
    Trap
    Changing the work order status directly instead of the booking.

  • Completed vs. Posted

    Work done versus reviewed and finalized.

    Remember
    Posted locks the work order for billing.
    Tested as
    Closure questions.
    Trap
    Treating Completed as the final financial state.

  • Primary incident type

    The main incident on a work order.

    Remember
    Sets duration and skills on the requirement.
    Tested as
    Incident questions.
    Trap
    Expecting extra incident types to extend duration automatically.

  • Incident type suggestions

    AI-assisted proposals based on work order history.

    Remember
    Suggest updates to durations and lines.
    Tested as
    Continuous improvement scenarios.
    Trap
    Thinking they change work orders automatically.

  • Agreement booking setup

    Recurrence and job content for agreement visits.

    Remember
    Generates work orders ahead of each date.
    Tested as
    Preventive maintenance questions.
    Trap
    Leaving the agreement in Estimate status.

  • Agreement invoice setup

    Recurring invoice schedule on an agreement.

    Remember
    Independent from visit recurrence.
    Tested as
    Billing questions.
    Trap
    Assuming invoices only follow completed visits.

  • Entitlement

    Rule that changes pricing for qualifying work.

    Remember
    Can apply discounts or a different price list.
    Tested as
    Pricing questions.
    Trap
    Confusing it with an SLA.

  • Inspection template

    Published checklist built in a designer.

    Remember
    Linked through a service task type.
    Tested as
    Checklist scenarios.
    Trap
    Expecting to attach it straight to a work order type.

  • Convert to customer asset

    Product setting that creates assets when used.

    Remember
    Applies to work order product lines marked used.
    Tested as
    Asset automation questions.
    Trap
    Expecting estimated lines to create assets.

  • Functional location

    A place in a site hierarchy where assets sit.

    Remember
    Assets can be linked to a location.
    Tested as
    Asset modeling questions.
    Trap
    Modeling a building as a customer asset.

  • Property template

    Defines readings captured for an asset category.

    Remember
    Values are logged over time.
    Tested as
    Asset monitoring questions.
    Trap
    Adding custom columns to every asset instead.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Work order statuses and labels

ConceptMeaningKey differenceCommon trap
System status Fixed lifecycle value Drives automation and cannot be extended Trying to add new values
Sub-status Custom label on a work order Must map to a system status Using it for technician updates
Booking status Status a technician sets on a booking Rolls up to the work order Editing the work order directly

Incident type vs. agreement vs. inspection template

ConceptMeaningKey differenceCommon trap
Incident type Template for one kind of job Pre-fills tasks, lines and duration Expecting it to create recurring work
Agreement Recurring service commitment Generates work orders and invoices on a schedule Using it for one-off jobs
Inspection template Structured checklist Captures responses via a service task Treating it as a replacement for tasks

Customer asset vs. functional location

ConceptMeaningKey differenceCommon trap
Customer asset A piece of serviced equipment Carries service history and properties Modeling buildings as assets
Child asset Component inside a parent asset Shares a top-level asset Flattening components into one asset
Functional location A place where assets sit Builds a site hierarchy Expecting it to hold readings

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Custom system status

    What candidates pick
    Add a new system status called Awaiting Parts.
    Why it looks right
    It matches the business language.
    Why it's wrong
    System statuses are fixed; a sub-status mapped to Scheduled or In Progress records the detail without breaking automation.

    Clue to watch for The requirement is a new label for reporting.

  2. Completed is final

    What candidates pick
    Treat Completed as ready for invoicing without review.
    Why it looks right
    The job is done.
    Why it's wrong
    Posting is the step that locks the work order and finalizes billing, usually after a back-office review.

    Clue to watch for A manager must review before billing.

  3. Invoices follow visits

    What candidates pick
    Expect agreement invoices only after work orders complete.
    Why it looks right
    It seems logical to bill after work.
    Why it's wrong
    The invoice setup runs on its own recurrence and creates invoices whether or not visits have happened.

    Clue to watch for A fixed monthly fee is mentioned.

  4. Estimated lines create assets

    What candidates pick
    Rely on estimated products to create customer assets.
    Why it looks right
    The product is already on the work order.
    Why it's wrong
    Assets are created when the product line is marked used and the work order progresses, not from estimates alone.

    Clue to watch for The part has not been installed yet.

  5. Inspection on work order type

    What candidates pick
    Attach the inspection template directly to the work order type.
    Why it looks right
    Work order types set defaults.
    Why it's wrong
    Inspections connect through service task types, which are then added to incident types or work orders.

    Clue to watch for Every job of a kind needs the same checklist.

  6. Asset for a location

    What candidates pick
    Create a customer asset for each building floor.
    Why it looks right
    Assets have hierarchy too.
    Why it's wrong
    Places belong in functional locations; customer assets represent equipment and can be linked to those locations.

    Clue to watch for The scenario describes sites, buildings or rooms.

Answer framework

For work order and asset scenarios in Domain 2, work through these steps in order.

  1. Decide whether the need is a one-off job, a repeated job pattern or a recurring commitment, because that separates work orders, incident types and agreements.
  2. For status questions, identify the booking status a technician sets and follow how it maps to the work order system status.
  3. Check pricing influences on the work order: price list from the account or agreement, entitlements and any SLA timers that apply.
  4. For checklists, link an inspection template to a service task type, and use asset-based inspections when several units are checked on one visit.
  5. For equipment, use customer assets and child assets, place them in functional locations, and capture readings with property templates.

Practice question

A facilities company wants every quarterly chiller service to generate a work order two weeks before the due date and to bill a fixed monthly fee, even in months with no visit. What should the consultant configure?

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

Give this domain the most time, because it carried the largest weight and connects to everything else. Build one end-to-end scenario in a trial: a service account with a price list, a work order type, an incident type with two service tasks, a part and a labor service. Create a work order, book it, then move the booking through Traveling, In Progress and Completed and watch the work order system status change. Set it to Posted and note what becomes read-only.

Next, create an agreement with a quarterly booking setup and a monthly invoice setup, activate it, and inspect the generated work orders and invoices. This exercise makes the independence of the two recurrences obvious.

Then add the newer features: an inspection template linked to a service task type, an asset-based inspection, a functional location tree with assets underneath, and a property template that logs a meter reading. Finish by reviewing incident type suggestions and Copilot in Outlook in the documentation. Write a status-mapping table on one page and test yourself on it until you can predict every roll-up without looking.

FAQ

How much of MB-240 was Manage work orders and customer assets?

Manage work orders and customer assets was 25–30% of the final outline, the largest single domain.

Can I add a new work order system status?

No. System statuses are fixed. Create a work order sub-status and map it to the system status it belongs under.

What does an incident type add to a work order?

It adds its service tasks, estimated products and services, characteristics and estimated duration, and can supply a requirement group template for multi-resource jobs.

Why is my agreement not generating work orders?

Check that the agreement is Active, that the booking setup has auto-generate enabled with a valid recurrence, and how many days in advance generation is set to run.

What is the difference between a customer asset and a functional location?

A customer asset is a piece of equipment with service history. A functional location is a place, such as a site, building or room, where assets are installed.

How are inspections added to a work order?

Link a published inspection template to a service task type. When that service task is added, directly or through an incident type, the inspection comes with it.

Other CRM & Business Applications certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 2 knowledge

You have covered work order lifecycle, incidents, agreements, inspections and customer assets. Practice predicting statuses and generated records before moving on.

Take the MB-240 practice test Check your MB-240 readiness

Keep going