One page per clause
The requirement in our words, the evidence an assessor asks for, the common gaps and what to do before publication.
Open the registerA twelve-week path to the evidence pack
The plan below is the order the standard expects. It is a default, not a promise: a single site can compress it and an estate with many barriers will extend it. The dates are relative to your start, and the planning date of 15 February 2027 is an estimate for the amendment, not a deadline for you.
The page adds the calendar dates for week 1 and week 12. With JavaScript off, the relative labels still work.
| When | Clause | What is produced | Owner |
|---|---|---|---|
| Week 0 | Clause 1 and 3 | Inventory every barrier, its function, its site and the claim made for it | Security lead |
| Week 1 | Clause 1 and the ISO record | Edition register: the edition cited in each specification and contract | Compliance lead |
| Week 2 | Clause 6.8 | Collect the full test reports, drawings and raw data for every barrier | Procurement |
| Week 3 | Clause 7.2 | Decode every rating into the eight parts and check the edition | Security engineer |
| Week 4 | Clause 6.5 and Table 2 | Compare the tested vehicle class and mass with the site threat | Risk lead |
| Week 5 | Clause 5.2 and 6.4 | Compare the tested foundation and fixing with the as-built installation | Site engineer |
| Week 6 | Clause 6.3 and 4 | Check the site angle, stand-off, penetration and debris against the rating | Security engineer |
| Week 7 | Annex C | Walk the post-impact access and add it to the emergency plan | Site operator |
| Week 8 | Clause 8 | Write the one-page assurance statement with the edition, rating and report date | Compliance lead |
| Week 9 | Annex D | Set the inspection and maintenance regime, with an owner and interval | Facilities |
| Week 10 | Amendment record | Send the supplier letter and set the amendment readiness date | Procurement |
| Week 11 | All | Tabletop review with legal, insurance and operations, and sign-off of the pack | CISO |
Print this page for the project wall. The paid kit carries the same plan with an editable date, an owner column and a status column per line.
The inventory comes first because a claim can only be checked against a named barrier and a named site. The report comes before the rating decode because the code is a summary of the report. The foundation comparison comes before the assurance statement because a rating that does not match the installation is not an assurance. The amendment readiness work comes last because it changes the wording of the claim, not the evidence behind it.
THE RECORD THIS IS BUILT FROM
Read from the public record, not invented
Every clause answer on this site points to the official record or the public preview behind it, so you can check any line yourself. The register holds 25 records, 111 evidence lines and 100 common failure lines. The dates come from the ISO stage record. The amendment text is not public, and this site does not describe what it changes.
16 CLAUSES
9 ANNEX RECORDS
Normative and informative, labelled
Annex A is normative and carries the measurement controls. Annexes B to D are informative and say so.
Open the annexesONE STAGE RECORD
No invented date
Stage 50.00 is recorded on 8 October 2026. The planning date is an estimate and is labelled wherever it appears.
Read the recordThe base standard is published. The amendment text is not public at FDIS. Each record cites the public source it comes from. Where the public record is silent, the page says so.