Toolbox Talk - Shared Dependencies Between Controls

HOP skills practice • Batch 6, topic 48 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?

Dependency tracing asks whether different controls rely on the same information, support or action.

Why use it?

Two controls can look separate while relying on the same input or person. Counting them does not establish separate protection. Trace their needs and flag shared dependencies for review before relying on them.

When should we use it?

During planning or when a change may affect more than one protective measure.

Where does it apply?

On approved plans and records, with safe observation and specialist review as needed.

Learning objective

Identify a possible shared dependency and obtain qualified assessment without defeating or testing safeguards.

Key hazards or failure points

Two displays fed by one source; two checks repeating one assumption; shared support overlooked; a backup unavailable for the same reason as the primary; unauthorized testing to prove independence.

How to use it — practical controls

• Name each control’s function and supporting inputs. Mark uncertain connections as questions.
• Ask the responsible technical person to assess suspected dependencies against current documentation. A sketch cannot establish independence.
• Maintain required protection during review. Implement changes only through the governing approval and verification process.

Verify It in the Field

• Draw two fictional review boxes that both copy one source list. Ask what happens if that list is wrong; do not calculate a failure probability.
• Trace real documented inputs and permitted visible identifiers. Record evidence and unknowns without opening equipment or disabling protection.
• Review the authorized disposition and prescribed check results. Matching displays or two signatures alone do not prove separate protection.

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 affected reliance when a required control is unavailable, its basis is unknown or a discovered dependency challenges the approved protection. Follow the task’s safe-state process and seek the required review. Never remove one safeguard to see whether another catches the problem.

Toolbox talk questions

• What does each control depend on to work?
• Which shared input is confirmed, and which remains uncertain?
• Who can assess the dependency and approve any change?

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.

Document review

Two reviewers use the same outdated source list. The team asks how source currency is established; adding another signature would not resolve that input.

Facilities

Two indicated statuses may share an underlying information source. The team asks the responsible specialist to confirm the arrangement without disconnecting or testing equipment.

Event planning

Two fallback arrangements rely on the same unavailable contact. The planning team verifies actual support rather than counting two entries as two available options.

Practice and discuss

Use a drawing with two arrows from one fictional source. Ask participants to distinguish the documented connection from an unverified assumption about failure. A shared input does not by itself mean the design is unacceptable; suitability and required independence need the appropriate technical assessment.

Leader follow-through — improve the conditions

Include support changes in reviews of affected controls. Study the quality of source information and availability of backup resources. Avoid reliability claims based on how many controls are listed.

Short supervisor field check

• Each selected control has a defined protective function.
• Dependencies traced to current approved information; uncertainties marked.
• Actual identifiers or records compared without equipment manipulation.
• Responsible technical authority evaluates significance and restrictions.
• Approved changes have required verification evidence and release.

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. 1 (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 1/VOLUME 1 CHAPTER 2-REDUCING ERROR.pdf; printed pages 2-11–2-12. Archived reliability calculations, diagrams and categorical independence claims are excluded. Original dependency sketch exercise.

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 1 — Chapter 2, printed pp. 2-11–2-12 — June 2009 conceptual discussion of dependency and checks. Reliability calculations, diagram and categorical independence claims excluded.
2. OSHA — Hazard Prevention and Control — Recommended practices on selecting effective combinations of controls, consulting expertise and verifying implementation. Does not establish system independence or a redundancy requirement.

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

• Independent Verification: Confirm Without Being Led
• What Does This Control Actually Do?

Practice another HOP skill

• Toolbox Talk - Getting Help with Unfamiliar Work
• Toolbox Talk - Resolving Competing Assignments
• Toolbox Talk - Understanding Control Functions
• Toolbox Talk - Recognizing Confusing Controls

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.