Skip to content
field operations2 min read

Keep a site-route note separate from the hired-plant condition record

Keep site-route note sources, identifiers and supplied scope distinct from hire condition photographs. Practical documentation examples for rental teams.

By AuditIt Editorial Team · Fact checked

Keep the site-route note source and identity with the supplied information. Link separately to condition photographs and observations.
Suggested filing relationship for site-route note; technical decisions keep their own evidence.

What to know

  • Keep the site-route note and condition record separately attributable.
  • Preserve the source, identity and scope exactly as supplied.
  • Mark a missing or mismatched reference as unresolved.

A delivery photograph can identify the machine that arrived, while a site-route note describes a plan or briefing supplied by someone else. Give the route note its own revision and source. That lets a colleague tell which site information accompanied the hire without inferring a route assessment from the machine image.

Retain the route note’s source and version

Record the plan or briefing title and the source that supplied it. Keep a later route revision separate from the earlier copy. A timestamp on the delivery photograph describes that submission; it does not date every feature drawn on a plan.

The Great Britain source used for this note is HSE’s Separating pedestrians and vehicles. Use that source for its own guidance and context. The filing format below is an editorial suggestion for keeping supplied records attributable; it does not reproduce a legal test, technical procedure or operating decision.

A suggested documentation note

  • Route-plan or briefing reference and supplied revision.
  • Source and received time of the site information.
  • Related delivery or handover record, with any version mismatch noted.

Example: preserve the document mismatch

In the fictional job SITE-R, a coordinator receives ROUTE-A before dispatch and ROUTE-B after delivery. Both references remain in the file with their received times. The delivery photograph stays a condition observation rather than confirmation that either route was assessed or followed.

The condition record in AuditIt

Choose the record shape for the condition task: equipment checkout and return uses before-and-after stages, while damage and pre-hire notes use a single visit. The wider AuditIt catalog also covers other industries.

Connect the condition record to the supplied site-route note through a document reference or a separately labeled note. The proposed fields above are editorial suggestions, not a claim that those fields are shipped defaults. The equipment checkout-and-return guide describes the existing condition workflow; explore AuditIt if it fits your process.

AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability. Keep any technical or legal decision attributable to its own evidence and the appropriate reviewer.

Prepared with AI assistance. Editorial review: AuditIt Editorial Team.

Direct answers

Frequently asked questions

Which route-plan version should be linked to a delivery?

Record the version actually supplied with that part of the file and retain later revisions separately. Leave any uncertainty about the applicable version visible.

Can the delivery photograph establish the route layout?

It preserves the submitted view. Keep route plans, briefings and any layout assessment separately sourced so a photograph is not expanded into a site-wide conclusion.

Sources

  1. Separating pedestrians and vehicles, Health and Safety Executive
  • workplace transport
  • equipment rental
  • condition records
  • site routes

Keep exploring