How to Improve Safety Culture in Construction: 2026 Guide

If you're running multiple crews, labour hire, and subcontractors across active sites, your safety culture is already being tested every morning before pre-start. The issue usually isn't whether you have a policy. It's whether the people doing the work believe the standard applies equally to everyone, including supervisors, project managers, and subcontractor foremen.

In Australian construction, that gap matters. Safe Work Australia reported 26 worker fatalities in construction during 2023, making construction the leading cause of traumatic work-related deaths, according to this summary of the Australian data. If you're serious about how to improve safety culture in construction, start with the reality that paperwork won't fix a culture problem on its own.

Table of Contents

• Diagnose Your Current Safety Culture Before You Act
  • Start with a baseline that reflects the real site
  • Look for the gaps between paperwork and practice
  • Build a short diagnostic that leaders can use
• Secure Leadership Commitment and Worker Engagement
  • Visible leadership changes what crews tolerate
  • Worker consultation has to affect decisions
  • What good engagement looks like on site
• Implement Practical Behaviour-Based Safety Techniques
  • Use observation to coach, not to catch people out
  • Keep the checklist tight and task-based
  • A simple field example
• Manage Safety Culture Across All Contractors
  • Induction alone won't align subcontractors
  • Set one site standard and enforce it consistently
  • Stop rewarding silence
• Use Digital Tools for Real-Time Reporting and Monitoring
  • Paper systems hide risk until it's too late
  • What to digitise first
  • Choose tools that support decisions
• Measure What Matters and Manage the Change
  • Use lead indicators to see culture moving
  • Example Safety KPIs
  • Treat culture improvement as an operational change

Diagnose Your Current Safety Culture Before You Act

Most construction firms move too quickly to solutions. They add another form, rewrite the SWMS template, or schedule more training. If you haven't diagnosed the culture properly, you'll treat symptoms and leave the drivers untouched.

A proper baseline isn't a compliance exercise. It's a working view of what people believe, what they do under pressure, and what leaders tolerate when programme, cost, and safety collide.

Start with a baseline that reflects the real site

Use more than incident data. Injury figures tell you what has already happened. They don't tell you whether supervisors are closing out hazards properly, whether subcontractors feel safe to speak up, or whether project teams normalise shortcuts late in the programme.

Build your baseline from several inputs at once:

• Document review: Check recent incident reports, corrective actions, site audit findings, toolbox records, SWMS reviews, and contractor non-conformance records.
• Field observation: Walk the site when work is live, not just during a planned inspection window. Watch handovers, plant interactions, temporary works, housekeeping, and permit controls.
• Worker input: Ask direct employees, labour hire, and subcontractors the same practical questions. Keep the wording plain and focused on how work really gets done.
• Leadership behaviours: Check whether managers attend site to understand risk, or only appear after an incident or client visit.

If you need a structured way to capture those findings, a WHS gap analysis template helps organise evidence against expected controls without turning the exercise into a paper shuffle.

Look for the gaps between paperwork and practice

The most useful diagnosis work happens in the gaps. That's where culture sits.

You might find that your pre-starts are well attended but superficial. You might find workers sign onto SWMS that no longer reflect the sequence of work. You might find supervisors talk about production in detail and safety in general terms. None of those issues will show up clearly if you only review lag outcomes.

Practical rule: If the documented process says one thing and the job runs another way, assess the real method of work first and the paperwork second.

A maturity model can help frame what you see. You don't need a complicated scoring system. A simple progression works well in practice:

Use the model to start honest discussions with leadership, not to produce a polished slide for the board.

Build a short diagnostic that leaders can use

A good diagnostic isn't long. It is repeatable. It should let your project leadership answer practical questions such as:

1. Do supervisors stop work when controls break down?
2. Can subcontractors raise concerns without fearing commercial fallout?
3. Are corrective actions being closed by the responsible person, not rolled forward?
4. Do site teams update controls when the job changes, or keep using old documents?
5. Do managers spend enough time where risk is being created?

Keep part of the process confidential. People tell you more in private than they will in front of a project manager or subcontractor boss. That matters even more on sites with layered contracting arrangements.

For firms trying to make the findings stick beyond the audit stage, a practical guide to cultural change management is useful because it treats behaviour change as an operational discipline rather than a slogan. That's the right mindset. Diagnose first. Then act on what your sites are telling you.

Secure Leadership Commitment and Worker Engagement

You can tell what a company values by what its leaders notice, fund, and challenge. Safety culture improves when site and business leaders make it visible in daily decisions, not when they repeat the right words at the annual WHS review.

Too many leadership teams think commitment means signing policies, approving PPE budgets, and asking for monthly stats. Crews don't judge commitment that way. They judge it by who turns up, what gets questioned, and whether anyone backs them when production pressure rises.

Visible leadership changes what crews tolerate

On a functioning site, leaders are seen in the field. They ask about isolations, traffic routes, sequencing, work at height, and supervision. They don't just ask whether the paperwork is complete. They ask whether the control is still valid for today's work.

That sort of visibility sets the tone quickly. If the project manager walks past poor exclusion zones, incomplete edge protection, or a rushed lift plan without comment, everyone reads the message. Standards are negotiable.

A stronger approach looks like this:

• Attend live work fronts: Visit during setup, handover, or change in sequence. That's when controls fail.
• Ask operational questions: "What's changed since yesterday?" is more useful than "Has everyone signed on?"
• Follow through: If a leader requests an action, check that it happened. Unchecked instructions weaken authority.
• Back the stop-work call: If a supervisor pauses a job for a genuine control issue, support it publicly.

Crews watch what leaders walk past. They don't care much about the wording in the policy manual if site behaviour says something else.

Leadership development matters here. For managers who want a sharper view of how behaviour at the top shapes standards below, this piece on how the tone from the top shapes an unbeatable company culture is worth reading. The principle applies directly to WHS. People copy what leaders reward, excuse, and ignore.

For a practical internal framework on this point, leadership and safety responsibilities can help clarify who needs to do what at executive, operational, and site level.

Worker consultation has to affect decisions

Worker engagement isn't about asking for feedback and then parking it in meeting minutes. Under the WHS framework, consultation has to be genuine. On a real site, that means crews can influence controls, sequencing, access arrangements, plant interfaces, and work methods before the issue becomes an incident.

Safety committees can help if they have authority and clear scope. They fail when they become a place to read out statistics and remind people about basic housekeeping. Keep them tied to real decisions.

Focus committee and consultation time on matters such as:

• Work planning changes: New trades entering site, revised sequencing, temporary works changes, access constraints.
• Recurring field issues: Repeated line-of-fire exposures, bypassed permit steps, traffic conflicts, or uncontrolled deliveries.
• Contractor interfaces: Gaps between principal contractor expectations and subcontractor supervision on the ground.
• Learning from events: What changed after the incident, near miss, or failed inspection.

What good engagement looks like on site

Good engagement is often simple. It has rhythm. It also has consequences.

A practical pattern is to combine daily pre-start conversations, weekly supervisor reviews, and a standing worker forum where issues can be escalated and tracked. The key is closing the loop. If a worker raises a concern about access, dust control, manual handling, or plant movement, someone needs to respond visibly.

Use plain rules:

The best sites don't separate leadership commitment from worker engagement. They connect them. Leaders show they mean it. Workers see speaking up changes the job. That's where culture starts to harden into standard practice.

Implement Practical Behaviour-Based Safety Techniques

Behaviour-based safety works when it's used as a field coaching method. It fails when companies turn it into a dressed-up compliance trap.

On construction sites, the point isn't to monitor people for minor breaches. The point is to identify a short list of behaviours around critical risk, observe them during normal work, and coach in real time before a lapse turns into an event.

Use observation to coach, not to catch people out

Start with one rule. Don't launch behaviour observations as an enforcement campaign. If workers think the exercise is there to find fault, they'll play to the checklist when you're watching and revert when you're gone.

Pick a few critical behaviours linked to your current risk profile. Keep them visible and task-specific. For example, if your site has repeated issues around mobile plant, work at height, or manual handling, build observations around those.

Use peer observers or frontline supervisors who can give calm, immediate feedback. The exchange should be brief and useful:

• what was seen
• why it mattered
• what good looked like
• whether any site condition made the task harder to do safely

That last point matters. At-risk behaviour often sits on top of poor planning, time pressure, layout problems, missing equipment, or unclear supervision.

Keep the checklist tight and task-based

A weak BBS checklist tries to cover the entire WHS system. A useful one focuses on a handful of observable acts.

Keep it to practical items such as:

1. Access and position: Is the worker in a stable, controlled position for the task?
2. Line of fire: Is anyone exposed to moving plant, suspended loads, stored energy, or pinch points?
3. Tools and equipment: Is the selected tool fit for the task and in serviceable condition?
4. PPE use: Is required PPE being used correctly, not just worn?
5. Communication: Are workers coordinating clearly during shared or high-risk activity?

You don't need long forms. You need repeatable field conversations and a way to spot patterns. If three crews are all stepping outside the same control, don't blame three crews first. Check whether the method, layout, materials flow, or supervision setup is driving the shortcut.

The useful question isn't "Who broke the rule?" It's "Why did the job make that shortcut easy?"

A simple field example

Take a routine observation around loading and unloading materials near a live traffic area. The observer sees a dogman standing closer to the drop zone than planned and a spotter losing line of sight around stored materials.

A poor response is to tell both people to be more careful.

A better response is to pause, reset the laydown area, clear the obstruction, restate the exclusion line, and check whether the delivery sequence created the pressure. Then log the issue so it can be fixed for the next delivery, not just this one.

That's how behaviour-based safety supports culture. It reinforces the standard, but it also respects the fact that behaviour is shaped by the conditions leaders and supervisors create.

Manage Safety Culture Across All Contractors

If you run a principal contractor model or a busy industrial site with multiple service providers, your safety culture is only as strong as the weakest subcontractor interface. That's where a lot of firms get this wrong. They put effort into direct employees and assume subcontractor management starts and ends with pre-qualification, induction, and the occasional audit.

It doesn't.

Induction alone won't align subcontractors

Subcontractor alignment breaks down when commercial pressure, supervision standards, and reporting expectations differ across the chain. That's one reason this issue deserves more attention than it usually gets.

According to this discussion of recent Australian construction safety data, SafeWork NSW reports subcontractors are involved in 70% of serious incidents in 2024-25. The same source notes the WA construction fatality rate at 12.5 per 100,000 workers in 2025, four times the national average, and cites a 2025 Curtin University study showing 25% underreporting of near-misses in WA high-rise projects due to subcontractors fearing contract loss.

Those figures line up with what many site leaders already know. The problem isn't just worker behaviour. It's fragmented accountability.

Set one site standard and enforce it consistently

If each subcontractor runs a separate safety culture, you don't have a site culture. You have parallel systems competing with each other.

The principal contractor or PCBU with management control needs to set one operating standard for the site. That standard has to cover more than induction content. It needs to shape procurement, mobilisation, supervision, reporting, and daily coordination.

A workable approach includes:

• Pre-engagement checks: Review the subcontractor's actual supervision model, competency controls, SWMS quality, incident response practice, and evidence of field leadership.
• Common site rules: Use one set of critical controls for shared high-risk activities such as work at height, lifts, plant interaction, energised systems, permits, and temporary works.
• Integrated supervision: Bring subcontractor supervisors into planning meetings, risk reviews, and learning discussions. Don't leave them outside the core operating rhythm.
• Joint field verification: Walk the work fronts together. Compare what the subcontractor believes is in place against what the site team is seeing.
• Clear reporting expectations: Define how hazards, near misses, and incidents are raised, escalated, and closed out across all companies on site.

Subcontractor foremen matter more than many head offices realise. They're the daily translators between commercial pressure and site standard. If they aren't aligned, the paperwork won't save you.

Stop rewarding silence

One of the worst habits in contractor environments is rewarding "zero incidents" in a way that punishes disclosure. It sounds positive. In practice, it can suppress near-miss reporting, hide weak controls, and push crews to manage problems informally.

If subcontractors believe a reported event will damage their standing, they will think twice before reporting. Some will say nothing. Others will only raise it once it becomes too visible to ignore.

A better model is to recognise:

If a subcontractor only feels safe reporting good news, your site is learning too late.

That is the practical heart of how to improve safety culture in construction across a fragmented workforce. Treat subcontractors as part of the operating system, not an external compliance problem.

Use Digital Tools for Real-Time Reporting and Monitoring

Most safety culture problems become worse when information moves slowly. Paper forms sit in utes, site sheds, and inboxes. Hazard reports are raised late. Corrective actions drift. SWMS revisions don't reach the people who need them. By the time head office sees a pattern, the site has already moved on.

Digital tools won't create culture on their own. They do remove friction from the behaviours you want more of.

Paper systems hide risk until it's too late

Paper has three practical problems on live construction work.

First, it delays reporting. Workers often won't stop to fill out a long form if the process is clumsy. Second, it fragments information. One site keeps a spreadsheet, another uses PDFs, another relies on email chains. Third, it makes trend review harder than it should be.

That matters most on contractor-heavy sites. If multiple subcontractors are feeding information into different channels, no one gets a clean picture of recurring plant issues, repeat permit failures, or overdue actions.

What to digitise first

Don't digitise everything at once. Start with the workflows that affect field visibility and response time.

A sensible first group includes:

• Hazard and near-miss reporting: Let workers log issues on a phone with photos, location, and a short description.
• Corrective action tracking: Assign actions to named people, set due dates, and make status visible.
• SWMS access and review: Keep the current version available in the field so crews aren't working from an outdated file.
• Inspections and verifications: Use standard checklists for plant, critical controls, permits, housekeeping, and high-risk work fronts.
• Contractor oversight: Record who has completed induction, what competencies are current, and where outstanding issues sit.

A platform such as Safety Space's safety culture app can support that by centralising reporting, form completion, and multi-site or subcontractor oversight in one place. The value isn't the software itself. It's the fact that managers can see risk signals while there's still time to respond.

Choose tools that support decisions

Good digital systems make it easier to act, not just easier to collect data. That's the test.

Ask practical questions before rollout:

Keep the rollout simple. Train supervisors first. Make field reporting easy. Review live data in site meetings. Then use what the system shows you to challenge weak supervision, poor close-out discipline, or recurring contractor issues. That's where the cultural value sits.

Measure What Matters and Manage the Change

If you only measure injuries, you won't see culture improving until long after the work changed. That's too late. By then, crews may already have stopped reporting weak signals, supervisors may be carrying overdue actions, and leaders may think the absence of incidents means the system is working.

Strong safety culture needs a mix of lag and lead indicators. The lag indicators still matter. They tell you where harm occurred. But the lead indicators show whether your organisation is doing the things that prevent harm and support learning.

Use lead indicators to see culture moving

The right indicators are close to the work. They show whether people are identifying hazards, updating controls, participating in reviews, and closing actions properly.

Look for measures that answer questions such as:

• Are issues being raised early?
• Are corrective actions being closed on time and verified?
• Are supervisors spending time on critical control checks?
• Are subcontractors participating in the same reporting rhythm as direct employees?
• Are workers involved in reviews after changes to work scope or sequence?

Don't let the dashboard become bloated. A short set that leadership reviews is better than a long set no one uses.

Good safety metrics don't just count failure. They show whether the business is practising prevention.

Example Safety KPIs

Use the dashboard to drive discussion, not just report status. If hazard reports increase, don't assume the site got less safe. It may mean reporting trust is improving. If near-miss reports fall sharply after a contract review cycle or a hard-line performance message, look deeper. Silence can be a warning sign.

Treat culture improvement as an operational change

Safety culture shifts when leaders manage it the same way they manage other important operational changes. That means a clear reason for the change, defined responsibilities, supervisor capability, worker consultation, and regular review.

Keep the change plan simple:

1. State the essential standards: Define the few site standards that apply across all crews and contractors.
2. Explain the reason: Link the change to risk exposure, work quality, and legal duty under the WHS Act.
3. Train the right people first: Site leaders and supervisors shape whether the initiative survives contact with the programme.
4. Review early signals: Check reporting quality, action close-out, field verification, and participation.
5. Acknowledge useful behaviours: Recognise teams that raise issues early, improve controls, and close gaps properly.

If you're trying to shift a fragmented contractor environment, don't wait for culture to improve on its own. Set the standard, measure the behaviours that support it, and manage the change with the same discipline you apply to programme, procurement, and cost control.

If your sites are still relying on paper forms, scattered spreadsheets, and inconsistent contractor reporting, Safety Space is worth a look. It gives H&S managers and operational leaders one place to manage reporting, corrective actions, form completion, and subcontractor oversight across multiple sites, which makes it easier to see where standards are holding and where they're slipping.