Toolbox Talk - Project Reviews That Resolve Interfaces

HOP skills practice • Batch 5, topic 33 of 52. A 5–10 minute toolbox talk plus time for actual field verification. One-page PDF and editable Word talk; separate supervisor and attendance forms.

What is this skill?

A project review brings affected people together to resolve decisions and interfaces before release.

Why use it?

Agreement in a meeting can leave a practical gap if nobody owns the action or supplies the evidence.

When should we use it?

Before important project decisions, modifications and release milestones.

Where does it apply?

With the people who prepare, review, use and maintain the result.

Learning objective

Turn one interface concern into a documented decision, owner and release condition.

Key hazards or failure points

Missing stakeholders; unreviewed documents; assumed agreement; actions closed by meeting minutes alone.

How to use it — practical controls

• State the decision needed and circulate the current information with enough preparation time.
• Ask affected roles to explain interfaces, limitations and contrary evidence.
• Record decisions, unresolved items, owners and due points. Confirm closure before dependent release.

Verify It in the Field

• Trace one release condition to an actual result approved through the required process.
• Paper practice: one team supplies equipment and another assumes training is included. Identify the gap.
• Assign ownership and evidence for readiness. A verbal promise does not close the action.

For real work, record the control, governing source and criterion, safe method, authorized checker, actual result and time. Mark VERIFIED, HOLD/NOT VERIFIED, or N/A with a reason. A practiced skill or matching label does not demonstrate that a physical safeguard functions. Do not create exposure to complete a check.

Stop and reassess

Hold the affected release if required representation, evidence or action closure is missing. Escalate unresolved disagreements.

Toolbox talk questions

• Which affected role is missing?
• What exactly remains open?
• What evidence permits the next step?

Examples across different work settings

These are original teaching examples, not operating instructions. Use paper, photographs or inert training items for practice. Change the setting to fit your team while retaining the skill steps and the applicable task requirements.

Equipment procurement

The supplier’s delivery scope does not include commissioning. The review assigns the missing responsibility and prevents delivery from being mistaken for readiness.

Campus move

The move team assumes building staff will update emergency information. The review identifies the owner and confirmation needed before occupancy.

Production change

Maintenance and operations expect different return-to-service steps. Both review the applicable process and resolve the handoff before the change proceeds.

Practice the skill and understand its limits

Give two people fictional role cards with conflicting assumptions about the same handoff. The facilitator must surface the difference, record it and identify a resolution path. The aim is a clear release condition, not forced consensus.

Leader follow-through — improve the conditions

Keep decisions and action evidence accessible after the meeting. Do not add meetings when the real constraint is missing expertise or authority.

Short supervisor field check

• Decision and current document set are identified.
• Affected roles and interfaces are represented.
• Concerns and differing views are recorded.
• Release conditions have evidence and authority.
• Actions have owners, due points and verified closure.

Use the separate supervisor sheet to retain evidence, open items, correction owner, recheck result and required restart authority. Keep task-specific permits, inspections and technical decisions in their established process.

Attendance and follow-through

Use the separate attendance sheet for participants, roles, questions, actions and rebriefs. Attendance does not establish competence, verify a control or authorize work. Keep completed records private under employer procedures.

Source acknowledgment

Based on DOE-HDBK-1028-2009, Vol. 2 (June 2009). No claim to authorship or copyright ownership of original U.S. Government work. Todd Jerome Jenkins adaptation; no government endorsement implied. Explanations, examples, practice exercises and layouts are original adaptations. Third-party material credited in the handbook retains its original attribution; this notice does not claim rights in that material.

Source file inspected: Volume 2/VOLUME 2 PROJECT REVIEW MEETING.pdf; printed pages 66–67. Source concepts paraphrased; historical mandates, guarantees and third-party wording are not reproduced.

Technical scope and references

References reviewed October 13, 2026. DOE human-performance tools and OSHA recommended practices support preparation and discussion; they do not establish universal technical acceptance criteria. Apply the current task procedure, manufacturer instructions, permit and required competent or qualified decisions. A successful exercise does not replace required training, technical verification or work authorization.

1. DOE-HDBK-1028-2009, Volume 2 — Reviewing a project decision — June 2009 illustrative guidance; Printed pp. 66, 67. Original ZIP excerpt inspected in full; no claim of universal mandated process.
2. OSHA — Communication and Coordination — Recommended practices: exchange hazard information and coordinate scheduling and responsibilities across employers.

The DOE handbook is June 2009 illustrative guidance, not a current requirements document. Availability of the official edition and the linked supporting guidance was checked October 13, 2026. Apply current task-specific requirements, manufacturer instructions, permits and required competent or qualified decisions; this talk supplies no universal technical acceptance criteria.

Connect this discussion to your JHA/JSA

Use the JHA/JSA planning and field-verification worksheet to record the actual task steps, hazards, responsible roles and controls. Return to What Changed Today? when the plan or conditions change.

Related Todd Jerome Jenkins articles: How to Conduct a Job Safety Analysis and What Is Human and Organizational Performance?.

Related toolbox talks

• Technical Task Briefing: Clarify the Deliverable Before Work
• Decisions Under Uncertainty: Make the Trade-Offs Visible

Practice another HOP skill

• Toolbox Talk - Briefing a Technical Task
• Toolbox Talk - Planning Resources for Safe Work
• Toolbox Talk - Decisions Under Uncertainty
• Toolbox Talk - Problem Solving with PACTS

One next step

Use the free JHA/JSA planning and field-verification worksheet linked above to apply this skill to one actual task step. Record what must be checked before exposure and who will check it.