Wording to prevent substitution and protect outcomes.
Protect your design from silent substitutions. This page provides clause language that prevents downgrades, specifies the evidence required for any change, and locks family/variant, foundation, and array parameters to rating-critical dependencies (421, 415, 332). It defines review/approval workflows (717, 938) and NCR responses (719) with sample text you can paste into specs (433) for HVM bollard and crash rated bollard projects. 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.
435.1 Why downgrade happens
Cost or lead-time pressure tempts swaps. Guard HVM bollard performance with clear rules.
Unplanned “value engineering” often targets the barrier itself, its footing, or the bollard array, eroding the certified configuration. Typical drivers are urgent availability, small price deltas, or aesthetic sleeve changes that seem harmless but alter effective height or stiffness. Without explicit anti-downgrade wording, teams may accept “like-for-like” claims that skip a proper evidence review.
Downgrade risk is highest when drawings omit the tested orientation, foundation class, and clear-gap rules, or when the spec lacks a defined standards equivalency pathway. Add explicit hold points so any change pauses works until evidence is approved.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read ratings |
| Dependencies | Depth, spacing, soil, sleeves | Rating-critical dependencies |
| Operations | Duty, fail-state, safety devices & measures | Installation Guide |
435.2 Wording to prevent it
State “no substitution without evidence and approval per 414.” Firm wording preserves the specified crash rated bollard.
Use unambiguous language: substitutions are prohibited unless an equivalence submission meets the evidence threshold defined in page 414 Standards equivalency and is approved in writing by the Owner’s Engineer/Authority. Reference the tested article, foundation class, clear-gap rule, and acceptable variants list (415). Add a hold point for procurement and for on-site receipt inspection.
435.3 Evidence required for changes
Demand certificates, photos, orientation, foundation notes, and matrices (431, 415). Evidence keeps HVM bollard safety intact.
Minimum pack: an authentic crash certificate/report with certificate scope, test IDs, tested orientation, and penetration results; unedited test footage; photos of the test article; a variant matrix cross-referencing heights/diameters/sleeves; and written notes on foundation depth/reinforcement and array spacing. Include a site comparability note proving soil/foundation/array parity with the tested setup.
Where UAE approvals apply, add a SIRA note: equivalence evidence must be suitable for authority review; see SIRA Bollards (UAE). Use page 431 Documentation & certificates and 415 Product families/variants as reviewers’ checklists.
435.4 Family/variant control
List allowed families/models/variants only (415). Control blocks off-catalog crash rated bollard swaps.
In the spec, name the product family and enumerate allowed variants (diameter, height, sleeve types, finish, lighting) that preserve certification. Add the rule that any unlisted variant is treated as a new product requiring full equivalence proof. Tie variant acceptance to the supplier’s family window document and to an evidence pack signed by an authorized test house or the certificate issuer.
435.5 Foundation/array lock-in
Tie bases and spacing to the rating (332, 322). Lock-in stops silent shifts that weaken an HVM bollard.
Lock the foundation class (e.g., Deep-Socket vs Shallow-Rail), reinforcement, concrete grade/cure, and embedment depth; prohibit reductions without a re-assessment. State the allowable clear-gap and array pattern per 322 Clear-Gap Calculations, and point to 332 Foundation types.
435.6 Review/approval workflow
Define who reviews and the forms used (717, 938). Workflow prevents ad-hoc crash rated bollard changes.
Use a simple RACI: Supplier (prepare), Contractor (submit), Designer/Owner’s Engineer (review), Authority (approve). Changes follow the Authority Submittals process (717) with a cover sheet and index per 938 Submission-Pack Guidance. Add a “no-work” hold point until written approval is issued.
435.7 Nonconformance response
Quarantine, assess, remedy, and document (719). Structured response protects HVM bollard compliance.
If an unapproved item appears on site, raise an NCR, quarantine the batch, and halt install in affected areas. Root-cause the gap (procurement, drawings, site swap), define remedy (replacement, re-work, or evidence submission), and record decisions and photos. Reference 719 Nonconformance & Defects.
435.8 Sample clause text
Include a short paste-ready paragraph referencing 414, 421, 431. Text standardizes crash rated bollard protection.
Clause: “Anti-Downgrade & Equivalence. The specified crash-tested bollard system (product family and listed variants) shall not be substituted or altered — including foundation class, embedment, rebar, array spacing/clear-gap, sleeves/finishes, or controls — without prior written approval. Any proposed change shall include an Equivalence Evidence Pack meeting page 414 Standards equivalency, prove conformance to page 421 Rating-critical dependencies, and attach valid certification per page 431 Documentation & certificates. Works shall pause at the defined hold point until approval is issued.”
435.9 Enforcement tips
Use hold points, labels, and site audits (714, 716). Enforcement keeps HVM bollard specs intact.
Insert Inspection & Test Plan hold points (714 ITP) for procurement, delivery verification, pre-pour checks, and pre-commission. Require itemized labeling (family, variant, certificate ID) and use a simple Go/No-Go gauge for clear-gap. Photo logs should follow 716 Evidence Capture Standards. Schedule short audits during setting-out and before pours.
Related
External resources
- BSI — Vehicle Security Barrier (VSB) impact test specifications
- ASTM F2656 — Crash testing for perimeter barriers
- NPSA — Hostile Vehicle Mitigation guidance
435 Anti-Downgrade / Equivalence Clauses — FAQ
What counts as a downgrade if the model name stays the same?
Any change that alters the tested configuration is a downgrade: foundation class/depth/rebar, array spacing/clear-gap, effective height/diameter, sleeve construction, or controls/safety that affect operation. Treat unlisted variants as new products requiring equivalence evidence and approval.
Is “like-for-like” acceptable without documents?
No. “Like-for-like” is a claim, not proof. Require a documented Equivalence Evidence Pack showing certificate scope, variant matrix, orientation, foundation notes, and test media; then follow the submittals workflow for approval.
Which pages should we cite inside the clause?
Reference page 414 for standards equivalency, page 421 for rating-critical dependencies, and page 431 for documentation & certificates. Add page 717/938 where authority submittals are in scope.
How do we handle unapproved items delivered to site?
Raise an NCR, quarantine the batch, stop affected works, and escalate per the ITP hold point. Conduct root-cause analysis and either replace, re-work, or submit full equivalence evidence for approval before proceeding.
Do SIRA projects require anything extra?
Yes. Add a brief SIRA note and ensure the equivalence pack is suitable for authority review. Coordinate with the SIRA approvals pathway and include their required forms during submittals.