Contoso Field Services: Incident Types, Requirement Groups, and Emergency Dispatch

Start by checking whether the work order actually has the incident type applied. Requirement groups attached to an incident type are only copied to the work order when the incident type is added, either through the Incident Type field or the Add Incident Type action. Portal-created and flow-created work orders often skip this step, so no requirement group is generated and the Schedule Assistant has nothing to enforce. Next, verify the incident type's requirement group: open the requirement group detail and confirm the EPA characteristic is present with the correct rating, such as Proficient or Qualified. Confirm the same characteristic exists on the bookable resource records for the 12 certified technicians and that the rating matches. Check Field Service settings for requirement group usage, and review Booking Setup fulfillment preferences to ensure the Schedule Assistant is using required characteristics rather than allowing any resource. Also check whether crews or pools are being used, because a crew booking can bypass individual characteristic checks if the crew itself lacks the characteristic. The most likely root cause is that work orders created through the portal or Power Automate do not have the incident type applied. Fix the flow to add the incident type explicitly, or set a default incident type on the work order type, then retest with the Schedule Assistant and Schedule Board.

Configure the work order type and incident type so emergency work orders carry a two-hour time window, the EPA certification characteristic, and a territory requirement. On the bookable resource side, assign each technician a territory and the EPA characteristic with the correct rating. In Booking Setup, set the fulfillment preference to restrict to territory and require characteristics so manual and assisted scheduling cannot bypass the rules. For automation, use a Power Automate flow triggered on work order creation that checks priority. For near-real-time dispatch, call the scheduling action or API from the flow to attempt a booking against the requirement, and log exceptions for the dispatcher. As a backstop, run Resource Scheduling Optimization on a short interval, such as every 15 minutes, with a scope limited to emergency work orders. In the RSO goal, treat the two-hour time window and territory as hard constraints, treat the EPA characteristic as a resource restriction, and minimize travel. Make sure the work order has a service account, territory, and priority populated before scheduling runs. Use booking alerts and a separate flow to notify dispatch when an emergency work order remains unbooked after one hour.

Use out-of-the-box Field Service security roles as the baseline. Assign dispatchers the Field Service - Dispatcher role, which includes booking and schedule privileges. Assign technicians the Field Service - Resource role, which should not include create, update, or delete privileges on bookable resource bookings or the ability to override requirements. If technicians need to view their bookings, grant read-only access. For the override itself, restrict edit rights on the requirement group and related characteristic records so only dispatchers can change them. Use field security profiles for sensitive fields if needed, and use business rules to lock the requirement fields after the work order is created. Audit override actions by enabling auditing on the work order and booking entities. In the Field Service mobile app, assign an app module that exposes only the technician's own bookings and work orders. Test by signing in as a technician and confirming the Schedule Board or booking form does not allow changing the certification requirement or booking an uncertified resource.