Key takeaways
- Review engineers on what customers and the law care about: safe work done with reasonable care and skill[1][2], fixed first time and explained clearly.
- Use a few measures from job data, plus sampled certificates and ride-along observations, not gut feel.
- Customer problems are common in home repair: 11% of people who bought these services had one, with a median detriment of £109 per problem[3][4].
- Hold the review as a conversation: the engineer speaks first, evidence second, agreed actions last.
- Short monthly one-to-ones make the yearly review a summary, not a surprise.
What a review is for
In many small heating firms the only feedback an engineer gets is a phone call when something goes wrong. A performance review fixes that. Done well, it tells engineers what good looks like, recognises the ones who deliver it, catches safety and quality issues early, and links pay and training to something the engineer can see. Done badly, it is a once-a-year argument about callbacks.
The aim is a short, fair, evidence-based conversation, held at least once a year with a mid-year check, and backed by brief monthly one-to-ones.
Keep the paperwork light. A one-page template with the six areas, the evidence, the engineer's comments and the agreed actions is enough. If the form takes longer to fill in than the meeting takes to hold, nobody will keep using it.
The measures that matter
| Area | Measure | Where the data comes from |
|---|---|---|
| Safety | Certificates complete and correct in a random sample; unsafe situations handled to procedure | Monthly sample of certificates; incident records |
| Quality | Callbacks for the engineer's own work within 30 days, as a share of jobs | Job software, callback tags |
| First-time fix | Breakdown jobs fixed on the first visit, as a share of breakdowns | Job outcomes in the diary |
| Customer feedback | Review ratings, compliments and complaints naming the engineer | Review platforms, follow-up calls, complaint log |
| Paperwork | Jobs closed with photos, notes and certificates on the day | Job software completion reports |
| Conduct | Punctuality, van condition, teamwork | Diary times, van checks, colleague feedback |
Six areas is enough. Pick two or three numbers you can measure reliably and judge the rest from sampled evidence and observation. Avoid measures that reward the wrong behaviour: jobs per day alone encourages rushing, and sales per visit can encourage recommending work the customer does not need.
Safety and quality come first
The legal baseline is not negotiable. Gas work may be done only by people in the class approved by the HSE, in practice Gas Safe registered engineers working within their categories[2]. Every contract with a customer to supply a service includes a term that the trader must perform it with reasonable care and skill[1]. A review should therefore check that engineers are working within their certificates of competence, that renewal dates are in hand and that a sample of their safety records is complete and consistent.
Sample fairly. Pick certificates at random each month, look at photos of flues, terminals and data plates, and compare readings with what you would expect. Record what was checked and the result, so the review discusses evidence rather than impressions. Commissioning records are increasingly digital, as Benchmark has moved online and to apps[5], which makes sampling quicker if your systems are set up for it.
Customer feedback
Customers judge engineers on more than the repair: arriving when promised, protecting the home, explaining what was found and what it costs. Problems are not rare in this part of the economy. In the government's consumer protection study, 25% of UK adults had bought home and garden maintenance and repair services, which include plumbing and central heating, in the previous 12 months, and 11% of those buyers had a consumer problem[3]. The median net cost to the consumer of each problem was £109, among the ten highest of any sector[4].
Source: Department for Business, Energy and Industrial Strategy (GOV.UK), 2021[3]
Show the data
| Item | Value |
|---|---|
| UK adults who bought these services in a year | 25% |
| Buyers who had a consumer problem | 11% |
Use feedback carefully. One angry review about price is not an engineer issue. A pattern of comments about mess, lateness or poor explanations is. Collect compliments as diligently as complaints, and share them with the engineer when they arrive, not six months later.
Running the review meeting
Prepare
A week before, send the engineer the measures and the sampled evidence, and ask them to think about what went well, what got in the way and what they want next.
Let them speak first
Open with their view. Most engineers know where they are strong and where they struggle.
Go through the evidence
Share the numbers and the samples. Ask about anything unusual before drawing conclusions; a high callback rate may reflect the jobs they are given.
Agree two or three actions
For example, a ride-along on system boilers, a check of certificate completion for a month, or a new training course.
Talk about the future
Ask where they want to be in a year and what training or responsibility would help.
Write it up
Send a one-page summary within a week, with the agreed actions and the next review date.
Script for a difficult point: 'Four of your last twenty breakdowns needed a second visit. Before we talk about why, how does that compare with how you feel the jobs went? Is there anything about those jobs, the parts or the diary that I should know?'
When the review shows a real problem
Sometimes the evidence shows a serious gap: repeated callbacks on the same type of job, incomplete safety records, or complaints that keep coming. Separate the two kinds of problem. If the engineer cannot yet do the work to standard, that is capability: agree a support plan with training, ride-alongs and a review date, and write down what improvement looks like. If the engineer can do it but will not, such as skipping readings to finish early, that is conduct and belongs in your disciplinary procedure.
Either way, say it clearly in the review and in the written summary. Engineers are rarely helped by softened feedback that hides a problem until it becomes a dismissal. A plain statement, the evidence, the support offered and the date of the next check are fairer to everyone.
Where safety is at stake, act before the review. If a sample shows that an appliance may have been left unsafe, revisit the job straight away and limit the engineer's work in that category until the issue is resolved.
Linking reviews to pay and training
Engineers take reviews seriously when they lead somewhere. Median weekly pay for full-time employee plumbers rose 4.3% in 2026[6], so a review that ends in no movement at all, without explanation, will feel like a pay cut. Keep the link simple: the review decides whether the engineer moves within or between pay bands, and which training the firm will fund next. Separate the pay conversation from the development conversation if you can, so the engineer is not distracted by money while discussing callbacks.
Example: a review summary
Example (fictional): Priya, engineer, two years' service. Safety: twelve certificates sampled, all complete; one missing photo of a flue terminal. Quality: callbacks on 3% of her jobs, below the team average. First-time fix on breakdowns: 82%, slightly below the team; she points out she gets most of the older system boilers. Customer feedback: five reviews naming her, all positive; one complaint about a late arrival caused by an overrun job. Actions: stock of common system-boiler parts added to her van; scheduler to allow longer slots for older boilers; heat pump course funded in the spring. Pay: moves to the top of the engineer band.
Reviewing apprentices and new starters
Apprentices and improvers need different measures. Their reviews should focus on skills gained, college progress, attitude, safety habits and how they work with the engineers they shadow. Callback and first-time fix rates mean little for someone still learning. Ask their buddy engineers for short written notes before each review, and set targets around the next skill to be signed off rather than numbers. Review them more often, every two or three months, so problems are caught while there is still time in the apprenticeship to fix them.
Between reviews: monthly one-to-ones
- Fifteen minutes, monthly, ideally face to face at the unit or on a ride-along.
- Three questions: what went well, what got in the way, what do you need?
- Share one piece of positive feedback and one area to work on.
- Note the conversation in two or three lines for the yearly review.
- Raise problems early, while they are small and easy to fix.
One-to-ones are also where you hear about stress, family pressures or the beginnings of a plan to leave. Listening at that point is worth more than any retention scheme.
Frequently asked questions
How often should engineers have a performance review?
A full review once a year with a mid-year check, plus short monthly one-to-ones, works well for most small firms.
Should first-time fix rate be a target?
It is a useful measure, but compare like with like. Engineers given older or more complex systems will naturally have lower rates.
Should reviews decide pay?
They should inform it through clear pay bands, but it helps to hold the development conversation separately from the pay decision.
References
legislation.gov.uk (The National Archives) (2015). Consumer Rights Act 2015, section 49 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (1998). The Gas Safety (Installation and Use) Regulations 1998, regulation 3 (opens in a new tab) ↑
Department for Business, Energy and Industrial Strategy (GOV.UK) (2021). Consumer protection study 2022: understanding the impacts and resolution of consumer problems (opens in a new tab) ↑
Department for Business, Energy and Industrial Strategy (GOV.UK) (2021). Consumer protection study 2022: understanding the impacts and resolution of consumer problems (opens in a new tab) ↑
Heating and Hotwater Industry Council (HHIC) (2026). Benchmark goes digital - what homeowners need to know (opens in a new tab) ↑
Office for National Statistics (2026). Annual Survey of Hours and Earnings 2026 provisional, Table 14 (occupation by 4-digit SOC 2020) (opens in a new tab) ↑