What records to keep to justify low-speed choice.
Approvals hinge on well-structured evidence. This page lists everything reviewers expect for HVM bollard and crash rated bollard submissions: annotated photos/plans (912, 936), rating certificates (431), equivalence notes (414), QA/ITP records (714), and witness forms (638). We show how to package files with naming/versioning (911, 115) and link to submission-pack guidance (938, 717) and handover deliverables (731–736, 739). Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.
Important: This is a general guide. For live projects we develop a tailored
Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.
444.1 What to collect pre-design
Capture site photos, surveys, VDA notes, utilities, and standoff sketches (211–219, 213). Early evidence frames the HVM bollard or crash rated bollard scope.
Before drawings, build a compact site assessment pack with a wide→detail photo set, a key plan, and short notes on VDA inputs (run-up, angles, vehicle class). Add utility constraints from PAS 128/GPR work so reviewers see real-world limits. Record tentative spacing rules and any people-flow hotspots near glazing.
Use dated, georeferenced images and label vantage points on a simple key plan. Note any approval dependencies (e.g., SIRA tier or mall landlord standards) and link to the mark-up standards you’ll follow. This groundwork makes later choices—low-speed vs HVM—traceable.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read ratings |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
444.2 What to include in submittals
Provide annotated plans, certificates, arrays/spacing calcs, ITP lines, and SAT plan (431, 232, 714, 638). Complete sets speed crash rated bollard approvals.
Minimum contents for low-speed packages: site plan with defend line and clear-gap callouts; section/typical for the selected device and foundation; certificate (PAS 170-1 or ASTM F3016) plus limits; calculation note showing approach/run-up vs tested speed band; and an SAT/witness outline scaled to low-speed commissioning. If the environment is hostile, escalate to HVM and reference standards equivalency policy.
444.3 Photos/plans/redlines
Use dated, geo-tagged media and mark-ups (716, 936). Visuals make HVM bollard reasoning obvious.
Follow the Mark-Up & Overlay Standards: arrows, colours, and consistent layers so reviewers can read deltas instantly. Maintain a photo/redline logbook and keep an evidence capture template handy for repeat shots at the same locations. For storefront risks, include glazing offsets and kerb-to-facade dimensions.
444.4 Certificates & declarations
Attach certificates, limits, and renewal dates (431). Declarations link each installed crash rated bollard to evidence.
Check the certificate detail: report number, tested orientation, penetration class, limits, and photos/footage. Add a brief equivalence note if you’re mapping PAS 170-1 to ASTM F3016 use-cases (or vice-versa). Finish with a site-specific declaration that the installed device and foundation match the certificate’s as-tested configuration.
444.5 QA & test records
Include cube tests, set-out surveys, gland/IR tests, and loop tuning (624, 626, 347, 344). QA shows the HVM bollard matches intent.
Even for low-speed devices, record concrete maturity/cube breaks where relevant, datum & alignment checks, cable gland plate inspection, and loop sensitivity settings if detection is used. Include a brief ITP excerpt that points to evidence and pass criteria.
444.6 Witness/inspection forms
Provide hold/witness sign-offs and punch lists (714, 638). Forms streamline crash rated bollard sign-off.
Use the standard witness & inspection forms with clear SAT scripts, acceptance bands, and named signatories. This reduces email churn and helps authorities (including SIRA where in scope) verify live function quickly.
444.7 As-built & O&M links
Link drawings, manuals, spares, and training (731, 733, 737). As-builts preserve HVM bollard maintainability.
Create a short “operations” index pointing to as-built drawings, O&M manuals, and the training plan. For automatic systems nearby, add references to the controls pages so maintainers can find panel layouts and I/O quickly.
444.8 Versioning & filenames
Apply 911/115 rules so reviewers can track revisions. Good hygiene protects crash rated bollard traceability.
Name files per the File Index & Naming Rules and keep a submission index that lists superseded items. Use stable IDs (e.g., Site ID, Release ID) so later archival is effortless. Add a brief versioning note inside the index PDF.
444.9 Reviewer acceptance tips
Use a one-page index and highlight deltas. Clarity accelerates HVM bollard approvals.
Lead with a single-page reader guide, then group drawings, photos, certificates, and QA in that order. On revisions, mark changes with clouded deltas and include a short comparability note if devices/arrays changed. For UAE projects, mention where SIRA review applies and cross-reference their specific evidence needs.
Related
External resources
444 Evidence & Documentation — FAQ
What minimum documents prove a low-speed bollard is suitable?
A site plan with clear-gap/defend line callouts, the low-speed certificate (PAS 170-1 or ASTM F3016) with limits, photos/redlines tied to locations, a brief VDA note showing approach speed/angle, and an index that maps every drawing/photo to the proposed device and foundation.
When should I escalate from low-speed to an HVM/crash-rated solution?
Escalate when credible approach speeds exceed low-speed bands, when hostile intent is plausible (crowd proximity, sensitive frontage), or when the site geometry creates long run-ups. Use the selection pages and document why HVM is required in the submission index.
How do I show that my installed product matches the certificate?
Include a short declaration that lists model/family, height/diameter, sleeve, foundation class, and orientation, then cross-reference to photos and drawings. Add set-out and alignment checks and any commissioning forms relevant to function.
What filename pattern helps reviewers track revisions?
Follow the site’s File Index & Naming Rules with stable IDs (project-site-discipline-seq-rev). Keep a superseded file list and highlight deltas on drawings; update the index cover each time.