Guides
How to keep industrial tour maintenance records that stay useful
A working maintenance log for industrial tours needs a closure note, a verification date and a named owner for every route condition found on site.
What to take away
- Seven fields carry each rowentry ID, date found, route location, condition, control or fix, owner, and status with closure note and verification.
- Write the row the day the condition is found, not at the end of the season.
- A closure note records the work. Verification names the person who re-walked the route, and the date.
- Mark a closed row closed. Never overwrite it, even when a later change reverses it.
- One file, one holder, one review date before each active tour period.
A guide can remember that a handrail was replaced. Nobody remembers the date, the cost, or who walked the route afterwards. Teams that keep maintenance records tied to individual stops lose fewer route changes between seasons.
The seven fields every row needs
Fill the row when the condition is found. A log written at season's end is a summary, not a record.
Seven fields per condition
- Locationwhere another person can find it
- Conditionthe fact, without speculation
- Immediate controlhow route kept safe
- Ownerperson carrying next action
- Due datereview point for open item
- Closure notewhat was actually done
- Verificationwho confirmed it, and date
| Field | What it holds | Example entry |
|---|---|---|
| Entry ID | Date plus a short tag, so rows sort and can be quoted in a briefing | 2027-0412-A |
| Date found | The day the condition was first seen, not the day it was reported | 12 April 2027 |
| Route location | Stop number and asset, findable without a guide | Stop 4, mezzanine handrail, north end |
| Condition observed | What is wrong, in words a new guide can act on | Lower bracket loose; handrail flexes when pushed |
| Control or fix | The temporary control used that day, and the permanent repair | Step moved off the mezzanine; two bolts replaced |
| Owner | One named person accountable for closing the row | Site maintenance supervisor |
| Status, closure note and verification | Open or closed, what the work was, who re-walked the route and when | Closed 13 April; route lead re-walked 14 April |
Field 7 holds three short lines. The closure note says what was done. Verification says a second person re-walked the route and saw the result. Collapsing the two is the fastest way to lose trust in a log.
Example: one loose handrail from discovery to closed record
- 12 April, morning. A guide finds the loose bracket at Stop 4 and fills all seven fields. Status: open. Owner: site maintenance supervisor.
- Same morning. The control goes in the row. The group skips the mezzanine, and the route card for that week is updated.
- 13 April. Two bolts are replaced. The closure note is written in the same row: what was done, by whom, on what date. Status: closed.
- 14 April. The route lead, a second person, walks Stop 4 and records the verification date in that row.
- Same day. Route card, site map, and booking text are updated from that one row, not from memory.
- June. The handrail comes out for a rebuild. Open a new row and point it back at 2027-0412-A.
Where the log lives
A shared Google Sheet or Excel workbook suits most single-site tours under a few hundred rows a season. A shared document works when you attach photographs. A computerized maintenance management system (CMMS) earns its place when the site's facilities team already issues work orders, because the repair and the record then share one number.
What a site will release, and when, varies by park, plant and province. The questions worth asking before you promise a group anything are collected in regional questions for U.S. sites.
- One file, one holder, write access for the route lead only.
- Read access for every guide who walks the route.
- No attendee names, payment details or personal access arrangements in the rows.
- A backup that survives the holder leaving.
Retention: a decision rule, not a habit
The IRS guidance on how long to keep records ties the period to what a record supports. That sets the principle for a route log, not the number.
Workable default, not a legal standard: hold every row while the condition it records can still affect the visitor route. Keep rows tied to a paid repair for seven years beside the invoice. Archive the rest after three seasons, in a read-only file you can still search.
The National Archives records-management FAQ is worth reading for the lifecycle idea: a record is created, maintained, used, then archived.
Where a repair was paid for, keep the invoice with the row. The IRS recordkeeping guidance explains that records supporting income and expenses should be held. Repairs with a budget line belong in your factory tour scope checklist as well as the log.
Closing notes and reversals
A route that changed in March and changed back in June needs both rows. Mark the first closed, keep the final condition, and point to the row that replaced it. A log with holes cannot explain why a path looks the way it does.
Reversals are the useful part of the history. They are also where route-check mistakes tend to hide, because a guide working from an old map will restore a retired path without meaning to.
