Vendor Interfaces: Verify the Handoff and the Evidence

Human Performance weekly series: lesson 39 of 52.

A 5–10 minute crew discussion, plus time to verify the actual controls. The crew talk and Word version are public. Separate supervisor and attendance records are included with free Safety & Systems membership.

Why this matters

A vendor may know its equipment well and still be unfamiliar with this site’s hazards or release process. The site team may understand local conditions but miss a product limitation. A useful handoff brings both kinds of knowledge together before anyone relies on the work.

Learning objective

Confirm one vendor interface, its shared control and the evidence required before acceptance or use.

Key hazards or failure points

Unclear scope; incompatible site and vendor instructions; unbriefed personnel; missing product records; changed equipment; two parties assuming the other verified a control; completion mistaken for readiness.

Practical controls

• Before work, compare the contracted task with actual location, equipment and nearby activities. Exchange site and vendor hazards, required competence, emergency arrangements and applicable instructions. Name who resolves conflicts and approves changes.
• Assign each important interface: who establishes, checks, maintains and releases the control. Keep employer, technical and permit responsibilities under their applicable processes. Vendor experience does not remove local orientation or required verification.
• Agree the deliverables and acceptance evidence before the handoff. Identify inspection or test records, equipment identity, restrictions and open items needed for the actual scope. Do not accept an assurance as a substitute for a required record or check.

Verify It in the Field

• Ask site and vendor representatives separately to describe one shared control and its owner. Compare their answers at a safe observation point or on the current plan. Resolve gaps before work; record the agreement and responsible contacts.
• Trace one consequential vendor statement to applicable evidence. Match the product or equipment identifier, revision, conditions and required acceptance source. Have the designated competent or qualified person perform any necessary technical check through the approved method.
• Before handover, compare the delivered status with the acceptance requirements. Confirm open issues, authorized restrictions and the receiving person’s understanding. Record actual findings, checker and time; sign only for the scope your role permits and confirm affected crews receive changes.

Stop and reassess

Hold affected work or reliance for conflicting instructions, unidentified responsibility, missing evidence or a change outside the agreed scope. Make the task safe through its procedure and contact the designated authorities. Do not solve a contract or technical dispute by improvising the work. Recheck before authorized release.

Crew discussion questions

• What local condition could the vendor miss?
• Who owns this control through release?
• What evidence supports accepting this deliverable?

For each required control, record its acceptance source and criterion, safe verification method, responsible checker, actual result and time. Use VERIFIED, HOLD/NOT VERIFIED, or N/A with a reason. A tick alone is not evidence. Complete all applicable task inspections; do not enter danger or improvise a test to fill out a form.

Leader preparation and practical detail

An orientation badge does not complete the interface

TBT48 addresses site-wide coordination. This lesson follows one vendor engagement from the agreed task to evidence at handover. Discuss actual operating restrictions, neighboring work and changes. Information must travel both ways: the vendor also needs to tell site personnel what hazards its equipment or method introduces.

Do not turn coordination into a legal shortcut

The historical source uses DOE contractor terminology and includes a co-employment caution. This adaptation does not assign legal employer status or suggest withholding safety coordination. Applicable laws, contracts and employer programs determine duties. OSHA recommended practices support exchanging hazards, planning work and resolving differences before exposure.

Accepted delivery is not equipment release

Illustrative situation: a repaired unit returns with an invoice saying complete, but the required test record is missing. Identify the technical evidence and authorized release process before use. Neither the invoice nor the vendor’s reputation proves the actual acceptance condition. Record restrictions and the receiving person’s responsibility for unresolved items.

Short supervisor field check

• Scope, location and hazards exchanged.
• Site and vendor roles agree on shared controls.
• Required competence and orientation confirmed.
• Deliverable evidence matches actual equipment.
• Open items and receiving authorization resolved.

Confirm the relevant trained/authorized people, unresolved items, interim protection, correction owner and recheck. Record required release authority and rebrief anyone affected. The separate sheet supports these records; it does not replace a specialist inspection, permit or engineering determination.

Attendance and follow-through

Use the separate attendance sheet for participants, roles, discussion concerns, actions and late-arrival rebriefs. Attendance is not proof of competence, functioning controls or authorization to work. Keep completed records private under employer procedures.

Source acknowledgment

This resource draws on the U.S. Department of Energy’s DOE-HDBK-1028-2009, Human Performance Improvement Handbook, Volume 2 (June 2009). Todd Jerome Jenkins makes no claim of authorship or copyright ownership in the original U.S. Government work. New explanations, examples, exercises and layouts are Todd Jerome Jenkins adaptations. No endorsement by DOE or the U.S. Government is implied. Third-party material credited in the handbook remains attributed to its source; this notice does not claim rights in that material.

Source excerpt: Volume 2/VOLUME 2 VENDOR OVERSIGHT.pdf; Printed pp. 68, 69. The June 2009 handbook supplies concepts; this lesson uses original explanations and exercises.

Technical scope and references

References reviewed October 9, 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 — Coordinating vendor work — June 2009 illustrative guidance; printed pages 68, 69. Historical concepts, not universal mandates.
2. OSHA Recommended Practices — Communication and Coordination — Current recommended practices; supports assigned responsibilities, worker input and evidence-based follow-through. Not a technical acceptance standard.

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. No task-specific worked example is linked for this topic yet. 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 crew discussions

• Site-Specific Safety Plan: Check the Interfaces Today
• Work Turnover: Transfer the State, Not Just the Story

Continue the weekly series

• Lesson 38: Work Product Review: Learn from the Work We Release
• Lesson 40: Independent Oversight: Find the Blind Spots

Put one check into practice

Use the free JHA/JSA planning and field-verification worksheet to record today’s change, the required protection and the evidence needed before exposure.