1. Confirm the numbers before comparing technicians.
Use the same reporting period and confirm what each field means. For conversion rate, identify which calls count as eligible opportunities. For callbacks, agree on what qualifies as a return visit. Check the number of calls behind each percentage. A missing value should prompt a question rather than a zero score.
2. Choose one gap and review the calls behind it.
Compare results with your company’s targets. Then look at call type, job complexity, and a few relevant work orders. A lower average ticket or conversion rate alone does not explain why the result occurred. Avoid judging a technician only by their position in a ranking.
3. Ask the technician what happened.
Discuss individual performance privately. Start with specific examples and ask which part of the work felt difficult. Listen before choosing training. Use the team meeting for shared learning without putting a struggling technician on display.
4. Agree on one action you can observe.
Make the action concrete: review diagnostic steps with a mentor, practice explaining repair options, or use a completion checklist on suitable calls. Name who will help and set a follow-up date. Keep the focus on work and the support needed to improve.
5. Check follow-through and the next set of results.
At the next review, ask whether the agreed action happened and inspect examples. Compare results over a suitable period and account for changes in call mix or workload. Recognize progress and adjust the plan when the evidence points elsewhere.
A fictional callback example
A technician has 3 callbacks across 50 completed calls: 6%, compared with a company target of 3%. That gap is a starting point for review, not proof of poor workmanship. The manager checks each return visit and confirms which ones qualify under the company definition.
If the review finds an incomplete final check, the action might be to practice the completion checklist with a mentor and review the next five suitable jobs together. Set a follow-up date and continue tracking callbacks. If the visits have another cause, choose a different action.
Keep the weekly coaching note simple.
- Observation: The metric, reporting period, call count, and relevant examples.
- Context: What the manager and technician confirmed together.
- Action: One practical behavior to work on.
- Support: The manager, mentor, or training resource that will help.
- Follow-up: A date and the work you will review.
Where SMM fits
SMM’s technician performance software helps organize KPIs and performance gaps. Professional and Business add saved Coaching Action Plans. The manager supplies the context, leads the conversation, and follows through.
If you want help reviewing reports or developing management priorities, explore monthly reporting and remote HVAC service management consulting.