- Spot hazards from the ticket, the last visit, and a direct question to the customer before dispatch.
- Assess each hazard for likelihood and seriousness, and mark anything you cannot judge as unknown.
- Control each hazard in order: eliminate it first, control the risk only if it stays.
- Write the assessment and the control in plain words on the ticket, dated, where the tech will read it.
- Close the loop after the visit so a missed hazard improves the next review.
Dispatchers and team leads often decide what a technician must review before a field visit. That decision happens in the gap between a work order arriving and a truck rolling out. If the review is thin, the tech arrives with questions nobody asked. If the review is heavy, every job slows down and people start skimming. You need a way to decide what goes into the review that is simple enough to repeat on every ticket.
This post uses three steps: spot the hazards, assess the risk, and control it before the visit. The structure follows hazard identification guidance from the Canadian Centre for Occupational Health and Safety (CCOHS). That guidance describes a method. It does not tell you what a review must contain for your own jobs, so you still need your own site knowledge and the rules that apply where you work.
Run the three steps in order. Each one feeds the next, so a hazard you skip in step one cannot be assessed or controlled in steps two and three.
Key Takeaways
Step one: spot the hazards before the tech leaves
Spotting means identifying hazards before anyone is on site. (CCOHS, Hazard and Risk - Hazard Identification)
The office has more information than it may seem. Start with the ticket itself. Read the task description, the equipment named, and any access notes. Compare the ticket with the last visit to the same address, and look for changes: a new tenant, a new machine, a different type of job. Ask the customer what has changed since the last visit, and write the answers down so the tech sees them.
Some hazards are easy to miss from a desk, so ask about them directly. Confined spaces, roof or ladder access, electrical panels, animals on the property, and locked gates or blocked driveways all need a direct question. Write what you learn in plain words on the ticket. "Possible trip hazard in the basement, stairs unlit" is more useful than "site hazards: see notes."
Ask the same kinds of questions about the people, not just the place. Who will be on the job, how long they have worked on this type of equipment, and whether they have been to this address before all shape what they need to see. A tech who has never been to the site may need the access notes and the hazards written out in more detail than a tech who knows the building well.
A hazard on the list is not yet a judgment. That work belongs to the next step, and it is easier when the list is complete and specific.
Step two: assess the risk of each hazard
Assessing comes after spotting. CCOHS describes it this way: "Analyze and evaluate the risk associated with that hazard (risk analysis, and risk evaluation)." The guidance names two parts, analysis and evaluation. Look at the risk first, then decide what it means for the visit as it is planned.
A simple way to start is to ask two questions about each hazard on your list: how likely is it that someone gets hurt, and how bad could the injury be? Write short answers, such as "likely, minor" or "unlikely, serious." This is a general approach and not a rule from CCOHS. Your team may use a different scale, and that is fine as long as everyone reads it the same way.
Keep the assessment tied to the actual task. A hazard that matters for a rooftop repair may matter far less for a bench check. If the ticket says the tech must work close to a live panel, the same hazard carries more weight than it would if the tech only reads a meter from a distance. The assessment should describe the job as it will really be done, not the job as it looks on paper.
The same hazard can call for a different assessment depending on who will be exposed to it and how they will work. A hazard that a tech handles every week still needs a note on the ticket, because the question is what happens on this visit, not what happens in general. Write the assessment for the people who will read it. If the tech will read the note in the truck, keep it short enough to read there.
If you cannot tell how serious a hazard is, do not guess quietly. Mark it as unknown on the ticket and send it to someone who can judge it. An unknown that is written down can be resolved. An unknown that is left out will surface on site.
Treat the assessment as something you revisit. When new information arrives, from the customer, from an earlier tech's notes, or from a change in the equipment itself, re-check the affected hazards before the next visit.
Step three: control the risk before the visit
Controls are the decisions that reduce risk before the tech arrives. CCOHS puts it this way: "Determine appropriate ways to eliminate the hazard or control the risk when the hazard cannot be eliminated (risk control)." The order in that sentence matters. First ask whether the hazard can be eliminated. Only when it cannot should you look at ways to control the risk.
Source: CCOHS, Hazard and Risk - Hazard Identification
| Step | What the CCOHS guidance says |
|---|---|
| 1. Spot | Identify hazards and risk factors that have the potential to cause harm |
| 2. Assess | Analyze and evaluate the risk associated with that hazard |
| 3. Control | Determine appropriate ways to eliminate the hazard, or control the risk when the hazard cannot be eliminated |
Dispatchers have several levers, and the right one depends on the hazard. Here are some examples to consider:
- Remove the hazard from the job. Ask the customer to clear the access route, or move the visit to a time when the condition is not present.
- Reduce the risk if the hazard stays. Assign a second person, send a tech with the right training, or hold the job until the right equipment is available.
- Write the control on the ticket. A control the tech never sees does nothing. Put it in plain words where the tech will read it before leaving.
- Escalate what you cannot control. If no suitable control comes to mind, send the question to the team lead rather than sending the tech in with an open problem.
Before you record a control as settled, check that it fits the job. A control that needs a second person works only if that person is actually free for the visit. A control that needs special equipment works only if the equipment is on the truck or will be there when the tech arrives. Record each control with the detail the tech needs to follow it: who is responsible, what is needed, and what to do if the condition is different on arrival.
Worked example: one ticket through all three steps
A ticket asks for a bench check of a rooftop unit's control board. Spotting turns up two hazards on the note: roof access by a fixed ladder, and a live panel inside the unit. Assessing marks the ladder as unlikely but serious if a fall happens, and the panel as likely but minor with a meter read from a distance. For control, the ladder hazard cannot be removed, so the ticket assigns a second person for the climb; the panel hazard is reduced by scheduling the read before the unit is opened. Both controls are written in plain words with the responsible name and a date, and the tech is asked to confirm them before leaving the yard.
Bring in people who see the job differently
A review can benefit from people who know the site and people who do not. CCOHS says that "it may help to work as a team and include people familiar with the work area, as well as people who are not." The guidance adds that this gives you "both experienced and fresh eyes." CCOHS makes this point about inspections, and the same idea fits a pre-visit review.
In practice, this can mean a dispatcher reviewing a ticket with a senior tech who knows the territory, then asking a newer tech to read the same ticket cold. The newer tech knows less about the site, so they may ask about things the experienced tech has stopped noticing. Both views go on the ticket.
You do not need a formal meeting for every job. Match the team involved to the job. A routine service visit to a known site may need only a quick check. A job with several hazards on an unfamiliar site may justify a fuller review with more people.
Keep the review current when safety information changes
This rule applies to employers under California's standard. It is not a general rule for every state or country, and it does not set the rules for your dispatch desk. The useful lesson for dispatchers is a general one: when new safety information arrives, re-check the reviews that depend on it, and make sure the tech sees what changed.
Build that re-check into your routine. When a new or revised safety document reaches your desk, find the tickets that cover the same product or equipment, and update their hazard notes. Then confirm that the tech on each job has the updated notes before the visit, not after it.
Write the date of each update on the ticket next to the change. A note that says what changed and when makes it easy for the tech and the team lead to see whether a review is still based on the current information. Without that date, a reader cannot tell an old note from a new one.
Hand the review to the tech clearly
A review helps only if the tech reads it before leaving the yard, so make the handoff part of the dispatch and not an extra step. Put the hazard list, the assessment notes, and the controls in one place the tech can find on a phone or in the truck. Keep the wording plain, and avoid pointing the tech to three different documents for one job.
Ask the tech to confirm they have read the notes, and make it easy to ask questions before the visit. A question that gets answered at dispatch costs less time than one that gets asked at the door of a customer's building.
Close the loop after the visit. If the tech finds a hazard the review missed, or a control that did not fit the job, have them report it back so the ticket and the team's notes can be updated. That loop is what turns one review into better reviews for the next visit to the same site.
Mistakes that weaken a review
A review is most useful when it is specific, current, and short enough to read. Several habits work against that, and each is easy to fall into when the schedule is tight.
- Writing vague notes such as "see site" or "use caution," which tell the tech nothing about what to do.
- Copying an old review forward without checking whether the site, the equipment, or the access has changed.
- Listing hazards without any assessment, so the tech cannot tell which one matters most.
- Recording a control that nobody on the team can actually provide on the day.
- Leaving out unknowns instead of marking them, which hides the questions the tech needs to ask.
Each of these mistakes can be caught with the same quick check: could a tech who has never seen this ticket act on it safely? If the answer is no, the review needs more work before it goes out.
A checklist for your next dispatch
Use this checklist on each ticket before you assign it. It follows the three steps and adds the team and update points.
- Read the ticket and note the task, the equipment, and any access details.
- Compare the ticket with the last visit to the same site, and ask the customer what has changed.
- List each possible hazard in plain words on the ticket.
- For each hazard, write a short note on how likely harm is and how serious it could be.
- Mark any hazard you cannot judge as unknown, and send it to a person who can.
- Ask whether each hazard can be eliminated. If it cannot, choose a control and write it on the ticket.
- Involve someone familiar with the site and, when the job warrants it, someone who is not.
- Re-check the review when new information arrives, and confirm the tech has the latest notes before the visit.
Your next step today
Take one live ticket and run it through the three steps before it dispatches: list the hazards in plain words, note how likely and how serious each one is, then write the control. For a matching handoff structure, see the Field Service Work Order Checklist for Dispatch Handoffs at /manual/field_service_work_order_checklist/.
Related guides: Backing 5% VAT out of a £483 price before a job is billed · Confined space hazards: 4 checks before dispatch · 5 invoice items to include before handing over a repair job.
Frequently asked questions
What are the three pre-visit hazard steps? Spot the hazards, assess the risk on each one, then control it, in that order.
Who should run the review? The dispatcher or team lead who receives the work order, with a second reader when the job or site warrants it.
What if a hazard cannot be judged? Mark it as unknown on the ticket and route it to someone who can judge it before the visit.
Does the 30-day rule apply to my team? That timing applies to employers under California's standard; check the rules where you work and your own company procedures.
Where this guidance stops
This guidance stops short of setting a review list or a time limit. The CCOHS guidance used here describes three steps: identify hazards, analyze and evaluate their risk, and determine ways to eliminate or control them. It does not set a required review list for any job type, and it does not give a time limit for a pre-visit review. The California rule covers one timing for updated safety data sheets, and only for employers under that state's standard.
Before you set a standard for your team, check the rules that apply where you work and your company's own procedures. Then use the three steps to make those rules practical on each ticket. A short, specific review that the tech actually reads will do more good than a long one that nobody opens.