Survey control, offsets, and tolerance targets.

Accurate set-out preserves clear gaps and certification dependencies. Establish survey datums, gridlines, and level benchmarks tied to height rules (312) and spacing calculations (232, 322). Use templates/jigs, enforce tolerance bands, and run verification cycles feeding into 626. Record set-out data for as-builts (731) and acceptance (638), avoiding common errors that later harm crash rated bollard compliance (421). This page sits within this section and the the chapter hub. If authority approvals are in scope, see SIRA Bollards (UAE). For a process overview, the installation primers What to Expect and Installation Guide may help.

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.

612.1 Survey control & datums

Establish site grid and reference points. Control anchors HVM bollard alignment.

Start by building a robust control network tied to a reliable base map/topo. Fix permanent control pins away from excavation zones and reference them with a datum & benchmarks schedule. Every lane or frontage should have at least two intervisible control points to reduce angular error and make resection quick after site obstructions move.

Lock the HVM array centreline and key edges early: define the array centreline and “defend line” references (see 322 Clear-Gap Calculations). Tie these to building grids so later trades can verify independently.

AspectWhat mattersWhere to verify
Horizontal controlStable, intervisible control pins; resection notes248 Survey Deliverables
Vertical controlPrimary & check benchmarks; transfer method312 Height setting
Array definitionCentrelines, rotation marks, defend line336 Bollard Setting-Out

612.2 Gridlines & offsets

Mark centerlines and offsets to façades (234). Offsets protect crash rated bollard clear gaps (232).

Snap the array centreline, then set offsets to the façade, kerb, or back-of-kerb using a documented rule (see 234 Frontage protection). Preserve the clear-gap while honouring egress widths and near-door spacing. Where frontages are not straight, break the array into short tangents and note each tangent’s start/end chainage.

Add a rotation mark at each position when system performance depends on orientation (e.g., asymmetric sleeves or keepered openings). Cross-reference with 322 Clear-Gap Calculations for projected gap checks on curves.

612.3 Level/height benchmarks

Set FFL benchmarks to manage head heights (312). Benchmarks keep HVM bollard visuals consistent.

Transfer a primary benchmark to the workface before excavation, then create temporary checks near each lane. Control the final bollard “effective height” relative to finished surfaces; record any paving build-up assumptions. For slopes, verify the visible head band forms a consistent rhythm across the array and won’t breach sightlines or door thresholds (see 312 Height setting).

Where sockets or sleeves are tall, note minimum/maximum embedment relative to benchmark to avoid tolerance stack-up that could harm certification dependencies (see 421 Rating-critical dependencies).

612.4 Templates & jigs

Use drill/jig plates for repeatable spacing. Jigs reduce crash rated bollard tolerance drift (315).

Adopt a leveled jig or drill plate that matches the certified pattern. Add a slot for the lane centreline and a mark for each rotation angle—this limits human error and accelerates checks. For anchor patterns, include a Go/No-Go gauge to test hole spacing before pour or grout.

Standardize tool lists and inspection points with 631 Pre-Commission Checklist and 714 ITP so inspectors can reproduce your measurements.

612.5 Tolerance bands

Publish positional/level tolerances linked to 314. Bands preserve HVM bollard performance.

Define horizontal and vertical tolerances as an acceptance band around the theoretical point/level. Use a tighter “work” band for production and a slightly wider “sign-off” band for acceptance (aligned to 314 Deflection vs permanent set). Document how compound errors (template, excavation, rebar, pour) add to tolerance stack-up.

When certification relies on precise keepered dimensions or sleeve geometry, set a stricter local band and a specific gauge for those features; record each check for the evidence pack (see 431 Documentation & certificates).

612.6 Verification cycle

First-off, mid-run, and final checks (626). Cycles lock crash rated bollard quality.

Run a three-stage cycle: (a) first-off inspection at the first array position, (b) mid-run sample checks after every few placements, and (c) final survey after curing/grout. Each stage should confirm clear-gap compliance (232/322), rotation/orientation, and head height. Close any drift before it propagates (see 626 Datum & Alignment Checks).

Use a short runbook with photos of the measurement method, including the step gauge position and centreline trace. Where approvals apply, include a witness point in the ITP and invite the reviewer early (see 638 SAT / Witness Procedure).

612.7 Recording set-out data

Log coordinates, elevations, and photos (731). Records support HVM bollard acceptance (638).

For each bollard, capture northing/easting/elevation, rotation mark, and any local notes (e.g., curb lip). Add a wide→detail photo set for traceability and geo-tag where possible. Save to the project evidence pack and align file naming with the site’s archive rules (see 939 Final Archive & Retrieval).

Publish “as-set” coordinates to help the 731 As-Built Drawings & Models team; include a CSV extract and a simple key plan to speed drafting.

612.8 Common errors to avoid

Beware slope effects, curb lips, and datum mix-ups (232). Avoidances protect crash rated bollard compliance.

Slope blindness: neglecting crossfall/camber can cause apparent head height variation and sub-threshold clear gaps on the uphill side. Check crossfall and use the projected gap method from 322.

Datum confusion: mixing temporary and primary benches without a transfer log. Always record benchmark transfers and use two-way level checks.

Kerb/edge assumptions: “back-of-kerb” lines shift during reinstatement—pin a fixed offset and re-verify after base course or screed.

612.9 Acceptance criteria

Define pass/fail gauges and survey ranges. Criteria make HVM bollard sign-off objective (714).

State the pass bands plainly: horizontal (e.g., ±5 mm to theoretical), vertical head height (e.g., ±3 mm to design), rotation (e.g., ±1°). Provide named gauges (e.g., clear-gap step gauge sizes) and the survey method (total station, control points used, closure error). Map each criterion to an ITP witness point and list the required evidence items for SAT close-out (638).

Related

External resources

612 Setting-Out & Benchmarks — FAQ

What is the minimum survey kit I need for accurate bollard set-out?
A total station or GNSS rover tied to a stable control network, a calibrated level for benchmark transfer, a leveled jig or drill plate, and simple Go/No-Go gauges for clear-gap and bolt patterns. Add a photo log (wide→detail) and a CSV template for coordinates to streamline as-builts.
How tight should my horizontal and vertical tolerances be?
Set a production “work” band (e.g., ±3–5 mm horizontally, ±3 mm vertically) and a slightly wider acceptance band agreed in the ITP. Tighten locally where certification-critical (e.g., keepered openings) and document the gauge/method used.
Do slopes change the clear-gap requirement?
The requirement is unchanged, but slopes affect apparent spacing and head heights. Use projected-gap checks on curves/crossfalls and confirm egress/sightlines. Break arrays into short tangents to control drift.
What records are essential for SAT/witness sign-off?
Control points, benchmark transfer notes, as-set coordinates (N/E/Z), rotation marks, clear-gap gauge results, and a geo-tagged photo set. File them in the evidence pack and reference the ITP witness points for traceability.