Repeatable tests, clean sign-offs.

Turn test plans into signatures. These forms mirror interlocks, devices, modes, and acceptance criteria, with fields for measurements, media, and witnesses. Use them for loops, sensors, EFO, failure modes, and throughput. Standardized evidence closes NCRs quickly and proves crash rated bollard performance under real operating conditions. 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.

918.1 Hold/witness point notice

Pre-filled with ITP line, date, prerequisites (714, 631). Schedulers align trades.

Use a simple notice to lock in the ITP line item, date, and prerequisites from 714 — ITP and 631 — Pre-Commission Checklist. This creates a shared trigger for hold or witness points so everyone knows when to stop and call the lead witness.

Include fields for scope, reference drawings, equipment IDs, and pass/fail criteria. Affected trades (civil, MEP, controls) add readiness notes and attach evidence from earlier activities (e.g., 633 — Loop & Sensor Proving). For UAE jobs, add an authority attendance field and a link to SIRA Bollards (UAE) where needed.

AspectWhat mattersWhere to verify
PerformanceTested system (bollard + foundation)Global crash ratings
OperationsDuty cycles, fail-state, safety devices & measuresInstallation Guide

918.2 SAT witness script form

Row-per-test matching 634. Signatures and media refs prove crash rated bollard behavior.

Build the form so each row corresponds to a test step in 634 — Interlock Matrix Verification and the 638 — SAT / Witness Procedure. Capture device IDs, setpoints, interlock matrix row, expected outcome, and actual result with a media reference (photo or clip ID). Use a witness signature block per row so partial re-tests are traceable.

Where bollards are HVM-rated, note the SoO state, mode, and any overrides enabled. If authority attendance is required, annotate their initials in the dedicated column. Link back to the 916 — Evidence Capture Templates for filename conventions and timestamps.

918.3 Loop/beam proving sheet

Tuning values, screenshots, pass bands (344–345). Attach photos (916).

For induction loops and photo-eyes, record controller type, channel, sensitivity, and stability checks from 344 — Induction Loops and 345 — Field Devices. Include screenshots of detector status and any pass band or debounce settings used to limit nuisance trips.

Confirm loop & sensor proving with test pieces (e.g., motorcycle surrogate) and mark positions on a sketch. Attach media per 916 — Evidence Capture Templates and reference the acceptance band used for each device.

918.4 EFO timing sheet

Start/stop stamps, sequence notes, cooldown checks (354, 637). Confirms HVM bollard readiness.

Measure end-to-end EFO timing from initiation to safe state using synchronized clocks. Record sequence notes (interlocks satisfied, annunciation order, beacons) and environmental conditions. Cross-reference to 354 — EFO & overrides and 637 — EFO & Failure Modes.

Verify EFO cooldown rules and battery/accumulator pressures (before/after). Where systems are integrated to BMS/SCADA, capture the audit trail snippet and operator acknowledgements.

918.5 Obstruction/intrusion test form

Objects used, outcomes, auto-reverse distances (635). Human-factors notes (353).

Record the object size/placement and expected auto-reverse behavior under 635 — Obstruction & Intrusion Tests. Note detection paths (beam/edge/loop), stopping distance, and reversible distance achieved. Add human-factors observations from 353 — Safety Signalling (visibility, annunciation, night mode).

Include a field for residual hazards and immediate mitigations, plus a retest row if parameters are adjusted (e.g., beam hood or receiver gain changes).

918.6 Drainage inspection form

Sump levels, outfalls, seals/glands (334, 245, 347). Prevents ingress.

Log sump freeboard, pump function, and outfall condition per 334 — Drainage and 245 — Drainage strategy. Check seals/glands for ingress, and confirm enclosure IP rating elements from 347 — Enclosures & Cabling.

Where high groundwater is suspected, add a buoyancy/floatation check box and photo of the non-return path. Capture maintenance notes for the operator handbook.

918.7 Foundation inspection form

Rebar/cover, anchors, cages, spacers (621–623). Matches design (333).

Before pour, check cage dimensions, cover spacers, and anchor templates per 621 — Rebar Cages & Anchors, 622 — Sleeves & Glands, and 623 — Formwork & Cover. After pour, verify finish, honeycombing absence, and alignment against 333 — Design checks.

Photograph each stage with a calibration photo board and index the images for the as-built pack and NCR closure if needed.

918.8 Alignment & gap sheet

Datums, plumb, clear gaps with tolerance bands (626, 232). Accept/reject criteria explicit.

Record datums from 626 — Datum & Alignment Checks and measure clear-gaps across the lane using a go/no-go gap gauge. State the tolerance band from 232 — Spacing rules, and capture plumb and rotation against the datum stick or index plate.

Where arrays are mixed-type, note the degraded state clear-gap and add a retest reminder after any mechanical adjustments.

918.9 Punch list & rectification

Defect, owner, target date, retest proof (639). Ensures close-out.

Log defects with severity, owner, target date, and specific verification of effectiveness evidence needed. Link directly to retest rows, media IDs, and the final sign-off matrix in 639 — Snagging & Handover.

For persistent issues, record containment, corrective and preventive actions to support NCR closure and the client’s O&M updates.

Related

External resources

918 Witness & Inspection Forms — FAQ

What’s the fastest way to prove SAT steps without missing signatures?
Use the row-per-test script tied to your 634 interlock matrix, and include a witness signature block in each row. That way partial re-tests keep their original evidence chain, and media IDs map cleanly to each acceptance criterion.
How do we handle EFO timing when conditions vary?
Record environmental conditions, interlocks satisfied, and device states alongside start/stop timestamps. Apply the defined EFO cooldown window and repeat three trials; keep the median and note any deviations or inhibits observed.
What counts as acceptable loop/photo-eye proving evidence?
Include detector settings (gain/sensitivity), stability screenshots, and a sketch/photo showing test piece positions. Add pass bands, nuisance-trip checks, and at least one video clip confirming detection and recovery for each mode.
How do punch lists link to NCR closure?
Each punch item should include root cause, containment/corrective/preventive actions, the retest row ID, and a final sign-off. When the verification of effectiveness is attached and signed, the NCR can be closed with traceable evidence.