Photos, forms, and proofs—ready.
Don’t reinvent evidence on every project. This kit provides photo logs, inspection checklists, witness forms, and data sheets that mirror ITP/SAT steps and rating dependencies. Use them to capture foundations, alignment, clear gaps, controls, and safety tests the same way every time—so crash rated bollard claims remain credible and auditable. 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.
916.1 Photo checklist (field use)
Step-by-step prompts for framing, scale references, and angles. Geo/time-stamp required per 716. Use it on HVM bollard pours, alignment checks, and crash rated bollard spacing proofs (626, 232).
(a) Use a georeferenced photo log with time timestamp to tie every image to its exact pour or check. Capture a wide→detail set: site context, array run, individual unit, and close-up of the proof (e.g., scale reference next to the clear-gap).
(b) Photograph in the sequence used by the SAT / witness procedure and your ITP. For pours, include rebar cage, cover chairs, sleeve penetrations, conduit entry, and concrete finish per Pouring & Vibration (624) and Datum & Alignment Checks (626).
(c) For spacing proofs, frame the run so the array centreline and edge references are visible; add a measuring rod to demonstrate the clear-gap rule from 232. Cross-link photos to the Page-ID reference in captions.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Ratings Explained |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
916.2 Video walkthrough script
Shot list for pre-pour, set-out, loop tests, EFO sequences (633, 354). Narrate Page IDs so clips drop straight into reports (911).
(a) Keep clips short (20–40s) and label each with the Page-ID you’re covering: pre-pour checks, set-out markers, conduit identification, and pour sequence. State the witness point and ITP line before you roll.
(b) For controls, film loop & sensor proving (633), including detector gain and cross-talk checks. Capture an EFO evidence log and narrate the override path (354).
(c) End each clip with “Result: pass/fail, reference 716” so reviewers can scan quickly. Save raw files; do not apply filters or trimming that could compromise authenticity—see Evidence & Documentation (444) and File Index & Naming Rules (911).
916.3 Measurement record sheet
Tabular form for levels, gaps, plumb, torque—tolerances prefilled (312, 315). One row per bollard preserves crash rated bollard traceability (421).
(a) Create one sheet per array. Include station ID, bollard ID, height per 312 Height setting, plumb/level within acceptance band, projected gap, and fastener torque sheet values.
(b) Prefill tolerances from 315 Tolerances & Manufacturability and add a notes column for tolerance budget remarks. Link each row to its supporting photo(s) from 916.1.
(c) Add a compliance tick for rating-critical dependencies (421), e.g., concrete class, sleeve type, and embedment depth. This preserves traceability if a nonconformance is raised under 719.
916.4 Test & calibration forms
IR/continuity, loop tuning, beam tests, pressure/flow (632–634, 344–345, 512). Evidence anchors HVM bollard commissioning.
(a) For electrical tests, include IR, continuity, and polarity. Log instrument ID and calibration expiry. File results under 632 Power-On & Controls Health.
(b) For sensing, record photo-eye alignment, receiver gain, and loop tuning (633). For safety devices & measures, capture obstruction and intrusion tests per 635.
(c) For hydraulics, log standby pressure, relief settings, and flow on the HPU (512); attach photos of gauges and the pressure test port. Close with an EFO trial and record the EFO timing window from 354.
916.5 Chain-of-custody log
Sign/transfer log for media and meters. Reviewer trust improves (444).
(a) Use a simple chain of custody table: item ID, description, timestamp, handler, handover to, signature, condition notes. Link each item to its Page-ID and storage path.
(b) Apply to raw photos/videos, meter downloads (e.g., dataloggers), and calibration certificates. Cite in submissions under Evidence & Documentation (444) and cross-reference Final Archive & Retrieval (939).
916.6 File naming helper
Auto-builds names from fields; mirrors 911. Export CSV for bulk rename.
(a) Mirror the structure in File Index & Naming Rules (911): Site-ID, Page-ID, evidence type, short subject, date/time, and checksum if used.
(b) The helper can output a CSV with source path and new filename; use your OS bulk-rename tool. Keep names human-readable and consistent with the filename convention.
916.7 Reviewer acceptance checklist
What reviewers expect: clarity, Page IDs, pass/fail statements (717).
(a) Before submission, confirm: (1) every image has a clear subject and scale, (2) all clips say which test or witness point they cover, (3) every test has a pass/fail statement and reference to Authority Submittals (717).
(b) Spot-check against 716 Evidence Capture Standards. If approval in UAE is in scope, add a brief note and link to SIRA Bollards (UAE) so reviewers understand the local context.
916.8 Common defects gallery
Photo examples of fails (honeycombing, ponding, misalignment) with links to fixes (624, 629).
(a) Include typical concreting flaws like honeycombing and ponding with a one-line “so what” (e.g., might reduce cover or cause corrosion). Link each to the corrective step in 624 Pouring & Vibration or 629 Surface Reinstatement & Interfaces.
(b) For alignment defects, show gap drift, tilt, and rotation; include a Go/No-Go gauge shot to prove compliance.
916.9 Zip bundle recipe
Folder tree and manifest file for upload to packs (938). One-click import.
(a) Build a repeatable folder tree: 00_Covers, 10_Photos, 20_Videos, 30_Measurements, 40_Tests, 50_Approvals, 90_Manifests. Place a CSV manifest listing position, filename, Page-ID, witness point, and evidence type. See Submission-Pack Guidance (938).
(b) Export a single ZIP named per 911 and upload with your submission or handover. Keep a copy in the archive per 939 Final Archive & Retrieval.
Related
External resources
- NPSA — HVM Guidance
- ASTM F2656 — Crash-Rated Barriers Overview
- BSI — Vehicle Security Barriers: Impact Test Specs
916 Evidence Capture Templates — FAQ
What minimum evidence should I collect for a concrete pour?
Capture rebar cage and cover, conduit entries, sleeve positions, pour sequence with vibration, and finish. Include wide→detail photos with scale, a short narrated clip, and a pass/fail note tied to your ITP line and Page-ID.
How do I prove spacing compliance without a survey crew?
Use a marked datum stick and a Go/No-Go gauge at the defend line. Record photos showing the array centreline, edge references, and gauge in place, then log the value in the measurement sheet for that bollard.
What makes video evidence acceptable to reviewers?
Short clips labeled with Page-ID, clear narration of the step or witness point, steady framing, and an explicit pass/fail statement. Keep raw files untouched and maintain a chain-of-custody log.
When should I link to SIRA requirements?
When the project is in the UAE or SIRA approval is in scope. Add a short context note and link to the site’s SIRA page so reviewers understand the local approval path and evidence expectations.