Guides
How to keep industrial tour planning records that survive a handover
Open the planning file before the first pilot and keep the decision path intact, so the next operator can see why the tour works the way it does.
What to take away
- Open the planning file before the first pilot, not after it, so raw observations land somewhere permanent.
- Keep the decision path wholeproposal, source, decision, approver, date. A choice without its source cannot be defended later.
- Store signed approvals and original emails apart from edited route maps and summary sheets.
- Record the date every version of booking copy went live, and keep the version it replaced.
- Do not delete required records during a cleanup. Archive superseded working copies instead.
Open the file before the first pilot
Most operators start the file the week the booking page goes live. By then the useful material is gone: the walk-through notes, the first refusal from a site manager, the reason a stop moved.
Start the file the day you ask a plant for access. The first entry is the request itself.
A pilot produces the evidence that justifies the finished product. Timing runs, group behaviour at a stairwell, where a group bunches at the furnace aisle, the stop that ran long. None of it survives in memory past the second rehearsal.
Planning records built this way answer three questions fast: what the operator was permitted to offer, what the site required, and why the visitor experience looks the way it does.
Keep the decision path as a chain
A decision on its own is an opinion. A decision with its source, its approver and its date is a record.
Five-part decision record
- Proposal as written at the time
- Sourcesite email, pilot observation, rule
- The decision itself
- Who approved it
- The date
A later manager should be able to read that chain and see why a stop was removed, why a group limit dropped, or why a visitor notice appeared. Without it, the next team re-litigates settled questions or, worse, quietly reverses them.
Never overwrite a past file with a newer one. Add the new version and leave the old in place.
Separate originals from working copies
Originals vs working copies
Originals
- Examples
- Signed approvals, permits, raw pilot notes
- Handling
- Keep apart, never overwrite
- Naming
- Date first, then purpose
Working copies
- Examples
- Route maps, spreadsheets, draft itineraries
- Handling
- Label as copies, date first
- Naming
- Avoid final, final2, final-v3
Name files with the date first, then the purpose. A folder of files named final, final2 and final-v3 tells the next operator nothing about which one the site actually approved.
The National Archives schedule for planning and design project files covers records that document critical planning decisions, approvals and meeting summaries. A small operator does not need a federal records program. The principle transfers: keep what explains the decision, not only the polished itinerary.
The National Archives records-management FAQ index is general background on records that stay readable and usable over time. It is not a retention schedule for a tour file. It supports one habit: name the document, show the date and version, make the current record obvious.
File the public copy with the plan
Booking pages, confirmation emails and guide packets are records of what visitors were told. They belong in the planning file, not in a marketing folder.
When the route changes, keep the previous version and note the date the replacement published. Otherwise nobody can tell which promise a group saw in March.
The U.S. Access Board accessible-routes guide explains how accessible elements connect to the spaces around them. It cannot settle an individual access request. It is a reason to retain the actual route version and any confirmed alternative, rather than a general statement of access floating free of the itinerary.
Log every material change
For each revision touching the route, capacity, visitor information or partner responsibility, record these details. Record the date, what changed, why, who approved it and what follow-up remains.
If a stairway closes, log the alternative stop and the date the booking page changed. If a new fact replaces an old one, log the source and every place the old wording appeared.
The Occupational Safety and Health Administration exit-route page states that exit routes in covered workplaces must stay unobstructed. The host site's procedure governs a visitor group. Retaining the approved movement instruction stops a superseded route being reused by default.
Hand over with a review list
Close a planning cycle with a one-page handover. It should cover:
- approvals to renew
- open risks
- access details to reconfirm
- guide training due
- evidence still unreviewed
- the name of the person who owns each item
Attach the site's current route or operating instruction to that page. A handover without it is a pile of undated files.
Close access at handover
Keep restricted attendee, payment and vendor information outside the general planning folder. Give guides and partners only what their role needs.
Review access when the file changes hands, so an outdated contact list does not stay open.
At the end of each review period, identify the current route file and archive superseded working copies. Do not delete required records under a casual cleanup routine. The active material should be easy to find and the evidence behind it should still exist.
Common questions
Who should own the planning file?
One named operator or manager, with access for the people who need current route and guide information. Shared ownership without a name is how versions multiply.
Should visitor personal data sit in the planning file?
Only where necessary and authorized. Keep attendee, payment and vendor details in a separate restricted location.
When does the decision log get updated?
Whenever a decision changes the route, capacity, visitor information, partner responsibility or launch date. Log it the day it changes, not at the end of the season.
