Leading the site safety meeting: capstone

Eighteen months into Cottonwood Place, Tallgrass promoted Ben Nakamura to safety coordinator for its next project, a five-storey seniors' residence called Harvest Lane, due to start in the spring. Before Ben left, Owen asked him to run the site-wide safety meeting at Cottonwood Place for a month, and then to write the outline of the Harvest Lane safety program using everything the two of them had learned. This last lesson follows both tasks: running a meeting that people actually listen to, and pulling the whole course together into a program.

Meetings that matter

A construction site has many safety conversations: the start-of-shift huddle, the pre-task plan, the toolbox talk, the Tuesday coordination meeting for foremen, and the committee meeting. Each has a different purpose and audience.

The committee

Manitoba requires a workplace safety and health committee at a workplace where 20 or more workers are regularly employed, and a worker safety and health representative where there are 5 to 19. At least half of the committee's members must be workers, chosen by the workers or their union, not by the employer, and the committee has co-chairs, one from each side. The committee identifies hazards, receives and deals with concerns and complaints, takes part in inspections and investigations, reviews the employer's program, and makes recommendations, to which the employer must respond in writing. Members are entitled to time off without loss of pay for committee duties and training. On Cottonwood Place, Tallgrass set up a site committee with worker members from the larger trades, so that the worker voice covered the whole site and not only Tallgrass's own crews. Lena Petrov was the worker co-chair.

Running the site-wide meeting

Ben's first site-wide meeting was a lesson in itself. He read from a list of reminders for twenty minutes in the lunchroom, at the end of a Friday shift, with a generator running outside. By the end, half the crowd was looking at phones. Owen's feedback afterwards was short: fewer topics, more stories, more questions, and finish on time.

By the third meeting, Ben had a format that worked.

• Start on time and keep it to 20 minutes. Start-of-shift on a Wednesday, in the yard, not the end of a Friday.
• One lesson from the site. A recent incident or near miss, told as a story without naming or blaming anyone: what happened, why, and what has changed.
• One change to the plan. A new rule, a new route or a new phase, and the reason for it.
• One question for the crews. A real question, such as 'Where on site do you feel least safe this week?', with time for answers. Ben wrote every answer down and reported back at the next meeting on what had been done.
• One recognition. A crew or worker who did something well: a good catch, a stop-work call, a tidy floor.
• Close the loop. What happened to last meeting's questions and concerns.

The question segment produced the most useful information. In the second month, a labourer said the north gate was dangerous at 7 a.m. because concrete trucks and workers on foot arrived at the same time. Ben timed it the next morning, counted 14 trucks and 60 workers through the same gate in 25 minutes, and the next week Tallgrass opened a separate pedestrian entrance on the lane side. He announced the change at the following meeting and thanked the labourer by name, with his permission.

Making talk lead to action

Meetings that produce no action teach workers that speaking up is pointless. Ben kept a simple log of every concern raised at any meeting, with an owner and a due date, and reviewed it weekly with Owen.

# Concerns raised at safety meetings over four weeks.
concerns = [
    ("north gate trucks and walkers at 7 a.m.", "Tallgrass", True),
    ("poor lighting in stair tower B", "Brooks Electric", True),
    ("no water station on level 7", "Tallgrass", True),
    ("hoist wait times push workers to use stairs with loads", "Tallgrass", False),
    ("dust from cutting on level 3 drifts to level 4", "Pinecrest Interiors", True),
    ("noisy compressor next to lunchroom", "Lone Star Mechanical", False),
]
done = [c for c in concerns if c[2]]
print(f"closed {len(done)} of {len(concerns)} ({100 * len(done) / len(concerns):.0f}%)")
for text, owner, closed in concerns:
    if not closed:
        print(f"open: {text} -> {owner}")

closed 4 of 6 (67%)
open: hoist wait times push workers to use stairs with loads -> Tallgrass
open: noisy compressor next to lunchroom -> Lone Star Mechanical

Two items were still open after four weeks. The hoist wait time needed a second hoist car, which the project manager approved after Ben showed the counts. The compressor was moved. Both were reported back at the next meeting.

Capstone: the Harvest Lane safety program

For his second task, Ben wrote an outline of the safety program for Harvest Lane, a five-storey wood-frame building on a concrete podium, beside an operating seniors' care home, with about 90 workers from 14 employers at peak. Owen asked him to organize it by the duties in this course, and for each one to say what Tallgrass would do and how it would show it had done it.

• Roles and duties (lesson 1). Confirm in the contract that Tallgrass is the prime contractor. Get the owner's written disclosure of known site hazards, including the care home's operations, oxygen storage and emergency routes. Name the superintendent, safety coordinator and each subcontractor's supervisor.
• Due diligence and supervision (lesson 2). Supervisor standards for every foreman, with the evidence scorecard for each top hazard.
• Notices and permits (lesson 3). A register from day one, with excavation, suspended platform and any asbestos notices for the existing site structures, building and street use permits, locates and WCB clearances.
• Site-specific plan (lesson 4). A hazard register by phase, with special attention to fire during wood-frame construction, work beside an occupied care home, and crane lifts near residents.
• Certification and measurement (lesson 5). Leading and lagging indicators on the monthly report; COR maintained.
• Competence (lesson 6). A training matrix for every worker and verification of high-risk credentials.
• Coordination (lesson 7). Shared hazard owners, the opening register, the guardrail removal permit, the look-ahead and handover walks from the first week.
• Subcontractor selection (lesson 8). Prequalification for every trade, pre-award meetings with foremen, conditions for any firm in the conditional band.
• Inspections and records (lesson 9). The six layers of inspection, the deficiency log with risk classes and monthly pattern review.
• Regulator visits (lesson 10). The visit procedure practised with the site team; the order register with appeal and compliance dates.
• Incidents (lesson 11). The first-hour procedure, reporting responsibilities named, the five-step investigation method, near-miss reporting from day one.
• Meetings and the committee (lesson 12). A site committee from the first month, the 20-minute site meeting and the concern log.

Owen read the outline and added one line at the top: 'Everything here is a promise. Write down how we will know if we have kept it.' Ben went back and added a measure to each item, such as 'percentage of planned inspections completed' or 'days to close class B deficiencies', so that the Harvest Lane program could be checked against itself every month.

What holds it together

The duties in this course can look like a long list of separate obligations. They are really one idea, written into the law in different ways: the people who control the work must find its hazards, control them, check that the controls work and learn when they fail. The prime contractor does this for the whole site, each employer for its own work, each supervisor for their crew and each worker for themselves and those around them. A program that keeps those four levels connected, with records that show it, is both the best protection for workers and the best answer to any officer, court or owner who asks what was done.

Toolbox talks that work

The weekly toolbox talk is the meeting most workers attend most often, and the one most often wasted. A foreman reading a printed sheet aloud while the crew stands in the cold teaches little. Tallgrass's guidance for foremen is to choose a topic that matters to this week's work, to start with a real example from the site or the trade, to show the actual equipment where possible, to ask the crew questions rather than just tell them, and to finish with one thing the crew will do differently. Ben ran a short session for foremen on these points during his month leading the site meeting, using a talk on dropped objects as the example: the foreman held up a tethered and an untethered tape measure, asked the crew where on site they had seen tools left at an edge, and finished by issuing tool lanyards to anyone who did not have one. Attendance sheets show who was there; questions and answers show whether anyone learned anything, so the guidance asks foremen to record one question raised at each talk.