Building Accountability in a Small Construction Team
Most construction business owners know exactly who isn't pulling their weight. The harder question is why nothing's been done about it.
Accountability in a small construction team isn't about being a hard boss. It's about being clear. Most team issues I see in construction businesses come back to one thing: the owner assumed the team knew what was expected, and the team had a completely different idea of what good looked like. Neither side is necessarily wrong. They just never agreed on the standard.
The first thing you need is clarity on what each person is responsible for and what completing that responsibility looks like. Not in vague terms. Specifically. If a site foreman is responsible for daily progress on a job, what does that actually mean? Does it mean the job's on programme? Does it mean the end-of-day report is sent? Does it mean materials are ordered 48 hours ahead? Until you define it in concrete terms, you can't hold anyone to it.
Once you've got that clarity, you need to communicate it. Not once in a team meeting. Regularly. Most people don't respond to one conversation about expectations. They respond to consistent reinforcement. Weekly check-ins, even short ones, where you go through what's on, what's due, and whether things are on track. That rhythm keeps everyone pointed in the same direction and gives problems a chance to surface before they become expensive.
The issue most owners run into is that they've never had the direct conversation with someone who's underperforming. They've hinted. They've commented on site. They've vented to someone else. But the actual conversation, the one where you sit down and say clearly that something needs to change, hasn't happened. That conversation feels uncomfortable. It is uncomfortable. But it's the only thing that gives the person a real chance to improve. Without it, they genuinely might not know there's a problem.
When you do have that conversation, it needs to be factual. Not emotional. Not based on how you felt about something. Based on what happened, what was expected, and what the gap was. If a job ran two days over programme and that cost you money, that's the conversation. What was agreed, what happened, what you need to happen differently next time. Give the person a chance to respond. Sometimes there's context you didn't have. Sometimes there isn't. Either way, you've had the conversation.
Documentation matters more than most small construction business owners think. Not for legal reasons, though that's worth considering. For clarity. When you've agreed on something with a team member, write it down and make sure both of you have it. Even a quick message summing up what was discussed. It removes the 'I didn't know that was expected' conversation later and gives you something concrete to refer back to.
Accountability also runs the other way. If you want your team to take ownership, you have to be consistent as the owner. If you say jobs get a proper brief on Monday morning and then you turn up with no brief on Monday, you've told the team that the standard doesn't really apply. People watch what you do far more than what you say. The culture of your business comes from you whether you intend it to or not.
Small teams can hold each other accountable too, but only when the environment allows it. When the standard is clear, when there's a process for how things get done, and when everyone knows that the owner is consistent with his own expectations, the team naturally starts to pick up the slack with each other. That doesn't happen by itself. It's built over time through the owner being clear and consistent.
Pick one expectation in your business that isn't being met and isn't being addressed. Write down what you expect, what's actually happening, and what a direct conversation about it would sound like. Have that conversation this week.
Marc works privately with construction business owners who want real structure, real profit, and a business that doesn't depend on them doing everything.
Apply for Coaching