Key takeaways
- A performance review should rest on observed work and dated notes rather than on memory, the most recent bad week, or an opinion about the person.
- The standards a crew member is judged against have to be known in advance, because a review that introduces new expectations feels like an ambush and gets defended rather than heard.
- Short, regular conversations built on a running record change behaviour far more effectively than a formal meeting held long after the work it describes.
- Keep the discussion to a few areas, the quality of the work, safety and site habits, and reliability and communication, and tie each point to something you can show.
- Write down what was agreed and when it will be checked, because a dated record protects both the builder and the crew member if the matter ever goes further.
Most builders dread the performance review more than the person on the other side of the table does. The usual version is an annual sit-down that starts with small talk, drifts into a general feeling that things could be better, and ends with nobody quite sure what was said. The crew walks away unsure where they stand, and the boss walks away feeling the duty was done without anything being fixed.
The problem is not the conversation itself. It is that the review has nothing solid underneath it. A review built from memory, from the last thing that went wrong, or from who turned up on time this month is a weak document, and a site crew will read it as a verdict on their character rather than a record of their work. A review built from observed work and written notes is a different thing. It is specific, it can be checked against the job file, and it gives the crew member something they can actually change.
This article sets out a routine for reviewing the people on your tools and in your site team. It is written for a builder running a small to medium crew who has no human resources department and no reason to pay for one. It sits alongside the articles on apprentice retention and hiring a first employee, which cover the decisions made before someone starts. Here the focus is what happens once they are on the job.
Why most site reviews go wrong
Think about how a review gets written on a typical job. The builder is busy, the crew has been working for months, and the review is booked in because a form says it must be. A couple of days beforehand, the builder tries to remember the last few months. What comes back is whatever is loudest in memory: the wet week the slab was poured late, the afternoon a crew member left early, or the one good piece of carpentry that everyone saw. That is not a review. It is a sample of recent memory, and it is biased toward the dramatic.
The second problem is that the expectations were never written down. A crew member cannot be assessed against a standard they never heard. If the expectation is that tools are cleaned down at the end of the day, or that a variation is reported on the day it arises, but nobody said so until the review, the review becomes a surprise. Surprises feel like an ambush, and people defend themselves rather than listen.
The third problem is timing. Annual reviews sit too far from the work to be useful. By the time the conversation happens, the job has moved on, the details have blurred, and the crew member has no realistic way to fix a habit that has been running for a year. A review that only ever arrives as a summary of the past is a poor tool for changing how someone works on the next job.
Start with what you can see on the job
The foundation of a fair review is observed work. That means things that happened on a job which you or another supervisor saw, or which show up in a record made at the time: the daily pre-start, a hold point signed off, a delivery docket, a photo of a footing before the pour, or a client complaint that was logged. Opinions about attitude and personality do not belong in the foundation. They may come up in the conversation, but only after the observed work has been put on the table.
A useful test is to ask whether a second person would see the same thing. A second supervisor looking at the same wall should agree that it was out of plumb, that the flashing lapped the wrong way, or that the crew member was on site at the agreed start time. If they would disagree about whether someone is a good team player, that is a sign the note is an opinion and needs rewriting as a description of what happened.
Keep the evidence where it was made. If the pre-start sheet records who attended and what was discussed, use that rather than trying to recall it. If the job file holds photos of the waterproofing before the tiles went down, pull them up. A review that cites the job record is hard to argue with, and it protects you as much as the crew member, because you are not relying on your memory of a bad week.
Write the notes while the job is still running
The single habit that makes reviews easy is a running note kept as the work happens. It does not need to be an app or a system. A notes entry on the phone, a line in the back of the site diary, or a message to yourself at the end of the day will do, as long as each entry has a date, the job, the person, and one plain sentence describing what happened.
Write what you saw, not what you concluded. “Dave cut the cornice return twice and the second cut was square and fitted first time” is a useful note. “Dave is getting better at joinery” is a conclusion that cannot be checked. “Sam left the site before the agreed finish time without telling anyone” is a note, while “Sam is unreliable” is a verdict. The difference matters the moment the crew member asks you to show them the basis for what you said.
Keep notes for the good things as well. A review built only from problems teaches people that the only time they hear from the boss is when something has gone wrong, and it turns the whole process into a charge sheet. A record of praise given at the time, and specific enough to repeat, is one of the cheapest retention tools a builder has.
Set the expectations before the review ever happens
A review is only fair if the standard was known in advance. That does not mean a formal policy binder. It means that on the first day, and again whenever a standard changes, the crew knows what good work and good conduct look like on your sites. The list is usually short: how the site is left at the end of the day, how a defect is reported, how a variation or a change to the plans is raised, how the induction and site rules are followed, and how a late arrival or an absence is notified.
Where pay is tied to a classification, the expectations of the role are part of the picture too. If you are not sure how a classification applies to the work someone is actually doing, read how building award classifications are explained before you talk about a pay review, because a conversation about progression goes badly when the criteria are vague. Keep the pay conversation separate from the performance conversation where you can, so the person is not left wondering whether the feedback is a warning or a pay decision.
A review routine that fits a working crew
The routine is short and has a few parts. The first is the running notes described above, kept as the work happens. The second is a monthly check, which is a quick read of the notes for each person to see whether anything is building up, either good or bad. The third is a short, scheduled conversation on the site or at the end of a job, with the notes as the agenda and the crew member free to respond. The fourth is a written summary, kept on file, of what was discussed and what was agreed.
The monthly check is the part most builders skip, and it is the part that makes the rest work. A problem that appears once is a note. A problem that appears on several jobs in the same month is a pattern, and a pattern needs a conversation while it is still small. Equally, a crew member who has had a run of clean sign-offs should hear about it while it is still fresh, not at a meeting months later.
The review routine, end to end
- 1Note as you goRecord the date, the job and one plain sentence about what you saw.
- 2Check each monthRead each person’s notes and spot anything building into a pattern, good or bad.
- 3Talk on siteHold a short, scheduled conversation with the notes as the agenda.
- 4Write it downKeep a dated summary that both of you have seen and agreed to.
What to cover in the conversation
Keep the agenda to a few areas so the conversation does not sprawl. The areas that matter most on a site are the quality of the work, the way the person works safely and looks after the site, and how reliable and communicative they are. Each area should be tied to the notes. If there is nothing in the notes about an area, it is usually fine to say so and move on, rather than inventing a comment to fill the gap.
The quality of the work
Talk about what was built and how it was checked. Did the framing go up to the set-out and the plans? Were defects found before the inspection, or after it? Did the person ask when something was unclear, or guess and hope? A crew member who asks early is saving the business money, and that is worth saying out loud.
Safety and site habits
Look at how the person behaves when nobody is watching. Are the edges protected, is the lifting gear inspected before use, is the materials pile tidy, and does the person report a near miss rather than hiding it? Safety habits are where a conversation can get tense, so keep it factual and tied to a specific job. Never use a review to punish someone for reporting a problem.
Reliability and communication
Cover turning up when agreed, telling someone when they will be late or away, passing on what the next trade needs to know, and raising problems before they become delays. These are the habits that decide whether the rest of the site can plan around the person, and a builder’s day runs on other trades being able to plan.
Before you sit down with a crew member
- Every point is backed by a dated note or a job record.
- Each note describes what happened, not what you think of the person.
- The standard being discussed was given to the person in advance.
- Good work is recorded alongside the problems.
- The next step is agreed, with a date for checking it.
- The pay or classification question is kept separate where possible.
When the result is not good enough
Sometimes the notes do not support the person. The work has been slipping for a while, or a serious safety issue has happened and the crew member has not changed how they work. This is the point where the review becomes a management decision, and it needs to be handled as one. Be clear about the standard that was not met, show the notes that record it, and agree on what will change and when it will be checked. Write it down and give the person a copy.
Lead in. The mistake that costs the most is letting a safety or quality problem sit for months and then raising it in a review, because by then the work has been built on top of it and the person has a fair point that nobody said anything.
If the issue is serious enough to touch the licence, the insurance or the safety of the crew, do not wait for the review. Deal with it the day it becomes known, follow your own safety processes, and get advice from the right people before you act.
Worked example: the leading hand who kept missing handover
Consider a builder in western Sydney running several jobs at once with a leading hand who looks after a small sub-crew. Over a few months the builder’s notes show the same pattern. The leading hand’s crew consistently finished their scope on time, and the work passed inspection, but the handover to the plumbers and electricians was thin. On more than one occasion a trade turned up to a room that was not ready, and once a plumber spent a morning waiting for a wall to be opened that had been left off the list.
The builder’s first instinct was to call the leading hand a poor communicator and leave it there. The notes were better than that. They recorded the date and job of each handover problem, and they recorded that the crew’s own work was good. So the review did not start with a verdict. It started with the handovers, the plumber’s wasted morning, and the builder’s own part in it: the builder had never set a simple handover list for the leading hand to use.
The conversation then moved to what would change. The leading hand agreed to use a one-page handover list at the end of each stage, which the next trade signed. The builder agreed to check the list on the first handovers of each new job. The notes were updated at the next monthly check. A few jobs later the list was being used without prompting, and the plumber’s complaints had stopped. The dated record of what was agreed, and when it was checked, is what made the outcome credible to everyone involved.
Keeping records that protect both sides
Keep the written summary of each review on the person’s file, dated and seen by both of you, and keep the running notes that sit behind it. The records are useful if a dispute arises about pay, about the end of an engagement, or about a safety matter. They are also the best evidence you will have that the process was fair. A builder who can show a crew member the notes and the history of conversations is in a much stronger position than one who says “I think I mentioned it”.
Check the employment obligations that apply to the person before you change their pay, duties or hours, and before you end anyone’s engagement. Those obligations depend on whether the person is an employee, a subcontractor or a labour hire worker, and on the award and any agreement that covers them. A review record does not replace that checking.
What a review is not
A review is not a way to deliver bad news you have been avoiding, and it is not a way to build a case against someone you have already decided to move on. If you are planning to let a person go, the review should not be the first time they hear about it. A review is a tool for improving work and for keeping good people, and it works best as a normal part of how the business runs.
It is also not a substitute for a clear hiring process. If you are still working out how to bring the right person on for a role, the article on hiring a first employee covers the decisions made before a person starts. The clearer the expectations are at the beginning, the fewer difficult reviews you will have later.
Using this routine on your own site
Start small. Pick the people on your current jobs, write a one-line standard for each area, and begin the running notes this week. Hold the first short conversation at the next natural break, not as a special event. Once the routine feels normal, the reviews become a way of keeping good people on track rather than a dreaded chore.
The courses on PointCPD are for the continuing professional development you need for your own licence, which is a separate matter from managing a crew. If you are looking for training you can complete on your phone, browse the PointCPD home page for the current range and see what suits your renewal.
Questions builders ask
Should I run performance reviews for subcontractors as well as employees?
Subcontractors are engaged commercially, so the useful review is about the quality, timeliness and safety of the work they delivered, measured against the subcontract and your site rules. Check the subcontract terms before you put any assessment in writing. Keep the feedback tied to the work rather than to how the person is engaged.
What do I do if a crew member disagrees with what is in their review?
Listen to their point and write it down alongside your own. Check each disputed item against the dated notes, and correct the record if a fact was wrong. Agree what happens next and put that on file, signed by both of you.
How often should site staff be reviewed?
The notes should be kept all the time, with a quick check of each person’s notes at a regular monthly interval. The formal conversation should happen on a schedule you set in advance, rather than only once a year. A written summary after each conversation is the record that matters.
Do I need an HR system before I can run reviews?
No. For most small builders, a notes entry for each job, a standard written out in plain language and a signed summary after each conversation is enough. Use the employment obligations that apply to each person to decide what must be written down and kept.
What is the difference between feedback and a performance review?
Feedback is given at the time, about a specific thing, so it can be acted on straight away. A review is a planned conversation that draws the feedback together and records what was agreed. Both need the same foundation, which is observed work.
What if I need to review someone and I have no notes?
Start the notes today and be honest about the gap rather than filling it with recollection. Use the job records you do have, such as sign-offs, pre-start sheets and photos, and keep the review to what can be checked. Do not make claims about periods you did not record.
Sources
- Continuing professional development for builders and swimming pool builders · NSW Government
- General building work licensing · NSW Government
- Home Building Act 1989 (NSW) · NSW Legislation
Published 5 October 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
