Guides
Factory tour safety checklist: what to settle before your 2027 launch
Factory tour safety scope checklist for 2027 helps U.S. operators separate visitor readiness, route decisions, host duties, and site safety responsibilities.
A tour program can coordinate visitors without taking over the facility's safety system. Use this checklist to define where the visitor program stops and where an assigned operations or safety role takes over.
What to take away
- Visitor readiness and workplace safety are connected but not interchangeable.
- Write down the approval path for route, capacity, and closure decisions.
- Send technical concerns to the site process instead of resolving them in a tour script.
Scope checklist
Visitor program owns
- Booking information
- What guests must know before arrival
- Route request
- Group size, timing, and desired stops
- Briefing
- Clear visitor instructions and host behavior
- Equipment
- Inventory of approved visitor items
- Disruption
- Guest communication and approved fallback
- Records
- Session changes and visitor-facing issues
Site safety or operations owns
- Booking information
- Facility rules and changes that affect public access
- Route request
- Approval of active areas and route conditions
- Briefing
- Required site-specific safety content
- Equipment
- Specification, control, and suitability of protective equipment
- Disruption
- Emergency direction and operational response
- Records
- Safety records, inspections, and corrective actions
OSHA's emergency action plan standard identifies responsibilities such as reporting emergencies, evacuation procedures, accountability, contacts, and employee training. A tour host should know how to reach the responsible people and follow the plan, not write a separate plan from memory.
Visitor program vs site safety
Visitor program owns
- Booking information
- Pre-arrival guest info
- Route request
- Group size, timing, stops
- Briefing
- Visitor instructions, host behavior
- Equipment
- Inventory of approved visitor items
- Disruption
- Guest communication, fallback
- Records
- Session changes, visitor issues
Site safety or operations owns
- Booking information
- Facility rules and changes
- Route request
- Approval of active areas
- Briefing
- Required site-specific safety content
- Equipment
- Specification and control
- Disruption
- Emergency direction and response
- Records
- Safety records and inspections
Questions to settle before launch
OSHA's communication and coordination guidance describes exchanging relevant worksite information and coordinating before on-site work begins. A visitor-program team should use that boundary by confirming the facility contact, approved visitor route or alternative, and the method for communicating a change. The team does not create its own technical safety plan.
OSHA's education and training guidance explains the value of current information about hazards, controls, reporting, and emergency roles for workers and managers. A visitor briefing is not worker training. It should use only the instructions the facility has approved for the visitor experience and tell the host where to direct an unexpected question.
The National Archives web-records guidance explains that online content can document official business. Keep the current visitor message and checklist result together. If a site condition changes, correct the guest-facing text and record the confirmed visitor effect.
Before the session, ask the designated facility contact for a visitor-facing confirmation. If the answer is not available, use the approved alternative, reschedule, or pause the visitor plan. Do not ask a host to make a technical judgment because a group has arrived.
Use the checklist in the order a visitor encounters the program: message, arrival point, check-in, briefing, approved route, questions, and departure. For each step, identify what the guest needs to know, who confirms the instruction, and what the host does if the normal plan changes. This gives a visitor-program team a clear operating boundary while leaving technical and emergency decisions with the facility.
After the session, record only the visitor-facing result. Note whether the planned format ran, which approved alternative was used, what public message changed, and who owns a follow-up item. That short record gives the next host useful context without creating a parallel safety file.
- Who can approve the route on the day of a visit?
- Who tells the host that a production or maintenance change affects access?
- What information may the host give guests about alarms, exits, and interruptions?
- What is the approved alternative when a planned stop is unavailable?
- Which system receives a reported hazard or maintenance concern?
Avoid vague handoffs such as "operations will handle it." Name a role, a contact method, and a backup. If the answer differs by shift, write that down.
Keep the handoff useful
When a host reports a concern, include location, time, what visitors encountered, and the immediate program action. Do not add an unsupported diagnosis. For example: "temporary barrier blocks the planned viewing line; group was moved to the west gallery; route confirmation requested." This gives the responsible team enough context to act while keeping the report inside the host's competence.
Common questions
Can a guide approve a new route?
Only if the site's documented authority assigns that approval. A guide may identify a visitor issue and use a preapproved fallback.
Is a visitor briefing the same as safety training?
No. A briefing gives guests the instructions they need for the visit. Required employee training and emergency preparation remain a site responsibility.
What should a tour record include?
Record the route used, material changes, responsible contact, and open follow-up. Keep sensitive operational details in the approved internal system.
