Microsoft Dynamics 365 Field Service · Project & Crew Dispatching
Crew & project dispatching for Dynamics 365 Field Service — the work RSO tells you to exclude.
Project-based dispatching is the documented edge of Dynamics 365 Field Service scheduling: Microsoft’s own configuration guidance is that native Resource Scheduling Optimization doesn’t consider Pool or Crew resources at all. FieldCamp’s AI Dispatcher works on top of D365 FS and plans that work natively — multi-day phase schedules with dependencies, crews matched by role and certification, shared equipment conflict-checked across jobs.
No rip-and-replace — Dynamics 365 stays your system of record. FieldCamp dispatches the crews and projects on top of it.
01 Crews & shared equipment
A crew isn’t four separate bookings. Stop scheduling it like one.
In Dynamics 365 Field Service, a crew is a container resource whose member bookings the system keeps in sync — and booking a job to a single crew member affects the availability of the entire crew. Native RSO doesn’t optimize crew resources at all, so the plan for a four-person, one-crane project lives in a dispatcher’s head.
FieldCamp models the crew as real people: every member matched by role and certification, and shared equipment — a crane, a lift, a test rig — held as a bookable row that’s conflict-checked against every other job that wants it.
Source: Microsoft Learn — Schedule crews in Dynamics 365 Field Service
02 Phase gates & dependencies
Day 3 doesn’t start because the calendar says so. It starts because day 2 passed.
Multi-day projects fail in a specific way: a crew rolls to a site where the previous phase isn’t finished — the inspection hasn’t passed, the sign-off hasn’t landed — and a full crew-day is burned. A booking on a board can’t know that.
FieldCamp plans phases with real dependencies and gates between them. Day-3 dispatch stays held until the day-2 gate clears — inspection passed, punch list closed, customer signed — and the moment it does, the next crew and the equipment release automatically. No tech rolls to a site that isn’t ready.
03 Mid-project changes
A five-day plan meets day two. Somebody always calls in sick.
In native D365 FS, the Crew Allocation tool swaps crew members one day at a time — for anything longer, Microsoft’s guidance is to edit the crew resource directly, and membership changes cascade asynchronously through the bookings.
FieldCamp treats a mid-project change as a re-plan, not a data edit: it finds a substitute with the matching license, holds the crane and the customer window, re-sequences only what has to move — and returns the whole thing as a diff you Apply or Discard, with every change explained.
Source: Microsoft Learn — Schedule crews (Crew Allocation tool)
04 What project dispatching includes
Everything a multi-day job needs. Planned like it’s one job.
Multi-day phase planning
Rig, install, commission — phases planned across days with real dependencies, so a slipped morning doesn't silently break Thursday. The whole project is one plan, not five disconnected bookings.
Crew dispatching by role & certification
Every crew slot matched on role, license and certification — lead installer, journeyman electrician, commissioning tech — with the reasoning and a confidence score shown per assignment.
Shared equipment conflict-checking
Cranes, lifts and test rigs held as bookable rows and checked against every other job that wants them — a double-booked crane is caught at planning time, not at the site gate.
Phase gates that hold dispatch
Inspection passed, punch list closed, sign-off landed — the next day's crew and equipment stay held until the gate clears, then release automatically.
Mid-project re-planning
A sick tech or a weather hold becomes a plan diff, not a manual rebuild: certifications re-matched, equipment holds kept, customer windows protected, Apply or Discard.
Projects and the daily board, together
Project crews and single-visit work orders are optimized as one operation — the crane job doesn't have to live outside the schedule your dispatchers run every day.
05 Where native D365 stops for projects
Microsoft documents the gap. Your project schedule lives in it.
These aren’t opinions — they’re what Microsoft’s own documentation says about crews, pools and projects in Dynamics 365 Field Service, and the reason project-based dispatching is the sharpest gap a third-party dispatch layer fills.
RSO doesn't optimize crews or pools
The resource types RSO considers are Users, Contacts, Accounts, Equipment and Facility — Pool and Crew aren't on the list, and single-resource optimization on the schedule board excludes crews, pools and facilities too. The optimizer that's supposed to build your schedule automatically doesn't cover multi-technician, multi-day work at all. Whatever RSO produces, the project plan still gets built by hand.
Source: Microsoft Learn — RSO optimization goals (considered resource types)
Crew changes are a one-day-at-a-time affair
The Crew Allocation tool swaps crew members for a single day; Microsoft's guidance for anything longer is to edit the crew resource directly. One member's booking affects the availability of the whole crew, and if a leader is moved to another crew they lose leadership status for that day — even if they're moved back. That's resource administration, not project dispatching.
Source: Microsoft Learn — Schedule crews in Dynamics 365 Field Service
Crew booking changes cascade asynchronously — and can misfire
Crew membership changes process asynchronously and bookings "begin to cascade" after the fact — and cascading crew changes when assigning a booking has its own entry in Microsoft's Field Service troubleshooting docs. On a live multi-day project, a schedule you have to wait on and then verify isn't a schedule you can dispatch from.
Source: Microsoft Learn — Troubleshooting: cascading crew changes when assigning a booking
06 The Microsoft cluster
Projects are one door. The whole dispatch day has pages here.
Every scheduling, dispatch and routing question a Dynamics 365 Field Service team asks has its own page in this cluster — each one grounded in what the AI Dispatcher actually does.
Microsoft, Dynamics 365 and Dynamics 365 Field Service are trademarks of Microsoft Corporation. FieldCamp is an independent product and is not affiliated with or endorsed by Microsoft; references are for compatibility and comparison.
07 Project dispatching FAQ
Crews, cranes and phase gates — questions, answered.
What is project-based dispatching in Dynamics 365 Field Service?
Project-based dispatching means scheduling multi-day, multi-technician work — crews, shared equipment and phased tasks with dependencies — as one coordinated plan on top of Dynamics 365 Field Service. It matters because Microsoft's native Resource Scheduling Optimization add-in doesn't consider Pool or Crew resource types, so this work sits outside automated optimization.
Can Resource Scheduling Optimization (RSO) schedule crews or multi-day projects?
No. Pool and Crew aren't among the resource types RSO considers for optimization — the native optimizer doesn't cover crew-based or project work. Crews can be booked manually via the schedule board and schedule assistant, but the optimization engine doesn't plan them.
Microsoft Learn — Configure Resource Scheduling Optimization →
How does FieldCamp dispatch projects on top of Dynamics 365 Field Service?
FieldCamp works with your D365 Field Service data — work orders, bookable resources, requirements — and plans the project as a phased, multi-day schedule: each crew slot matched by role and certification, shared equipment conflict-checked against other jobs, and phase gates holding the next day's dispatch until the site is ready. Dynamics 365 stays your system of record.
How do phase dependencies work?
Each phase — rig, install, commission — declares what it depends on. If a phase slips, only the dependent phases move, and the re-sequenced plan is returned as a diff you Apply or Discard. A weather hold on a crane lift moves the lift, not the whole week.
Can it handle shared equipment like cranes or lifts?
Yes. Equipment is held as a bookable row inside the project plan and conflict-checked against every other job that wants it. If another work order needs the same crane on the same day, the conflict is surfaced at planning time — with the alternative windows shown — not discovered at the site gate.
What happens when a crew member calls in sick mid-project?
FieldCamp re-plans instead of re-administering: it proposes a substitute with the matching license and certifications, keeps the equipment holds and customer windows, and re-sequences only what has to move. In native D365 FS, the Crew Allocation tool swaps members one day at a time; longer changes mean editing the crew resource directly.
Does it replace requirement groups or the schedule assistant?
No — it augments them. Requirement groups and the schedule assistant remain how D365 FS represents multi-resource work; FieldCamp adds the planning layer on top: dependencies across days, certification matching, equipment conflict-checking and phase gates, with the reasoning shown for every assignment.
Do I have to leave Dynamics 365 Field Service to use it?
No. FieldCamp works on top of D365 Field Service — you keep Dynamics as your system of record and add project and crew dispatching on top, with no rip-and-replace and no migration project. It's available on Microsoft Marketplace.
What does it cost?
Book a demo and we'll walk you through it against your own project — your crews, your equipment, your phases.
How do I get started?
Book a demo — bring a real multi-day project, and we'll run it through the AI Dispatcher live: the crew roster, the crane share, the phase gates, the day-2 sick call.
Bring the job RSO couldn’t plan — and watch it become one schedule.
Book a demo. Bring a real multi-day project — the crew of four, the shared crane, the inspection gate, the Wednesday wind forecast — and we’ll run it through the AI Dispatcher live.
No demo deck. Your Dynamics project, our dispatcher.