What a field service dispatch board should help you decide
A dispatch board brings the day's work and the people available to perform it into one planning view. The important questions are practical: which jobs need an owner, which appointments are already committed, where time is available and what changed since the last review. The board is useful when it helps the dispatcher make those decisions from the job record instead of reconstructing them from separate messages.
WorkOrderPro's dispatch workflow uses work orders, assigned technicians and scheduled times. The board includes an unassigned queue, technician rows and job details. It also surfaces scheduling overlaps and available location context. These elements support the dispatcher's judgement; they do not remove the need to confirm access, travel time, relevant skills or the actual state of a job before promising attendance to a customer.
For a South African plumbing, electrical, HVAC, repair or maintenance business, the first improvement may simply be a consistent daily review. Decide who owns the board, when appointments become commitments and who can change an assignment. A clear operating rule is as important as a useful screen. If the office and technicians continue maintaining conflicting private schedules, the shared board will not represent the whole operation.
Dispatch, scheduling and routing answer different questions
Scheduling establishes when work should happen. Dispatch assigns responsibility and gives the field team the information needed to act. Routing considers how people travel between locations. These activities influence one another but should not be treated as interchangeable. A free calendar slot does not prove that a technician can reach the site in time, and a nearby map marker does not prove that the person has the required equipment.
Use the dispatch board to review the planned job and assigned person. Use location context carefully, checking when the position was recorded. Allow time for travel, parking, building access and preparing the work area. Where a separate routing or navigation capability is essential, demonstrate that requirement during the trial rather than assuming that a calendar assignment also creates a fully optimised travel plan.
Start the day with the unassigned work queue
Review requests that have not yet been placed with a technician. An unassigned job may be ready to schedule, waiting for approval, missing an address or dependent on a part. Those situations need different next actions. Read the job details before placing every item into the next visible opening. A full calendar can disguise unresolved preparation rather than represent a workable day.
Check the customer, job site, problem description and contact information. Clarify whether the customer has agreed to an appointment or only requested help. Establish whether the job is an inspection, a repair with an agreed scope or follow-up work from a previous visit. Assigning a vague request can move uncertainty from the office to the technician without resolving it.
Keep the queue review focused on decisions. If a job needs approval, identify the person who will obtain it. If the appointment cannot be confirmed, record the next action in the job's working process. If the correct technician is unavailable, consider a later slot rather than making a promise that depends on an unrealistic reassignment. The objective is to create a schedule the team can execute.
Check the information that affects attendance
| Dispatch input | Question to resolve | Consequence if overlooked |
|---|---|---|
| Job site | Is this the correct property and access point? | The technician may travel to the wrong location |
| Contact | Who can grant access during the appointment? | A scheduled visit may become an unsuccessful attendance |
| Scope | Is the task diagnostic, approved work or a return visit? | The team may arrive with the wrong expectations |
| Skills | Does the assigned person have the relevant capability? | Proximity may be mistaken for suitability |
| Parts and tools | Is anything required before departure? | Work may stop shortly after arrival |
| Duration | Is the allowance realistic for the known scope? | Later appointments may become impossible |
| Customer commitment | What time or window has actually been agreed? | Internal planning may be confused with a customer promise |
Assign jobs with realistic durations and ownership
The drag-and-drop workflow lets the dispatcher place a work order into a technician's schedule. Review the intended person and time before treating the placement as confirmed. Open the resulting job record where necessary and verify that the assignment saved. A temporary visual movement during a network request is not the same as a successful server response.
Estimate duration from the task and known conditions. A routine service with a clear scope differs from an unexplained fault. A new installation may involve preparation and testing that should not disappear from the schedule simply because the physical fitting looks straightforward. Where uncertainty is high, leave enough flexibility for the dispatcher to respond without moving every later appointment.
Use one clear owner for each assignment decision. If two office users dispatch at the same time, one may be working from an older view of the job. WorkOrderPro can report that another dispatcher changed the record and reload current information. When that happens, review the saved assignment before trying again. Do not repeatedly drag the same card until the display happens to match your earlier expectation.
Treat overlap warnings as decisions to review
An overlap warning identifies work scheduled for the same technician during conflicting times. It is a prompt to examine the plan. Determine whether a duration is wrong, a job belongs to someone else or an appointment needs to move. Contact the relevant people through your established operating process before changing a customer commitment.
The dispatch workflow includes an intentional override path for a conflict. That means the correct description is overlap detection and review, rather than a guarantee that double-booking can never happen. If your business permits an override, define the situations in which it is acceptable and who is responsible for checking the consequences. Do not make overriding warnings the normal way to fit an overloaded day onto the screen.
A schedule can also be impractical without a literal time overlap. Two jobs may touch at the same boundary but be far apart. A technician may need to collect a part between visits. A commercial site may require a lengthy access process. Review those gaps as part of dispatch planning. A calendar represents the times entered into it; it cannot establish that every operational assumption behind those times is correct.
Work through common scheduling exceptions
| Situation | First check | Dispatch response to evaluate |
|---|---|---|
| Urgent callout arrives | Urgency, required skill and current commitments | Review a suitable available technician and the effect on later appointments |
| Existing job runs late | Remaining work and realistic completion estimate | Revisit affected assignments and customer expectations |
| Customer cannot provide access | Confirmed contact and alternative window | Record the reason and arrange the next appointment |
| Part is unavailable | Whether any useful work can proceed | Separate today's attendance from the return visit |
| Technician becomes unavailable | Jobs affected and required capabilities | Reassign deliberately rather than moving the whole list blindly |
| Two dispatchers edit one job | Current saved assignment and modification warning | Reload and reconcile the intended change |
| Location update is old | Timestamp and connection conditions | Confirm availability through the job record or your operating process |
Use skills and location together for urgent callouts
The closest person is not always the person who should attend. Start with what the callout requires: knowledge, equipment, site access and enough time to perform the task. The board supports filtering technicians by recorded skills. Keep those records current and use them as an aid to selection. A skill entry in software is not independent verification of a professional qualification or authority to perform regulated work.
Then review the technician's current schedule and available location information. Check the timestamp attached to location data. Devices can lose connectivity, permissions can change and a person may have moved since the last update. Avoid presenting an old point on the map to a customer as a live arrival estimate. The job assignment and the person's actual readiness both need attention.
For businesses covering several suburbs or towns, group work where practical without overlooking customer windows. A Johannesburg team may need to account for very different journeys within the same day; a contractor covering rural sites may need much larger travel allowances. Use your own operating experience and observed travel requirements. This page does not assume that one city's name produces a reliable duration or a universal dispatch rule.
Handle return visits without losing the original context
A return visit should make the remaining work understandable. Identify why the first attendance did not finish the assignment, what has already been completed and what is needed next. Keep the relevant customer and site context available so the next technician does not begin with a blank description. If the scope has changed, establish whether further approval is needed before scheduling additional work.
Distinguish a planned second visit from a service problem that needs investigation. A repair waiting for a replacement component is different from a customer reporting that completed work has failed. Your job descriptions and office process should preserve that distinction. Otherwise, repeat visits can look like ordinary new work and hide the reason the team is returning.
Review the invoice implications separately from dispatch. Attendance on the calendar does not establish that the entire job is complete or that every proposed charge is authorised. The office needs a consistent handover from the technician's record to the billing review. Explore time tracking, job photos and the invoicing guide as connected parts of that handover.
Keep the board useful as the day changes
Choose a small number of review points that fit the way your team works. An opening review can address unassigned work and known constraints. A later review can focus on delays, changed scope and new callouts. The final review can identify jobs awaiting completion information and work that needs a clear next action tomorrow. These reviews should use the job records, not create another independent schedule.
Connected updates help the office follow progress, but the displayed state still depends on saved information and connectivity. If a technician has not recorded a change, the office may need to confirm the situation. If the board appears stale, refresh and check the relevant record before acting. Avoid equating an attractive real-time display with certainty about every person and job.
Keep exception communication concise. State the job reference, what changed, the decision required and the person responsible. Do not bury a new appointment among unrelated messages. When your normal communication channel is used to agree a change, make sure the authoritative job record reflects the outcome. The purpose of the board is to make the next decision easier for the whole authorised team.
Evaluate dispatch software with a realistic trial
Create a small set of representative work orders using test information. Include one unassigned request, an agreed appointment, a longer job and a return visit. Use two technicians with different recorded skills where that reflects your business. Ask the person who normally dispatches to assign the work without someone else controlling the screen. Observe which details they need and where they hesitate.
Try an overlap deliberately with test jobs and inspect the warning and override behaviour. Move a job to a different time, change the selected date and check that the resulting assignment is correct. Ask a second authorised office user to view the same work. The evaluation should establish that people can understand the saved schedule and recover from a failed or conflicting change.
Test the field handover as well. Verify how the assigned technician finds the job, which details are available and how a recorded update appears to the office. Use the actual device and connectivity conditions you expect to support. The web dispatch board requires a connection; confirm mobile release availability and the supported behaviour of each field action before making offline operation part of your rollout plan.
Measure outcomes your business can observe
Choose measures tied to the problem you are solving. Count unassigned jobs that are ready for scheduling, appointments moved because preparation was missing, or jobs whose next action cannot be identified. Review how often dispatchers need to ask for information already expected in the job record. These observations are more useful than assuming a fixed percentage improvement from installing software.
Compare similar working periods and record changes in workload or staffing that could explain the result. A quieter week may make scheduling look better even if the process has not improved. Treat trial findings as evidence for your own buying decision, with limitations recorded. WorkOrderPro does not guarantee that every business will save the same number of hours or complete a specific number of additional jobs.
Choose a plan and rollout process for the whole team
The dispatch board is configured as an included feature in Starter, Professional and Enterprise. Compare the active-user limits and the other capabilities your operation needs before selecting a plan. Include active administrators and dispatchers in the headcount alongside technicians. The pricing calculator shows how the base fee, active users, billing cycle and VAT affect the subscription estimate.
Start rollout with a clear owner, a small group and agreed minimum job information. Decide how appointments are confirmed, who can override a conflict and how the office handles incomplete field updates. Review a normal day and an interrupted day before broadening use. If a particular scheduling requirement remains uncertain, request a demo using that scenario rather than assuming a generic feature label answers it.