Safety Program Review for General Contracting

Decide if the review will focus on a single project, a group of projects, or the whole company. Write this down so participants know the level of detail expected.

Determine how often reviews will take place (for example, quarterly for active projects, annually at company level). Align timing with key milestones such as project phases or budget cycles.

List what the review should accomplish, such as “identify top safety risks,” “check if processes are being followed,” and “decide which improvements to implement next year.” Keep objectives specific enough to guide work.

Decide which components you will examine: orientation, training, inspections, incident reporting, near miss reporting, PPE management, toolbox talks, and supervision. Note any special focus areas, such as high-risk work types.

Write a one-page description of scope, frequency, and objectives. Share it with project and safety leadership so everyone agrees on what the review will cover.

Designate a person (for example, safety manager or operations leader) who is responsible for organizing and completing the review on schedule.

Choose the time window for the data set (for example, the last quarter, last six months, or the duration of a project phase). Note the start and end dates clearly.

Export or collect all incident and near miss records for the review period, including severity, causes, and corrective actions. Ensure you include both recordable and non-recordable events.

Compile daily safety walk logs, weekly inspection reports, and any formal audits from clients or internal teams. Note the number of findings, types of issues, and any repeat observations.

Obtain records of completed orientations, toolbox talks, and formal safety training events. Note attendance, topics covered, and any missed or overdue training.

List any citations, warnings, or formal notices from regulators or clients received during the review period, along with their status and associated corrective actions.

Store all collected data in a single location (shared drive, safety software, or binder) and label files clearly. This ensures the review team can access what they need without hunting through multiple systems.

Identify who will provide feedback: foremen, superintendents, project engineers, and a sample of tradespeople from different subcontractors and tasks.

Select one or more methods such as short anonymous surveys, small group discussions, or one-on-one interviews. Pick methods that fit your culture and the time available.

Prepare 6–10 simple questions covering topics like “What safety processes help you most?” “Where do you see gaps?” and “What makes it hard to work safely?” Use open-ended questions to get useful answers.

Arrange times that do not disrupt critical work, such as just after a shift meeting or at the end of the day. Explain the purpose and stress that honest input is valued and will not be used against individuals.

Take notes on repeated comments, frustrations, and positive observations. Capture specific examples of good practices and problem areas that workers describe.

Write a short summary of what you heard, grouped by theme (communication, training, equipment, supervision). Include direct quotes where helpful, without naming individuals.

Sort events into categories such as falls, struck-by, caught-in, manual handling, equipment, or environmental. Note counts and severity levels within each category.

Look for clusters of events tied to specific areas of the site, types of tasks, shifts, or subcontractors. Mark any “hot spots” where issues are concentrated.

Scan inspection reports to see which types of deficiencies show up again and again, such as housekeeping, access routes, guardrails, or electrical. Compare these to the incident categories.

If you have data from previous review periods, compare current and past trends. Look for risks that are increasing, decreasing, or staying stubbornly the same.

Check whether certain hazard types appear frequently in near misses but not yet in injuries, which could signal emerging risks. Treat these patterns as future problems to get ahead of.

Write a short trend summary that highlights top incident types, common locations, and major inspection themes. Use basic charts or tables if helpful, but keep the summary easy to understand.

Write down the main processes you will examine, such as new hire orientation, daily and weekly inspections, toolbox talks, JHAs, incident reporting, near miss reporting, and PPE management.

For each process, decide what “effective” means, such as “held on schedule,” “documents complete,” “issues corrected promptly,” and “workers understand expectations.” Keep criteria clear and observable.

Pull a sample of records for each process: orientation sign-ins, toolbox talk forms, inspection logs, JHAs, and incident reports. Check for completeness, timeliness, and meaningful content.

During site visits, observe whether work practices match what documentation claims. For example, if JHAs are completed, check whether crews actually know and follow the planned controls.

Give each safety process a simple rating such as “Effective,” “Partially Effective,” or “Needs Improvement,” and note the reasons for your rating in plain language.

Identify which processes are farthest from how they should work or are clearly not supporting safe work. These will be prime candidates for redesign in the improvement plan.

During site visits, note whether supervisors and managers wear PPE correctly, stop to address unsafe acts, and participate in safety discussions. Their behavior is a strong signal of real priorities.

Sit in on planning meetings or production reviews to see how safety is addressed: is it a real agenda item or an afterthought? Note whether safety issues are resolved or simply acknowledged and forgotten.

Look back at previous safety meeting minutes and action logs to see if agreed safety actions were completed on time. Persistent delays can signal weak commitment.

Ask supervisors and workers whether rules are applied the same way to everyone, including senior staff and “star” performers. Inconsistent enforcement undermines the program.

If feasible, use an anonymous survey asking workers whether they believe safety is truly valued, whether they feel comfortable speaking up, and whether they trust that issues will be addressed.

Write a short summary describing the current safety culture in practical terms, noting both positive aspects (visible involvement, open communication) and problem areas (tolerance for shortcuts, blame).

From trend analysis, process evaluations, and culture assessment, compile a single list of issues such as “weak JHA use,” “frequent ladder misuse,” or “inconsistent incident follow-up.”

Cluster related items into themes like “training,” “supervision,” “planning,” “equipment,” and “communication.” This makes it easier to think about broader fixes rather than isolated problems.

For each item or theme, rate how much risk it represents (based on severity and frequency) and how much improvement you could gain by addressing it. Use simple ratings like high, medium, or low.

Roughly estimate effort and cost to tackle each issue, considering whether it requires new equipment, procedure changes, or additional staff time. Note any constraints such as client requirements or tight schedules.

With the review team, rank improvement opportunities by combining risk, impact, and feasibility. Identify a handful of “must do now” items and others that can be addressed over the medium term.

Agree on the top set of improvements that will move into a formal action plan, making sure they are manageable in number and within the team’s capacity to implement.

Use an existing company template or create a simple table with columns for issue, action, owner, due date, resources needed, and success measure. Keep the format easy to read and update.

For each priority item, write clear actions such as “revise orientation content to include near miss reporting,” “update ladder safety procedure,” or “add weekly supervisor safety coaching sessions.” Avoid vague actions like “improve safety culture.”

Name a specific person responsible for each action and set a realistic completion date. Confirm that owners understand and accept their responsibilities.

Note any budget, tools, or support required to complete actions, such as training materials, external trainers, or time set aside in meetings. This prevents plans that cannot be implemented.

For each action, describe how you will know it worked, such as a reduction in particular inspection findings, improved survey scores, or higher near miss reporting. Keep measures simple but meaningful.

Present the draft improvement plan to project or company leadership, discuss any adjustments, and obtain formal approval so the plan has visible backing.

Condense the review into a short summary that explains main strengths, main concerns, and high-level changes planned. Avoid technical jargon and keep the focus on practical impacts.

Decide what details to share with field crews, supervisors, project managers, and executives. Field crews need to know what will change in their daily work, while leadership may focus more on trends and program-level actions.

Hold a meeting or series of meetings with supervisors and management to walk through findings and the improvement plan. Allow time for questions and discussion of how changes will be implemented.

Use toolbox talks, crew huddles, or brief site meetings to explain a simplified set of findings and upcoming changes. Emphasize how changes will help them work more safely and efficiently.

Create one-page handouts or simple posters highlighting major safety changes and post them on safety boards and in trailers. Keep them up to date as actions are completed.

Let people know who to contact with questions or suggestions about the new measures. Encourage them to share whether changes are helping or if adjustments are needed.

Use a spreadsheet or software tool to track each action, its owner, due date, status, and notes. Link the log back to the Safety Program Review for context.

Schedule brief monthly or bi-weekly check-ins with action owners to review progress, obstacles, and any needed support. Update the log after each check-in.

For actions marked as complete, visit the work areas or review processes to confirm changes are actually in place and being followed, not just documented on paper.

Track incidents, near misses, inspection findings, and safety observations for trends related to the issues you targeted. Look for signs of improvement or areas where additional action is needed.

If certain problems persist despite actions, discuss why and consider additional or different measures. Update the action plan to reflect these adjustments.

Once major actions are complete and early impact is visible, document outcomes and formally close that review cycle. Note the date and focus areas for the next Safety Program Review so continuous improvement continues.