Editable field survey template and guidance.
Start every project with structured data. This template captures standoff zones (213), approach/run-up (214, 222), access/circulation (215), and utilities clues (241–243), with photo slots and mapping references (936). Built-in picklists improve data quality, while sign-offs and export options align with VDA (221–229) and evidence packs (444). A complete assessment de-risks HVM bollard and crash rated bollard selection later (432–434). 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.
912.1 Field list & IDs
Include location, approach vectors, utilities clues, levels, photos. Map to VDA inputs (221–229) and selection (432).
Capture the basics first: a unique Site ID, coordinates, and site type. Then log approach lines and the likely approach vectors, nearby crossings, kerb lines, and gradients. Mark obvious stand-off distances and potential protection zones from 213. Keep IDs short, consistent, and human-readable—your VDA worksheet later will thank you.
Next, structure photo slots (wide→detail sets) and level checks. Use standard names for every field so the export maps cleanly into the VDA method overview (221), run-up distance (222), and the VDA report template (229). Use picklists where possible (e.g., paving module, kerb type, vehicle classes) to minimise typos and speed up data quality checks.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global crash ratings |
| Operations | Duty cycles, fail-state, safety devices & measures | Safety & interlocks |
912.2 Evidence standards
Geo/time-stamp images; note measurements with tolerances. This underpins HVM bollard and crash rated bollard decisions (232).
Take geo-tagged photos and ensure camera clocks use project time-sync policy. For each dimension (e.g., clear gaps, kerb setbacks), record the value plus a realistic tolerance band. Label every photo with location, direction, and purpose. This evidence flows into spacing rules (232) and later approvals.
Use a consistent filename convention and create a simple evidence index. Aim for repeatability: if someone else repeated your measurement tomorrow, would they get the same result? If you are working in Dubai or wider UAE, note authority expectations early and include a pointer to SIRA Bollards (UAE).
912.3 Plans & overlays
Attach marked plans (936) showing standoff and run-ups (213, 214). Keep scale bars.
Upload a clean base plan and apply redlines that follow our Mark-Up & Overlay Standards (936). Always include a scale bar and north arrow. Overprint the defend line and penetration line, plus candidate bollard arrays. Show effective run-ups from 214 and related VDA run-up corridors.
Use descriptive layer names (e.g., “S912-DefendLine”, “S912-RunUp”) and keep overlays compact so reviewers can toggle items quickly. If you are planning frontage protection, highlight near-door spacing and pinch points for a smooth hand-off to design.
912.4 Utilities & permits
Log records requested and clashes suspected (241–243, 134). Feed 422 depth choices.
Start a utilities request log: who you asked, when, and what map/survey products were received. Tag suspected utilities conflicts from 241 and 242, and flag red-zone utilities that would block standard footings. Feed these into 422 depth & utilities choices early to avoid rework.
Permits live on a timeline—coordinate with 134 Permit & Inspection Timeline. If SIRA or municipal approvals are in scope, link your plan overlays and evidence bundle to the appropriate submittal checklist so the acceptance path is clear.
912.5 People flow sample
Peak counts and queue sketches (231, 215). Data informs frontage arrays (323).
At busy frontages, collect short sample counts (e.g., 10-minute windows) at peak and off-peak. Sketch queue positions and note any queue spillback. Tie this to 231 People Flow & Egress Widths and the local 215 Access & Circulation constraints. Note desire lines and the egress cone.
These observations shape your frontage/door protection arrays (323) and help balance safety with throughput in later design reviews.
912.6 Environment & constraints
Heat, sand, marine, heritage (218, 316, 363). Notes shape materials/coatings (361–362).
Record climate and context: sun-load, airborne sand, coastal exposure, and any heritage curtilage. Cross-reference 218 Environmental Context, 316 Aesthetics that Work, and 363 Environmental Durability. This drives material and finish decisions, from stainless grades to coatings.
Flag constraints that affect installability or maintenance—access windows, noise limits, or night/quiet mode. These notes become inputs to 361 Materials and 362 Coatings, and help set realistic expectations for life-to-first-maintenance.
912.7 Risk & issues
Seed entries for 846 register. Track blockers early.
Open a preliminary risk register at assessment stage and pre-assign risk owners. Record triggers (e.g., utility strikes, heritage constraints) and a simple RAG status. Link this to 846 Risk Register & Governance so issues don’t get lost between survey and design.
Capture assumptions and unknowns: e.g., pending PAS-128 survey results, or unverified slab thickness. This seeds your assumptions register and informs the contingency in later phases.
912.8 Sign-offs & distribution
Stakeholder approvals (131). File to 911 paths.
Define who signs off what: security lead, architect, client rep, and contractor. Map roles back to 131 Stakeholders & Responsibilities. Store outputs under the agreed folder rules in 911 File Index & Naming Rules so the team can retrieve the latest version quickly.
Provide a snapshot PDF for circulation and keep the live file editable. Maintain a short distribution list and version note so reviewers know what changed.
912.9 Handover to VDA
Package for 229 report assembly. Smooth handoff speeds reviews (717).
Export a clean data bundle that slots directly into the VDA Report Template (229): site summary, overlays, photo log, utilities notes, and people-flow samples. This accelerates the compliance/specification path and smooths authority submissions (see 717).
Finally, signpost what’s next: VDA calculations, spacing checks, and a shortlist for design selection (432) and HVM vs low-speed choices (434).
Related
External resources
- NPSA: Hostile Vehicle Mitigation (HVM)
- ASIS: Security Risk Assessment Standard
- FEMA 426 / DHS Reference Manual
912 Site Assessment Template — FAQ
What’s the difference between this template and the 211 Site Assessment Checklist?
The template gives you editable fields, picklists, and export-ready IDs for data capture. The 211 checklist is a quick compliance check to ensure you didn’t miss a topic. Use them together: fill this template on site, then run 211 before handing over to VDA.
How many photos should I capture per location?
Use the “wide→detail” rule: at least one wide context shot, one medium framing the feature, and one close-up with a scale reference or tape. Geo-tag and timestamp each image, and label direction (e.g., “Facing NE”).
Do I need a utilities survey before starting VDA?
No, but log records requested and suspected clashes now. Early red flags guide whether shallow or alternate foundations will be needed, which affects spacing and selection. Confirm with PAS-128 surveys before finalizing foundations.
When should I involve approvals (e.g., SIRA) and stakeholders for sign-off?
Flag approvals at assessment stage. Share the snapshot PDF and overlays for early feedback, then obtain sign-offs before VDA submission. For Dubai/UAE projects, align with SIRA requirements and keep evidence standards consistent across submissions.