Minimum outputs: drawings, coordinates, utilities schedule.
Package survey outputs so designers and reviewers can act immediately. Provide coordinated drawings, benchmarks, utility records, and photo/redline evidence (937 Photo/Redline Logbook). Include GPR/EM reports and trial-pit logs tied to depth classes (243). A responsibility matrix, review flow, and a final pack format feed selection (432–435), foundation pages (331–334), and authority submittals (717, 938). For more context, see this section and the chapter hub. Add SIRA context when approvals are in scope via SIRA Bollards (UAE). 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.
248.1 Required drawings
Topos, utilities, sections, and overlays. Drawings guide HVM bollard arrays (321) and crash rated bollard foundations (331–334).
Deliver a coordinated set: topographic base (spot levels, contours), underground utilities plan with confidence/accuracy class, long/short sections through proposed arrays & spacing, and overlays showing proposed foundations & loads. Each sheet should reference the survey grid, datums & benchmarks, and drawing origin.
Use a simple layer/color convention for mark-ups & overlays (936) so clashes, keep-outs, and survey limits read at a glance. Add key sections at gates, corners, and near-door areas where frontage protection is critical. Tie foundations to design checks (333) and rating-critical dependencies (421).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash standards overview |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
248.2 Coordinates & benchmarks
Provide grid, datums, and checks (336). Controls keep HVM bollard set-out true and crash rated bollard cages aligned (621).
State the coordinate system (local grid or national) and the benchmark scheme used for level transfer. Include control points with northing/easting/elevation, photos, and witness sketches. Add a checking loop: independent re-section or traverse closure to confirm positional accuracy before setting out the first rebar cages & anchors (621).
Publish as-staked coordinates for every bollard centerline and key draw pits, then verify with a datum & alignment check (626) and a gap gauge where spacing is critical.
248.3 Utility records
Attach undertaker plans and notes (241). Records de-risk HVM bollard trenches and crash rated bollard sockets.
Bundle all utility undertaker plans with request dates, validity windows, and coverage notes. Cross-index to a utility search method log (241) and mark-out sketches. Clearly label red-zone utilities (617) and any no-go envelopes (243).
When shallow systems are under review, add a side-by-side showing standard deep socket versus shallow foundations (244) with minimum offsets and drainage implications (334).
248.4 Photos & redlines
Wide→detail with codes and dates (716). Visuals accelerate HVM bollard reviews and crash rated bollard approvals (717, 938).
Capture a wide→detail photo set per location: wide context, mid-range, detail with scale. Embed date, location, chainage and Clash ID where applicable. Use redline callouts to flag conflicts, falls to sump, and duct entries that affect ducting & draw pits (615) and trench details (934).
Reference each photo to drawing sheet/viewport, and maintain an evidence chain linking photos to logs, ITP hold/witness points (714), and final submission pack (938).
248.5 GPR/EM reports
Full methods, grids, and limitations (242). Reports anchor HVM bollard feasibility and shallow crash rated bollard decisions (244).
Include survey scope & methods (antenna frequencies, grid spacing, EM modes), coverage maps, and a clear limitations statement. Tag anomalies with coordinates, depth estimates, and confidence level, cross-referenced to the depth-class decision tree (243).
Where important, add verification steps: follow-up trial pits and service tracing to upgrade confidence before committing to foundation type (332).
248.6 Trial pit logs
Depths, soils, finds, coordinates (613). Logs confirm HVM bollard tolerance bands and crash rated bollard edge distances (331).
Standardize each log: position (northing/easting/level), excavation method, soil strata, finds with measured depth/offset, and annotated photos. Record any water ingress and backfill/compaction notes relevant to backfilling & compaction (628) and groundwater (614).
Close with an accept/reject note against the intended foundation (edge distances, socket depth, impact load path, and drainage needs).
248.7 Responsibility matrix
Who surveys, checks, and signs (135). Matrix prevents HVM bollard drift and cert gaps for a crash rated bollard.
Publish a concise RACI (roles grid) mapping: who surveys, who interprets (engineer), who approves (reviewer/authority), and who records in the file index (911). Identify the accountable owner for each deliverable and the escalation path for blockers.
Note competency requirements (e.g., PAS 128 survey levels for utilities), calibration status of equipment, and any third-party independence needed (e.g., client’s Owner’s Engineer).
248.8 Review & approval flow
Define reviewers and timelines (444). Flow avoids HVM bollard delays and smooths crash rated bollard acceptance.
Show a simple review swimlane: Surveyor → Designer → Security reviewer → Authority. Add SLA targets (e.g., 3/5/10 working days) and evidence & documentation rules (444). Mark witness points where needed—e.g., SAT on powered systems (638).
For UAE projects, include a brief note with a link to SIRA Bollards (UAE) when the submission involves security barriers, and align pack contents with the submission-pack guidance (938).
248.9 Final survey pack
Single indexed PDF + CAD (911). A tidy pack feeds HVM bollard design and crash rated bollard submission (938).
Deliver a single indexed PDF (sheet list, bookmarks) plus native CAD. Include a file index & naming (911), a submission index (938), and a superseded file list to preserve the evidence chain. Attach a concise reader guide (how to navigate, what changed) and a transmittal log with revision IDs.
Provide a ZIP with CAD, shapefiles/GIS (if used), georeferenced photo logs, and the utilities schedule (service, accuracy class, depth, status, action).
Related
External resources
248 Survey Deliverables — FAQ
What’s the minimum set of drawings to release for design?
At minimum: a coordinated topographic base, underground utilities plan with accuracy classes, key long/short sections through proposed arrays, and overlays marking clashes and keep-outs. Each sheet must show the survey grid, datums/benchmarks, and the drawing origin.
How should GPR/EM results be reported for approvals?
Include scope, methods (antenna frequencies, grid spacing), coverage, limitations, and anomaly tables with coordinates, depth estimates, and confidence. Cross-reference any proving trial pits and state how findings inform the depth-class decision and foundation choice.
Which coordinate and level references are acceptable?
Use a consistent local or national grid, state units, and provide at least two permanent benchmarks tied to site features. Publish control point coordinates/elevations, plus as-staked coordinates for bollard centers and draw pits; verify with a closure or re-section check.
What does a “final survey pack” include?
A single indexed PDF with bookmarks and sheet list; native CAD; utilities schedule; photo/redline log; submission and file indices; superseded file list; and a brief reader guide. Provide a ZIP containing CAD, GIS/shapefiles (if used), and all referenced logs.