A busy service day can become difficult to control when new calls, schedule changes, and unassigned jobs are spread across different screens or handled informally. The dispatch board workflow gives the office one repeatable process for seeing what needs attention, assigning work, and keeping job information current.
The goal is not to fill every available space as quickly as possible. It is to maintain an accurate operational picture: which jobs are waiting, which are assigned, what has changed, and what still needs an office decision. The steps below are vendor-neutral because dispatch board layouts and status labels vary across field service platforms.
What a dispatch board workflow is for service businesses
A dispatch board is the office hub for coordinating scheduled and unscheduled work before and during the service day. It normally brings together jobs, dates, time windows, assigned team members, and operational statuses. Some products call it a schedule board, calendar, job tray, queue, or dispatch view.
Official product documentation reflects this central role. ServiceM8 describes its dispatch board overview as the place where jobs can be queued or scheduled, including work that still requires action. ServiceTitan separately documents a daily dispatch board used to schedule and assign work.
Board visibility and job assignment are related, but they are not always the same action. A job might be visible in an unassigned queue without appearing under a technician. Depending on the platform, assignment may involve dragging the job onto a technician’s schedule, opening it and selecting an assignee, or using another scheduling control.
A useful workflow therefore answers five questions throughout the day:
- What work is still unassigned?
- Which jobs are ready to be scheduled or dispatched?
- Who is responsible for each assigned job?
- Which jobs have changed or need another office decision?
- Is the board showing the correct date, view, and filters?
Dispatch is one part of the broader calendar process. Businesses still defining their overall setup can use this guide alongside an overview of scheduling software for contractors, without turning the daily board into a software-selection exercise.
How to handle unassigned work first
Start each dispatch review with the unassigned tab, tray, queue, or equivalent holding area. Unassigned jobs may not appear in the main technician view, so scanning only the visible schedule can create the false impression that all work has been handled.
1. Confirm that the queue is showing the right work
Check the board date, selected view, and active filters before making assignment decisions. Confirm that the queue includes the relevant service area, team, business unit, job type, or other categories used by your system. The exact filter choices vary by platform.
2. Review whether each job is ready for assignment
An office team can sort each unassigned job into one of three practical groups:
- Ready to assign: The job has enough scheduling information for the dispatcher to choose an appropriate team member and time.
- Needs an office decision: A time, assignee, job detail, or internal approval still needs clarification.
- Hold for later review: The work should remain visible but should not yet occupy a confirmed schedule position.
Use a queue, hold state, alert, or other visible marker for the second and third groups. Avoid moving unresolved jobs into personal notes or an untracked message thread, where the rest of the office may not see them.
3. Assign the job using the supported board action
When the job is ready, assign it to the selected technician or crew. Drag the job onto the appropriate schedule when the platform supports drag-and-drop assignment. Otherwise, use the product’s equivalent assignment action. Do not assume that moving a visual card always changes the underlying assignee; verify that the job now appears in the intended schedule position.
4. Check for conflicts before confirming the placement
Review the assigned person’s existing jobs, working hours, appointment windows, and any operating buffers maintained by the business. If schedule overlap is a recurring problem, establish separate double-booking safeguards rather than relying on the dispatcher to notice every conflict manually.
How to keep the board accurate during the day
A dispatch board is useful only when its statuses reflect what the office currently knows. If completed work still appears open or changed jobs remain in their original positions, dispatchers and CSRs begin making decisions from stale information.
Use a small, clearly understood status sequence. For example, a business might distinguish among work that is unassigned, scheduled, dispatched, in progress, on hold, and complete. These are workflow descriptions rather than universal product labels; the terms and available states vary by vendor.
| Workflow point | Office action | Question to answer |
|---|---|---|
| Unassigned | Review and place in the correct triage group | Is this job ready for assignment? |
| Scheduled | Confirm the assignee and schedule position | Who owns the job, and when is it planned? |
| Dispatched or released | Update the board when the work is handed off | Has the field team received the assignment? |
| Working or in progress | Keep the status current as reported | Is the job actively underway? |
| Hold or exception | Record an office-facing reason and next review point | What decision is still outstanding? |
| Done | Clear it from active dispatch attention | Does the office still need to act? |
Update the board when the work changes, not just at the end of the day. A cancellation, delay, reassignment, or newly available opening can affect later decisions. The person who receives the change should either update the record or hand it directly to the team member responsible for doing so.
Maintain one visible exception queue for jobs that cannot proceed normally. Each item should show an owner and a next action, even if the software does not provide dedicated fields for both. This keeps unresolved work separate from jobs that are genuinely ready for assignment.
What to check when jobs seem to be missing
Do not immediately recreate a job that appears to be absent. It may be sitting outside the current view rather than actually missing. ServiceTitan’s official dispatch board FAQ specifically documents the importance of the selected date and filters, as well as the separate treatment of unassigned work.
- Confirm the date. Make sure the board is displaying the day on which the job was booked.
- Confirm the view. Check whether the system separates a daily board, calendar, technician view, or unassigned area.
- Clear or review filters. A technician, team, category, or other active filter may hide booked work.
- Open the unassigned queue. Jobs without an assignee may remain outside the main schedule.
- Check access permissions. Permissions can limit who may view, assign, or edit jobs.
If the record is found, correct its date, assignment, or status through the normal workflow rather than creating a duplicate. Exact controls differ by vendor and may also differ by the configuration or product access available to the user.
A simple office workflow for dispatchers and CSRs
Small teams do not need a complicated dispatch manual, but they do need clear ownership. The following routine can be adapted for an owner-dispatcher, a dedicated dispatcher, or a shared CSR team.
Morning board review
- Open the correct date and confirm the board’s view and filters.
- Review the unassigned queue before scanning technician schedules.
- Identify jobs ready for assignment, jobs needing a decision, and jobs remaining on hold.
- Assign ready work and verify that it appears under the intended person.
- Check that active jobs have understandable statuses and that exceptions have an owner.
Same-day intake and handoff
When a CSR adds new work, the record should enter the shared unassigned queue unless assignment is part of the CSR’s role. The dispatcher then reviews it against the current board and either assigns it, places it in a visible hold state, or returns it for missing information.
Define one handoff rule so responsibility is clear. For example, the CSR owns information capture until the job enters the queue; the dispatcher owns assignment and schedule placement; and the designated office user owns status corrections when field updates arrive. In a very small business, one person may perform all three roles, but the sequence should remain consistent.
Midday control check
- Review unassigned and exception queues again.
- Confirm that completed or changed jobs are no longer shown in stale states.
- Recheck jobs affected by cancellations, delays, or reassignments.
- Verify the date and filters before treating any job as missing.
End-of-day cleanup
Review every job left unassigned or on hold. Decide whether it should remain visible for the next day, return to an office review queue, or receive a confirmed schedule position. Record the next action and owner so the following morning does not begin with unexplained leftovers.
Dispatch board operating checklist
- The board is open to the correct date and view.
- Active filters are understood.
- The unassigned queue has been reviewed.
- Every ready job has a confirmed assignee and schedule position.
- Every unresolved job remains in a visible queue or hold state.
- Current statuses match the latest information available to the office.
- Same-day changes have been reflected on the board.
- Permissions allow the responsible office users to perform their assigned actions.
- End-of-day exceptions have an owner and next step.
A reliable dispatch board workflow is less about a particular screen layout and more about disciplined visibility. Check unassigned work first, assign through the supported action, update statuses as the day changes, and verify dates and filters before assuming work has disappeared. If the current system cannot support that basic operating model, the next step is to assess the assignment and visibility capabilities described in this dispatch software guide.
Frequently asked questions
What is the first thing to check on a dispatch board?
Start with the unassigned queue or its equivalent. Then confirm that the board is displaying the correct date, view, and filters before assigning work or concluding that a job is missing.
Why do jobs disappear from the dispatch board?
A job may be hidden by an active filter, displayed on another date or view, or held in a separate unassigned queue. User permissions can also limit visibility or prevent assignment and editing actions.
Should every dispatch board use the same status labels?
No. Platforms use different labels and layouts. Establish a shared operational meaning for stages such as unassigned, scheduled, dispatched, working, hold, and done, then map those stages to the statuses available in your system.