Feedback on a Construction Site: Why It Matters, How to Give It, How to Take It (2026)

Most Sydney supervisors were never taught how to do this. They were taught how to build.

So the feedback either never happens, or it arrives six days late at full volume in front of eight other blokes.

This guide runs in three acts, and the order matters. Why it is necessary. How to give it. How to receive it.

Skip act one and the other two feel like technique. Read it and they feel like the job.

Table of Contents

1. Act 1: Why is feedback necessary on a site?
2. Act 2: How do you give feedback? Use the sandwich
3. What does the sandwich sound like on a Sydney site in 2026?
4. What never works when you correct a worker?
5. When is the sandwich not enough?
6. Act 3: How do you ask your crew for feedback?
7. How do you take criticism without blowing up?
8. Where is the line with agency crew?
9. Frequently Asked Questions

Act 1: Why is feedback necessary on a site?

Because silence is not free. It just bills you later.

You have known for three weeks. You have said nothing, not because you are soft, but because the conversation feels harder than the problem.

Three weeks of silence is not patience. It is a decision you are making badly.

Here is the uncomfortable maths. The worker does not know there is a problem, so he cannot fix it. The rest of the crew does know, and they are watching you do nothing about it.

What the research actually says

Gallup has been measuring this for two decades across millions of employees. Its consistent finding, reported in How Millennials Want to Work and Live (2016), is that workers who receive frequent, meaningful feedback from their manager are dramatically more engaged than workers who hear from them once a year or not at all.

Read that as an operator, not an HR poster. Engagement on a deck is not a mood. It is whether the bloke walks past a loose lead or picks it up.

The Fair Work Ombudsman's managing underperformance best practice guide makes the same point from the compliance side. Underperformance should be addressed straight away, because early conversations are easier to resolve and stop the issue becoming a serious one.

And it is a safety duty, not just a productivity one

The Safe Work Australia model code of practice on managing psychosocial hazards names poor support, lack of role clarity, poor organisational justice and conflict or poor workplace relationships as psychosocial hazards a PCBU must manage.

NSW has run its own Code of Practice on managing psychosocial hazards since May 2021. SafeWork NSW also lists inadequate reward and recognition as a hazard in its own right, so the praise half is not a courtesy either.

A worker who does not know where he stands is not just underperforming. He is carrying a recognised hazard you are responsible for managing.

And the crew cost is the one nobody budgets for. Your best two blokes are absorbing his slack, and they have noticed you are fine with that.

That is how you lose a good worker to keep a bad one.

Act 2: How do you give feedback? Use the sandwich

Something good. The correction. Something good. That is the sandwich, and it is the right default for almost every conversation you will have this week.

It gets sneered at in management training. On a live deck it wins for two plain reasons.

One: it is easy. You can run it in ninety seconds between a pour and a delivery, and you can teach it to a leading hand in one smoko.

Two: the worker stays on your side. He hears the correction as a note about the work rather than a verdict about him, so he fixes the stack instead of defending himself.

That second one is the whole game. Everything else in this act is detail hanging off it.

Build the middle, because the middle is the only part that changes tomorrow

The bread is easy. The filling is where sandwiches earn their bad name, and it has four mechanics.

The bread wraps that. Bread one: something real, the praise you would have given anyway. Bread two: close on the work, not on flattery. "That's all, you're going well otherwise, get back into it."

And place it properly. Correct one on one, praise where the crew can hear it. Public correction turns a task problem into a status problem, and from that moment he is defending his standing instead of fixing the work.

What does the sandwich sound like on a Sydney site in 2026?

Three situations, on repeat, on every job in Sydney. Here is the sandwich running in each.

The bloke stacking material wrong

"Your pace today has been good, we are well ahead on the bays. That stack is above head height and it is leaning, so bring it to chest height and land it on the bearers like that one. Give us a yell when it is done and we will keep moving."

Behaviour, a standard, and a close. Under twenty seconds, no character verdict anywhere in it.

The bloke on his phone

"You have been switched on all week, no dramas. No phones out on the deck while plant is moving, so if you need to take something, step off to the amenities and take it there. Other than that you are going fine."

You have given him a rule with a legal spine and a lawful alternative, instead of an order he can only lose.

The bloke who is technically fine but slow

The hardest one, because there is no incident to point at. Which is exactly why supervisors let it drift into a personality problem.

"Your work is clean, I have got no complaints on the finish. I need bays 4 and 5 cleared by smoko, so what is in your way? I will check in at smoko and we will sort it from there."

Give a slow worker a target, not a mood.

A target is something a worker can hit. A mood is something he can only absorb, and it usually comes back as a shrug and a slower morning.

Notice what all three have in common. The correction is aimed at something a camera could have filmed.

What never works when you correct a worker?

Two failure modes, and between them they cover most of what actually happens on Sydney sites.

Passive aggression is the quiet one. The sigh, the pointed silence, the job quietly reallocated to someone else, the comment made to the leading hand so it gets back to him.

It feels safer than a conversation. It teaches him nothing except that you have a problem with him and will not say it.

Having a go is the loud one. The spray across the deck, the sarcasm in front of the gang, the three weeks of frustration delivered in one go on a Friday.

Neither one tells the bloke what to do differently tomorrow.

Sustained public humiliation is also not just bad management. Repeated unreasonable behaviour that creates a risk to health and safety is how the model code frames workplace bullying, and it sits in the same psychosocial duty as act one.

When is the sandwich not enough?

The sandwich handles the day. It does not handle a pattern.

When the same behaviour survives two or three sandwiches, you have moved from correcting a task to managing performance, and that needs a different shape.

The prep is the same four mechanics from the sandwich filling. The difference is that the bread comes off and you say the point in the first sentence.

"Mate, I want to talk about your start times. Tuesday and Thursday you were on the tools around 7:40 instead of 7. I need that fixed. What's going on?"

Four sentences. Under fifteen seconds. It names the topic, gives one dated fact, states the standard, and ends on an open question so the next voice is his.

Compare that to the version most supervisors actually deliver.

"Yeah look, no dramas, you're going alright, it's just, you know, the boys have been saying a few things, and I'm not having a go, but we might need to have a bit of a look at how the mornings are running, if that makes sense?"

He walks away thinking the meeting went fine. Nothing changes. You get angrier.

If he can walk away unsure whether he was just told off, you did not have the conversation.

Two prep rules worth stealing from the Fair Work guide. Tell him the meeting is happening and roughly what it is about, so he can think about it first. And pick a spot where the audience is zero.

Then shut up

You have said your piece. Now stop talking, and let the silence sit there.

Most supervisors last about four seconds before filling the gap with a softener, a joke, or a second complaint, and the worker never has to answer the first one.

This is where you find out the thing you did not know. The induction never covered it, or he was never shown.

Or he has been getting contradictory instructions from two leading hands, which is textbook role conflict under SafeWork NSW's own hazard guidance.

Half the performance problems on a Sydney site are instruction problems wearing a worker's face.

The Fair Work guide makes the same point from the other side. Of the action points you agree, at least one should be something you will do to support him.

What do you say when it goes sideways?

He gets defensive. Do not argue the interpretation. Go back to the observable thing and ask a question.

"I'm not arguing about whether you work hard. I'm telling you what time you got on the tools Tuesday. What's making the mornings hard?"

He goes silent. Let it run. Count to ten in your head, then name it and set the follow-up.

"All good, you don't have to talk about it now. The start time still needs to be 7 from tomorrow. I'll check in with you Friday."

Something is going on at home. Listen, do not diagnose, do not fix. Then point him at real support rather than your own advice. MATES in Construction runs a 24/7 line built specifically for this industry, and telling the agency the same day lets the placement be adjusted.

He agrees, then nothing changes. The most common outcome of all, and the reason the say-it-back step exists.

"We agreed Tuesday you'd be on the tools at 7. Today's Friday and it's happened once. So either something's stopping you that we haven't talked about, or this isn't going to work. Which is it?"

Then write two lines in your phone. The date, and what was agreed. Not to build a case. So that in ten days you are working from a record instead of a mood.

Act 3: How do you ask your crew for feedback?

Acts one and two are you talking. The third act is the half that almost never gets built: getting the crew to talk to you, and being able to hear it.

Surveys do not work on a site. Verbal, one on one, in the moments where the tools are already down.

Two mechanics do most of the work. Ask about today, because memory of a specific morning is honest and memory of "the last month" is a summary.

And ask a specific question. "Any feedback for me?" gets "nah, all good mate" every time, which is not a closed worker but a badly built question.

"What wasted your time today?" gets you an answer, because it is concrete, recent and blames nobody.

Then close the loop out loud. Tell the bloke who raised it what you fixed, or what you could not fix and why, by name and in front of the others.

The longer version of this, including the five questions that get a real answer, is covered in our separate guide to collecting feedback from your crew.

How do you take criticism without blowing up?

Asking is only half of act three. The other half is what your face does in the two seconds after the answer arrives.

The damage in almost every site blow-up happens in the first three seconds, before your thinking brain catches up with your adrenaline.

So build a reset and run it every time. One breath in, one breath out, before a single word. Hands still. Face the person.

Then use the same three-part response, every time, no matter who is delivering it.

Step two is the one almost nobody does, and it is the one that does the work. It is the same say-it-back mechanic from act two, pointed at yourself.

Shutting down costs you as much as blowing up. It just takes longer to show, because the person who raised it reads silence as resentment and stops raising things. 🦺

The worker-side version of this, including what to do when the feedback is genuinely wrong, is covered in our separate post on taking feedback on site without blowing up.

Where is the line with agency crew?

All three acts run the same way with labour hire crew, with one boundary sitting over the top of them.

You direct the work. The agency employs the worker. Both are true at the same time.

So the practical rule is short. Have the conversation on site. Tell the agency the same day.

You are not stepping on anyone's toes by telling a worker what the site standard is. That is exactly what a host is supposed to do, and it sits inside the host employer responsibilities you already carry.

What you should not do is issue warnings, threaten his employment, or talk about his pay. That is the agency's lane, and staying out of it protects you.

Praise runs to both. Tell the worker, then tell the agency, because that is how the good ones keep landing on your job. Every allocator keeps a record of who to send where, and a host who feeds back specifics gets a better-matched crew next time.

At Leap the allocator holds that record, and our systems flag the patterns for a human to read. AI watches the signals and suggests. The allocator and the client decide. Nothing about a worker's placement is decided by software.

And when do you end the placement?

When you have done the honest version and it did not work. That is two conversations: one that named the behaviour and agreed a dated change, and one follow-up that showed nothing moved.

Anything less and you are ending a placement over something the bloke was never clearly told. Anything more and the crew reads the standard as optional.

Make the call the same day, and be specific on the phone. "He was told Tuesday, we agreed 7am starts, it happened once" gives the allocator something to work with. Vague feedback produces vague replacements.

Get Started

Want an agency that takes the call, acts on it the same day, and sends back a worker who fits the site instead of a shrug? See how Leap prices and supplies Sydney crew, or tell our allocator what your site actually needs.

Frequently Asked Questions