Inspection/Test Plan scope, hold points, and records.

The Inspection & Test Plan is your master checklist for build quality. It enumerates inspections, hold/witness points, acceptance methods, and sampling frequency for foundations, drainage, controls, and safety. Tie each line to drawings (931, 733), rating dependencies (421), evidence capture (716), and SAT/handovers (638, 736). Strong ITPs protect HVM bollard uptime and certification credibility. This page sits within this section and the broader chapter hub. If your project involves UAE approvals, see SIRA Bollards (UAE) for context and submittals. Where installation detail helps, refer to the What to Expect overview and the full 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.

714.1 Scope of inspections

Foundations, drainage, controls, safety (331–334, 343). Scope secures HVM bollard quality.

Define the ITP scope so it spans civil, mechanical, electrical, and controls checks that affect performance. Typical lines include excavation limits, cage placement, concrete quality, drainage sumps, ducting, enclosure ratings, safety devices & measures, and interlock matrix verification. Reference nearby detail pages such as design checks for foundations and safety circuits to ensure nothing critical is omitted.

AspectWhat mattersWhere to verify
PerformanceTested system (bollard + footing)Crash ratings explained
OperationsDuty cycles, fail-state, safetyInstallation Guide

714.2 Hold/witness points

Define holds before concealment and live tests (631–638). Holds protect crash rated bollard integrity.

Identify hold points such as rebar cage inspection, formwork checks, and anchor template verification before concrete pour; and witness points like power-on, loop proving, and SAT / witness procedure. Place holds prior to concealment or irreversible steps. Each hold/witness line should show the approver, acceptance method, and required evidence (photo set, readings, calibrated gauges).

714.3 Methods & acceptance

Measurement tools, gauges, and numeric bands (626, 232). Methods make HVM bollard checks repeatable.

For every inspection, state the method (e.g., steel tape, digital level, FDT, IR/continuity meters) and the acceptance criteria band (e.g., clear-gap 100 ± 5 mm; plumb ≤2 mm/m). Include instrument ID and calibration expiry in the record. Link dimension checks to spacing rules and datum & alignment checks so field teams know what “good” looks like.

714.4 Sampling & frequency

First-off, percentage checks, and final surveys. Sampling reduces crash rated bollard risk.

Use a “first-off inspection” to prove the method, then define sampling (e.g., 25% of pours, every lane for controls checks) and 100% verification at handover. Increase sampling for high-risk items (foundation depth class; safety interlocks). Add “triggered sampling” rules—if one fail occurs, expand the sample or revert to 100% until two consecutive passes are achieved.

714.5 Roles & sign-offs

Who inspects, who approves, when (131). Roles avoid HVM bollard ambiguity.

Clarify responsibilities with a RACI grid. Typical roles: Contractor (inspects), Owner’s Engineer (approves hold points), Vendor (technical witness), and Authority/Third-party (as required). Add signature blocks and time limits—e.g., “Approve within 24 hours or work stops.” Map escalation to the authority submittals path when approvals are gated.

714.6 NCR/defect handling

Log, root-cause, rework, retest (719). Process restores crash rated bollard compliance.

Tie the ITP to NCR & defects so every fail has a closure path: contain, correct, prevent recurrence. Require photos, measurements, and updated checks after rework. Where a defect impacts rating-critical dependencies (e.g., embedment, grout bed), flag for engineering review before resuming works.

714.7 Records & forms

Standard templates and filenames (716, 911). Forms preserve HVM bollard evidence.

Use standard forms from Witness & Inspection Forms with filenames per File Index & Naming Rules. Specify the evidence type for each line (geo-tagged photos, instrument readings, torque sheets). Follow Evidence Capture Standards so reviewers receive consistent, auditable packs.

714.8 Traceability to drawings

Line items reference 931 IDs. Traceability links crash rated bollard details.

Every ITP line should cite the exact CAD/BIM reference (e.g., “CAD/BIM Standards – Detail FND-12”). Add sheet/page and revision so field teams can locate the source of truth. Where vendor drawings govern, include both the project sheet ID and the vendor detail number, and capture as-tested configuration notes that affect installation.

714.9 Closeout pack linkage

ITP outputs feed SAT/O&M (638, 736). Linkage accelerates HVM bollard handover.

Design your ITP so its outputs drop straight into the SAT/witness pack and the Handover Pack Index. That means consistent file naming, index pages, and cross-references to O&M manuals. A clean evidence chain reduces review time and avoids re-tests that disrupt operations.

Related

External resources

714 ITP — FAQ

What’s the difference between a hold point and a witness point?
A hold point stops work until an authorized person signs off; a witness point is observed but does not necessarily stop work. Both should list the approver/witness, acceptance method, and required evidence.
How detailed should acceptance criteria be in the ITP?
Use numeric bands and clear methods (e.g., “clear-gap 100 ± 5 mm measured by calibrated gauge”). Avoid vague words like “adequate.” Include instrument ID and calibration expiry in the record.
When do we increase sampling frequency?
Escalate sampling after any fail, for high-risk items (e.g., embedment depth, safety interlocks), or when changes occur (crew, method, materials). Continue elevated sampling until consecutive passes demonstrate control.
How should ITP evidence feed the SAT and handover packs?
Organize forms and photos using the site’s naming/index rules. Map each ITP line to SAT scripts and the Handover Pack Index so reviewers can trace checks without re-testing.