Page codes, revision policy, changelog etiquette, and citation format.
Our code system (e.g., 321.4) makes it easy to cite guidance in drawings, specs, and emails. Slugs and titles are tuned to strengthen relevance for “HVM bollard” and “crash rated bollard.” See the live change log (118) and file rules (911) for traceability. Old URLs redirect to keep internal links from 371–374, 411–416, and 611–639 intact. This page sits within this section and the chapter hub. If a project falls under UAE approvals, also see SIRA Bollards (UAE) for authority context.
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.
115.1 Chapter/section/page code system
Codes (XXX / XXX.X) make guidance citable. Use them in drawings, RFIs, and ITP lines. HVM bollard spacing checks might cite 232.7; a crash rated bollard dependency cites 421.3. Keep codes visible in change notes (118).
Each page shows a visible page code in headings to tighten cross-references between design, installation, and commissioning. Use codes directly in submittals, RFIs, and the Inspection & Test Plan (ITP) so reviewers can jump to the exact clause. For arrays and spacing, codes in the 320s (e.g., 320 hub) keep design discussions precise.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) and rated claim | Crash standards overview (411) |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
115.2 H2/H3 numbering rules (XXX / XXX.X)
H2 = page code; H3 = sub-topic (e.g., 321.5). Don’t mix with SEO slugs/titles; those follow 911/115 rules. For HVM bollard design, numbering speeds peer review. For a crash rated bollard, it ties acceptance to certificate fields (431).
Keep H2s as XXX.n and any H3s as XXX.n (a/b/c). Numbering is content-visible only: never put codes in the WordPress Title field, the slug, or Rank Math SEO title. See File Index & Naming Rules (911) for filenames. For ratings content, numbered H3s can map directly to certificate checks in 431.
115.3 Slugs and SEO title policies
Human-readable, keyword-relevant, no code in slug. Titles should reflect task (e.g., “Spacing rules for HVM & Crash-Rated Bollards”). Use “HVM bollard” and “crash rated bollard” where meaningful. Map redirects when titles evolve (118).
Keep slugs short and descriptive; avoid numbers and punctuation. If you rename a page, update the slug and set a 301 to preserve equity. Re-check incoming links from related hubs like 400 Ratings & Compliance and design pages under 300 Design. Use “Guide” in SEO titles for informational intent (see our Article checklist v5.1) and verify SERP Snippet Health before publishing.
115.4 How we log changes
Each entry notes what changed, where (codes), and why. If HVM bollard spacing tolerances move (232), the log flags dependent pages. If a crash rated bollard equivalence note updates (414), specs/435 are linked.
Log changes centrally in 118 Change Log with: (a) affected codes, (b) summary, (c) rationale, (d) links to pages and downloads updated, and (e) impact on drawings/specs. Tag dependencies such as 232, 414, and 435 to help reviewers understand downstream effects.
115.5 What “Approved” vs “Draft” means
“Approved” is issue-for-use; “Draft” is under review. Don’t cite Draft in submittals (938). For HVM bollard sites, SAT scripts (638) must be “Approved.” For a crash rated bollard, only “Approved” certificates (431) are valid.
Use a clear status line on PDFs and forms: Draft, For Review, or Approved (Issue-for-Use). In the commissioning stream, ensure SAT / Witness Procedure (638) and 431 certificates carry the correct status before submission in 938 Submission-Pack Guidance.
115.6 Backwards compatibility & redirects
Old URLs 301 to new slugs; codes persist. If HVM bollard arrays guidance relocates, 321.* remains addressable. Crash rated bollard pages keep rating strings intact (413).
When consolidating content, keep the same numbered clauses where possible and create 301s from any retired slugs. Re-crawl key hubs like 320 Arrays & Spacing and 413 How to read ratings to fix broken anchors. Note the redirect in the Change Log (118).
115.7 Referencing specific versions
Quote code + date (e.g., 232 v2025-09-12). Attach PDFs to packs (938). For HVM bollard acceptance, snapshot the ITP line. For a crash rated bollard, include the certificate version (431.7).
Use a compact format like 232 vYYYY-MM-DD in emails and drawings. Store the “snapshot” PDF in the relevant folder under 910–919 Downloads and reference it from 710 FDS/SAP/ITP/SAT. For acceptance, capture the exact ITP line and include the current rating certificate version from 431.
115.8 How to cite pages in reports
Use code, title, and precise clause (e.g., “232.7 Tolerance drift”). This helps reviewers track HVM bollard spacing rationale and crash rated bollard limitations.
Preferred format: “232.7 — Spacing tolerance drift (ref: 232)” with a live link to the page section. In multi-disciplinary packs, add the responsible RACI role next to each citation (e.g., Designer/Installer/Reviewer) so actions are unambiguous.
115.9 Roadmap & release notes format
Group by theme: Selection (432–435), Arrays/Spacing (321–326, 232), Foundations (331–334), Controls (341–357), Evidence (431, 444, 938). Note impacts to HVM bollard commissioning (631–639) and crash rated bollard wording (414–435).
Release notes should summarize changes, list affected codes, and highlight impacts on drawings/specs, calculators (920–929), and commissioning (630–639). Link to deep pages like 432 Design selection, 321 Array Patterns, and 639 Snagging & Handover for immediate next steps.
Related
External resources
- NPSA — Hostile Vehicle Mitigation guidance
- BSI — Impact test specifications (VSB systems)
- ASIS — Security Risk Assessment Standard (governance context)
115 Versioning & Numbering — FAQ
How is a page code different from the slug or SEO title?
The page code (e.g., 232.7) is a short in-content reference for citing exact clauses. The slug is the human-readable URL path without codes. The SEO title is what appears in search; it should be descriptive and code-free.
When should we create a redirect (301)?
Create a 301 whenever a slug changes or content is merged. Keep codes stable in the body so references in drawings, RFIs, and ITPs continue to make sense, and list the redirect in the Change Log (118).
Can we cite “Draft” pages in submittals?
No. Only “Approved (Issue-for-Use)” material should be cited in authority submittals or witness procedures. Drafts are for internal review and iteration.
What is the correct format to quote a specific version?
Use “
XXX.n vYYYY-MM-DD” (e.g., 232.7 v2025-09-12) and attach the snapshot PDF in the submission pack. Include current certificate/appendix versions where applicable (e.g., page 431).