This checklist structures your first visit so later choices—HVM bollard rating, crash rated foundations, and clear gaps—are evidence-led. It ties your findings directly to selection and layout decisions, and to documentation standards so what you record on day one flows cleanly into design and approvals. For context, see this section and the chapter hub. If UAE approvals apply, also consult SIRA Bollards (UAE). When helpful, refer to installation intros: What to Expect and Installation Guide.
211.1 Pre-visit prep
Print site forms (912–913), past utilities (241), and aerials with run-up overlays (222, 214). Pack gap gauges and level staff for HVM bollard spacing checks (232) and camera for evidence (716). Bring any crash rated bollard certificate excerpts to confirm on-ground constraints (431, 421).
Before you go, assemble a lightweight pack: a copy of the Site Assessment Template, the VDA Worksheet, and utility records from Utility Search Methods. Pre-mark suspected run-up distance and likely approach vectors on an aerial print. Pack a photo-evidence kit and a gap gauge to quickly validate likely clear-gap compliance on site.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read ratings |
| Operations | Duty cycles, fail-state, safety measures | Installation Guide |
211.2 On-site walkdown
Clock approach lines, corner vectors, and pinch points (214, 324). Mark candidate array lines (321) and near-door risks (323). Note conflicts affecting an HVM bollard layout and any depth issues that could block a crash rated bollard foundation (332–334).
Walk the site perimeter first, then move inward to entries and service routes. Sketch plausible array patterns and record any obstructions, slopes, or kerb returns that would force tighter clear-gap tolerances. If local approvals may apply, capture anything SIRA reviewers typically question (e.g., emergency access paths) and note it for later cross-check with SIRA Bollards (UAE).
211.3 Access & egress points
Map doors, ramps, crossings, and fire routes (231, 233). Keep HVM bollard lines outside egress sweeps; anticipate service turns (325). If selecting a crash rated bollard near glazing, record offsets for height checks (312, 234).
Confirm minimum widths from People Flow & Egress Widths and verify that turning radii for service vehicles (waste, deliveries) align with Turning & Service Access. Where doors are protected by a frontage/door protection array, record threshold details and potential trip hazards so later detailing can mitigate them.
211.4 Hazards & conflicts
Log traffic, pedestrians, kerb radii, and sightlines (237). Identify slopes/steps that complicate HVM bollard clear gaps (232). Tag constraints that may force a shallow-base crash rated bollard (244, 243).
Note line-of-sight to signage and signals (Sightlines & Signage) and any crowd-flow pinch points. If the gradient or paving steps would produce an uneven effective height, mark where foundation depth or bollard height must be adjusted. Capture any conflicts that might mandate shallow foundations.
211.5 Utilities/ground clues
Spot covers, trenches, cabinets, and patching. Photograph and sketch likely corridors for later proving (242). Utilities often decide HVM bollard feasibility; depth clashes drive crash rated bollard base choice (422).
Tag every chamber lid and visible duct path on plan, then follow up with Underground Detection. Cross-reference typical base depths in Foundation types so you can shortlist models that actually fit. Where conflicts are probable, pre-flag shallow foundation options and note any drainage needs.
211.6 Measurements & benchmarks
Shoot datums/FFLs, kerb faces, and facade offsets (612, 312). These control HVM bollard heights and clear gaps (232). Store coordinates so a crash rated bollard socket can be positioned within tolerances (626, 421).
Establish a datum & benchmarks set early. Record facade set-backs, kerb face lines, and threshold levels to verify effective height per Height setting. For accurate set-out later, capture coordinates and tolerances you’ll re-use during Datum & Alignment Checks.
211.7 Photos & markups
Capture annotated wide→detail sets with time/geo stamps (716). Include array arrows and vector angles (225). Use consistent codes so both HVM bollard and crash rated bollard evidence drops into packs (938).
Follow the Evidence Capture Standards: start with a wide shot to anchor context, then move to mid and close-ups, ending with an annotated markup. Label each photo using the File Index & Naming Rules, and keep your redlines consistent with Mark-Up & Overlay Standards.
211.8 Stakeholder sign-offs
Record who attended and immediate constraints/agreements (131). Early buy-in reduces redesign of HVM bollard arrays and avoids later disputes over crash rated bollard claims (444).
List stakeholders present (client, facilities, security, architect, contractor) and note any agreements, hold points, or requested changes. Use the roles primer in Stakeholders & Responsibilities. If reviewers will require proof, set the path now toward a clean Submission-Pack and the evidence expectations in Evidence & Documentation.
211.9 Filing and follow-up
Upload to the project index (911), update the risk/issue log, and trigger VDA (221–229). Schedule utilities proving (241–243). This keeps HVM bollard selection fast and ensures crash rated bollard options remain buildable (332).
Immediately file photos, notes, and sketches to the job’s index using the File Index & Naming Rules. Open any RFIs and book proving works from Utility Search Methods and Underground Detection. Kick off the VDA method so selection and spacing move forward without waiting on missing data.
Related
External resources
- NPSA: Hostile Vehicle Mitigation
- FEMA 426: Building Security Guidance
- ASIS: Security Risk Assessment Standard
