Published October 27, 2026.
A technician reads the dispatch note in a truck, often with gloves on and the engine running. If the note begins with a long narrative about the caller's day, the technician scrolls to the address and misses the gate code. Good dispatch notes are ordered by what the technician needs first: where to go, how to get in, what is wrong, what is unsafe, and what the customer expects.
Put access before history
The first block should contain the service address, the gate or lockbox code, the parking instruction, and the on-site contact. If the property has a dog, a locked lobby, or a service elevator that requires a key, that belongs in the first block. A technician who cannot get in cannot use the rest of the note.
Verify the address against the client's system, not only the caller's verbal description. Read the street number and the unit number back. If the caller gives a landmark instead of an address, ask for the nearest cross street and record both. For rural properties, add the mileage and the gate description.
Name the problem in the caller's words
Use a short problem statement followed by quoted detail. "No heat on second floor. Caller says the thermostat clicks but the blower does not start." That sentence tells the technician what was observed without diagnosing it. Avoid paraphrases that add a cause the caller did not state, such as "failed blower motor."
Include when the problem started, whether it is intermittent, and what the caller has already tried. A technician who knows the breaker was reset twice will bring a different part than one who assumes a first-time failure.
Flag hazards in a separate field
Hazards should not be buried in prose. Use a visible field with values such as gas odor, standing water near electrical, aggressive animal, hoarding conditions, vulnerable occupant, or prior violence. If a hazard is present, state what the dispatcher told the caller to do and whether emergency services were contacted.
Do not use the hazard field for speculation. "Possible mold" is not the same as "visible mold in the basement." Record what the caller reported and label it as a report.
Capture the customer's expectation
The technician needs to know what the caller was promised: a diagnostic visit, a repair, a temporary fix, or an estimate. Record the arrival window and the price quote if one was given. If the caller was told there would be no charge for the diagnostic, put that in the note. Mismatched expectations cause more complaints than technical failures.
Also record who is authorized to approve work and any dollar limit. A tenant may be home, but the landlord may be the approver. If the approval path is unclear, the technician should call the desk before starting billable work.
Write for the next shift, not only this one
End the note with a disposition: dispatched, scheduled, callback requested, or referred. Add the next action and the time it is due. If the technician has not acknowledged the page, say so. The next dispatcher should not have to infer the state from a timestamp.
Use a consistent field order across clients. The technician may serve three accounts in a day, and a familiar structure reduces scanning time. If a client insists on a different order, keep the same field labels and change only the presentation.
Read the note back to the caller
Before ending the call, read the address, the callback number, the problem statement, and the arrival window. Ask the caller to correct anything wrong. This step catches transposed digits and unit numbers before the technician drives. It also gives the caller a chance to mention the gate code they forgot.
Do not read back a clinical or financial detail that is not needed for the dispatch. Keep the read-back focused on access, safety, and the visit.
Audit notes against outcomes
Sample ten dispatches a week and compare the note with the technician's closeout. Look for return trips caused by a missing access code, a wrong unit number, an unrecorded hazard, or a promise the technician did not know about. Count the causes rather than grading the dispatcher.
If the same field is missing repeatedly, change the form so it cannot be skipped. A required gate-code field is more reliable than a reminder in a team meeting. If technicians ignore a field, ask them which fields they actually use and remove the rest.
Train with a real truck-side review
Bring a technician to a training session once a quarter. Give the group three real notes, one good and two defective, and ask the technician to explain what they would do next. Dispatchers learn quickly when they hear how a missing detail turns into a second trip. Keep the customer information de-identified.
Implementation checklist
- Lead with address, access, and on-site contact.
- State the problem in the caller's words and label any summary.
- Use a separate hazard field with clear values.
- Record the promise, the approver, and the dollar limit.
- End with disposition and next action.
- Read back address, callback, problem, and window.
- Audit notes against technician closeouts weekly.
- Review real notes with technicians quarterly.