Date-stamped updates, what changed, and why it matters.
Track what’s new so your drawings, BOQs, and specs stay current. Each entry lists added or revised pages—e.g., updates to HVM bollard spacing (232), array patterns (321–326), crash rated bollard foundations (331–334), and submission guidance (938). We also flag known gaps, roadmap items, and reference IDs that tie back to file naming rules (911) and redirects (115). This page sits within this section and the wider chapter hub for orientation.
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.
118.1 What changed in this release
Summarize updates by code and impact. If HVM bollard spacing moved (232.7), list affected drawings/specs. If a crash rated bollard equivalence rule changed (414), flag 433/435 edits.
Use a short, decision-focused summary so teams can update quickly. For spacing rules, point designers to 232 Spacing rules and array specifics in 321 Array Patterns. If 414 Standards equivalency changes, confirm knock-ons in 433 Specification template and 435 Anti-Downgrade / Equivalence.
Keep terminology tight on first mention. For example, a change to clear-gap rules affects both obstruction control and emergency access (see 233 Emergency/service access). Where ratings are referenced, remind readers that HVM systems are tested as a whole (bollard + footing), not components.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Ratings & Compliance (400) |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation hub (600) |
| Docs | Spec wording, certificates, submittals | 430 Compliance & Spec |
118.2 Pages added
List new guidance (e.g., 327 event reconfiguration). Note why it matters to HVM bollard operations and to crash rated bollard acceptance.
When a new page launches—such as 327 Temporary/event reconfiguration—include a one-line impact note (e.g., traffic management during temporary/event mode) and where to update drawings, ITP, and SAT forms.
- New content must cross-link to parent hubs and close siblings (e.g., 321–326) to maintain a consistent reader path.
- Set self-canonical and verify social previews per checklist (v5.1).
118.3 Pages updated
Detail clauses touched (e.g., 331.4 group effects). Provide quick actions for HVM bollard designers and crash rated bollard reviewers.
For foundation edits (331–334), call out whether the change affects depth class, drainage sump, or grade beam requirements; then point to the impacted drawings and commissioning checks in 630 Commissioning & safety tests.
For ratings language (411–416), flag the exact paragraph and show how it affects 433 spec boilerplate. Where equivalency is claimed, ensure the evidence pack includes the right rating string and supporting certificates (see 431).
118.4 Pages deprecated
State replacements and redirects. Keep HVM bollard installers on current ITP lines (714) and crash rated bollard certificates aligned (431).
When content is superseded, mark it here, update internal links, and implement a 301 redirect per 911 File Index & Naming Rules and 115 Versioning & Numbering. Note the successor page and any scope changes.
- Check 714 ITP references and update witness points in 638 SAT / Witness Procedure.
- Ensure Page-ID references in PDFs are revised or a “snapshot date” disclaimer is present.
118.5 Known issues or gaps
Track pending clarifications (e.g., mixed-type arrays 326). Explain interim handling for HVM bollard design and crash rated bollard claims.
Use a simple triage: (a) blocking (stops approval), (b) material (affects selection or acceptance), (c) editorial (wording/clarity). Example: mixed-type arrays (326)—until test evidence is comparable, enforce the stricter acceptance band in 716 Evidence Capture Standards.
118.6 Upcoming changes
Roadmap entries with ETA and dependencies. Useful for HVM bollard programme planning (855) and crash rated bollard submittal timing (717, 938).
For each roadmap item, specify dependency (e.g., results from 636 performance tests) and target pages to be edited. Link teams to 855 Programme & Phasing and 938 Submission-Pack Guidance for timing/lead-time implications.
118.7 How to report errors
Quote code, evidence (716), and suggested fix. Prioritize items blocking HVM bollard acceptance or crash rated bollard compliance.
- State the Page-ID (e.g., 232.7) and paste the problematic sentence/figure.
- Attach evidence (photos, mark-ups) that meet 716 standards, and cite impacted 431 certificates or 936 overlays.
- Propose a fix and where it propagates (specs 433, drawings 915, calculators 920s).
118.8 How to subscribe to updates
Opt in via project comms. Critical HVM bollard/SAT changes (631–639) and crash rated bollard standard updates (411–416) trigger alerts.
We recommend teams enable update alerts for commissioning (631–639) and ratings (411–416). For operations teams, include changes to KPI thresholds and remote fault logging so maintenance plans (734) stay aligned.
118.9 Version reference IDs
Each log entry has an ID you can cite in packs (938). Use it to prove which HVM bollard rule set or crash rated bollard wording you followed.
Every entry includes a unique version reference (e.g., 118-2025-10-22-A). Use this in the cover/index of your Submission Pack (938), and in the footer of any snapshot PDF. If an approval cites an older version, note the delta in your 718 Variations & Change Log.
| Field | Example | Use in documents |
|---|---|---|
| Ref code | 118 | Change Log page anchor |
| Date | 2025-10-22 | Pack cover (938), drawing title block (915) |
| Sequence | A/B/C | Multiple same-day edits |
Related
External resources
- ASIS — Security Risk Assessment (change governance context)
- BSI — Impact test specifications (terminology)
- ISO 22343 — Protective security (standards equivalency context)
118 Change Log — FAQ
How is a “release” different from a minor edit?
A release groups multiple edits into a dated entry with an ID (e.g., 118-YYYY-MM-DD-A). Minor line edits that don’t change meaning are batched into the next release. If wording affects specs, spacing, foundations, or certifications, it is always included in a formal release.
What should I update after spacing or array changes?
Update drawings and schedules that reference 232 and 321–326, revise the spec clauses in 433, and note the change in your project’s 718 Variations & Change Log. If approvals are pending, include the release ID in the submission cover (938).
When do I need a 301 redirect?
When a page is deprecated or merged. Log the successor page here, implement a 301 per 911, and confirm internal links are repointed. Keep a snapshot PDF if the older wording was cited during approvals.
How do I cite the version I followed in my submission?
Place the release ID on the submission index and covers (938) and in the footer of drawings (915). If reviewers query differences, show the delta between your cited release and the current one.