Guides
How industrial tour operators should organize trip records and guide files
Season folders for permissions, routes, guide packets and media keep an industrial tour program auditable across staff changes and shutdowns.
What to take away
- Open one folder per operating season, not one folder per site.
- Five subfolders carry the loadPermission, Route, Guide, Operations, Publication.
- Each subfolder has its own review trigger, so nothing waits for a year-end tidy.
- Keep a one-page index naming the current file in each subfolder, its owner, and its last-review date.
- Store originals apart from working copies so a figure can be traced back.
A season folder answers one question fast: what were we allowed to run, and what did we actually run? Sites like Sloss Furnaces and Pullman National Monument change their visitor routes around maintenance and construction, so last year's approved path is not this year's.
Name the folders the same way every season
Use the season as the top level, written so it sorts: 2027-spring, 2027-fall. Inside it, five subfolders. Same five names every year, so a new coordinator finds the permission file without asking.
Five Season Subfolders
- Permissionagreements, permits, insurance, photo approvals
- Routestop list, maps, access notes, alternates
- Guidescript, fact sources, induction, emergency contacts
- Operationsgroup logs, delays, incident notes
- Publicationimages, credit lines, booking copy
| Subfolder | What lives there | Review trigger |
|---|---|---|
| Permission | Site agreements, permits, insurance certificates, photo approvals | New dates, new route, or a change of site contact |
| Route | Stop list, maps, access notes, alternate plan, shutdown calendar | Building work, production restart, or a closed stair |
| Guide | Script, fact sources, induction date, emergency contacts | New guide, or revised interpretation |
| Operations | Group logs, delays, incident notes, maintenance observations | A repeated problem, or any disruption worth explaining |
| Publication | Images, credit lines, approved booking copy | Any public update |
The trigger column is the part teams skip. A permission file reviewed only in January will not tell you that a site contact left in June.
Write the one-page index first
One-Page Season Index
- Each subfolder named
- Current file in it
- Person who owns that file
- Date last reviewed
The index is what a site contact sees when they ask who approved a photograph, and what a new guide reads on day one. It also exposes a stale file before it gets copied forward, which is the usual way an outdated route survives into a new year.
Keep originals and working copies apart
Save the original confirmation, permit scan, or observation note before editing anything. Put shortened notes and edited spreadsheets in a working subfolder marked as such.
The Library of Congress guidance on long-term digital usability covers how preservation actions and documentation keep digital material usable as software and storage change. A tour operator does not need an archive, but does need enough context that a file still makes sense after a staff change.
The National Archives records-management FAQ index explains how records are identified and managed over time. It is not a retention schedule for a tour program. It supports plain file names, dates and versions, so the live route is never confused with a superseded one.
Log route changes and corrections in the same place
Every route change gets a date, a reason, an approver, the booking dates affected, and the public copy update. If a stair landing closes, record the alternate stop, what was sent to booked visitors, and when the original route can be reviewed again.
Treat a factual correction the same way. Note the source, the new wording, and where the old wording appeared. That stops a stale claim returning through a copied script or a partner listing.
Keep the public description in Publication beside the route version it describes. The U.S. Access Board accessible-routes guide explains how accessible elements connect to spaces and routes. It does not assess an individual request, but it is a reason to keep the actual route and alternate plan behind any access wording.
Restrict what each role can open
Guides need the current route, script and contacts. Visitor contact details, incident notes and unapproved quotations stay restricted. When a photographer or site owner withdraws permission, mark the asset unavailable and pull it from current promotion the same day.
At season end, write a handover note: route issues to watch, current contacts, open questions, approvals about to expire. Remove access that is no longer needed and name the owner of each current file.
Where a route has changed, the handover carries the current movement instruction. OSHA's exit-route guidance requires exit routes in covered workplaces to stay free and unobstructed.
The site's own procedure governs a visitor group, and a current approved route record keeps a retired path from being reused by accident.
Before the next season opens, factory tour questions for U.S. sites help compare how each route change lines up with the coming schedule.
Common questions
Should every guide see every file?
No. Give guides the current route, script, contacts and operational details. Personal data, incident notes and financial files stay with the coordinator.
Where do photo credits belong?
In Publication, with the original image, the credit wording, the licence or permission, and the publication date. Keep them together so a reprint request is one lookup.
What should a new coordinator open first?
The one-page index. It names the current file in each subfolder, who owns it and when it was last reviewed, which is enough to start work without reading old email.
How often should the index be updated?
Whenever a current file changes, and once at season end. An index that lags behind the folders is worse than none, because people trust it.
