ISO 55001 audit readiness: every clause of ISO 55001:2024 mapped to your own evidence, and every gap found before the auditor finds it
Auditor questions answered with the evidence attached.
See one case, screen by screen ↓Every certified utility faces a surveillance audit each year and a recertification every three years, and before 31 July 2027 each one must also move to ISO 55001:2024. The auditor walks the standard clause by clause and asks for the document that proves each requirement: the Strategic Asset Management Plan (SAMP), the asset management plans, the objectives, the risk register, the management review minutes. The asset management office finds that evidence by hand across document folders, EAM exports and inboxes, in a control matrix that is out of date the day it is finished.
The evidence usually exists; what goes wrong is a document that is still a draft, a review that was never minuted, a report a quarter old, or a plan that covers electricity but not water. The 2024 edition adds new requirements — the decision-making framework in 4.5, the SAMP's required content in 6.2.1, planning of changes in 6.3, data and information in 7.6, knowledge in 7.7 and predictive action in 10.3 — so last cycle's matrix no longer covers the standard. A major nonconformity holds up the certification decision until it is closed and verified.
Estimated split of about 6 weeks of part-time effort by 3–4 people in the asset management office, in working days, by hand and with the solution. Our estimate for a utility running both businesses; to be measured in the pilot.
Six agents map every document to the clauses, name what is missing and draft the requests; the asset management office sends them and the Director signs.
Lumina Utilities runs electricity distribution up to 132 kV and water supply from source to meter. Its recertification and transition audit to ISO 55001:2024 with Ardenvale Assurance is 17–19 Nov 2026. Today is Tue 13 Oct — 35 days out. Here is what happens next, screen by screen, in the working solution.
Amara owns the audit plan and the evidence. The clause map shows all 27 subclauses of ISO 55001:2024 and 142 requirement lines: 84 % ready today, 119 lines evidenced, 16 needing work and 7 documents missing. The clauses new or revised in 2024 are marked, and every gap shows in red on its tile.
6.2 Asset management objectives and planning · REVISED · 14/20 · 2 missing · 70 %
She asks in plain words. The clause mapper reads 1,246 documents and matches 27 passages from 12 of them to the 20 lines of 6.2. The evidence checker checks versions, approvals and dates; the gap finder names what the auditor will ask for; the request drafter finds the owners. Four agents, four steps, 4.6 seconds.
“Mostly — 70 % today.” 14 of 20 lines evidenced · 4 need work · 2 missing
Every requirement line carries its cited passages. SAMP 2025–2030 v3.2 §1.3 gives effect to the Asset Management Policy AMP-01 rev 4 (6.2.1 a); §4.1 carries the Decision-Making Framework DMF-02 and the value Lumina seeks in four measures — safety, service, whole-life cost and environment (6.2.1 b). Open the SAMP and each passage is highlighted, with a margin note on what it proves.
Margin note, 6.2.1 a: “Shows the SAMP is consistent with the policy, by name and revision.”
SAMP §5.4 says the capabilities needed are identified through the Asset Management Capability Plan, approved by the Steering Group. The only version is v0.4, marked draft and not approved. Line 6.2.1 d is graded needs work, and the next step is for Ines Carvalho to take v0.4 to the Steering Group on 27 Oct and send the approved version.
“Needs work — the only version is v0.4, not approved. Drafts never count as evidence.”
SAMP §10.1 commits to a review each September; the September 2025 review is on file, nothing for September 2026. SAMP §9.2 says Finance reconciles the plans to the approved budget each June; the latest found is FY2024–25. Each gap names the auditor's likely question and its owner — Helena Varga and Priya Nandakumar — with request R-031 and R-032 drafted, due Tue 3 Nov, two weeks before the audit. Amara sends both.
“80 % when the 2 requests come back — 16 of 20 lines.”
“What is missing for 7.6 Data and information?” 57 %, 4 of 7 lines. The information requirements are set in IRR-01 and procedure PR-14 covers the data life cycle, but the plan to collect, integrate, improve and share asset data is missing — PR-14 §5 calls it “to be issued”. The Asset Data Standard ADS-01 v0.9 covers electricity assets only.
The auditor will ask: “Show me your plan to collect, integrate, improve and share asset data.”
Requests move from drafted to sent, received and accepted. R-031 and R-032 are sent, due 3 Nov. R-019 to Ines Carvalho, competence evidence for investment decision roles, is 4 days overdue, and one click sends reminders to overdue owners. R-024 is back from Tobias Lindqvist: ADS-01 v1.0, Part 3, water assets.
“Requests are due 14 days before the audit: Tue 3 Nov.”
Amara clicks Check it. The evidence checker reads the version and approval (v1.0, approved by the Asset Data Board on 9 Oct), the scope (Part 3 covers 11 water asset classes, from mains to reservoirs) and requirement 7.6 b. The document is accepted, and clause 7.6 moves to 71 %, the whole standard to 85 %.
“Checked by the evidence checker: v1.0 approved · 11 water asset classes · meets 7.6 b”
Ardenvale's plan arrived on 6 Oct. Each session shows its clauses, who attends and its readiness: SAMP, objectives and plans on Tue 17 Nov at 75 % with 2 missing; the Harrowfield 132/33 kV substation visit at 100 %. Last year's two minor nonconformities, NC-2025-03 and NC-2025-04, show as closed with their closure evidence.
Likely question for 13:00 on Tue 17 Nov: “How are your asset management plans aligned with the budget?”
The audit pack assembler collects the cited passages for 142 lines, freezes 212 cited documents at the version cited — 0 drafts — and indexes them in 27 folders by clause, each with its gaps and owners. Known gaps go to Gareth with the owner's action plan and date. Nothing is shared with Ardenvale Assurance until he signs.
“Ready for the Director — nothing is shared until Gareth Mensah signs.”
The same audit, seen by the four people who carry it — what the run-up looked like, and what it looks like now.
Six agents map every document to the clauses, name what is missing and draft the requests; the asset management office sends them and the Director signs.
Reads every document in the evidence library and maps passages to the 142 requirement lines of ISO 55001:2024, recording the line, the passage and why it applies. It re-runs when a document changes.
Checks the version, approval, date, scope and review period of every evidence document, and grades it current, out of date, draft or missing by the evidence rules in Settings.
For every line without current evidence, names in the auditor's words the document the auditor will ask for, the question likely to be asked and why the evidence falls short.
Finds the owner of each missing document in the document register and drafts a short, specific request: the document, the clause, what the auditor will ask and a due date 14 days before the audit.
Answers an auditor's question during the audit with the cited passages, and logs the question, the answer and who showed it. If no evidence exists, it says so plainly.
Collects the cited documents at the version cited, builds an index by clause and line, and lists the known gaps with their owners and action plans.
Signs the pack and accepts known gaps. The agents propose; a named person decides.
Ask in plain words about any clause, document or request — or say what to do. Every answer cites the passage.
Are we ready for clause 6.2?
70 % — 14 of 20 requirement lines are evidenced, from the SAMP to the Objectives Register. Two documents are missing: the September 2026 SAMP review record the plan commits to, and the FY2026–27 budget reconciliation — the latest is FY2024–25. Both requests are drafted to Helena Varga and Priya Nandakumar.
Which gaps could the auditor raise as a major finding?
None on its own, but two sit at the heart of 6.2.1: a SAMP with no record of its yearly review, and no current tie to the budget. The other gaps are drafts to approve or records to file. Only the auditor grades a finding.
Is last year's pump-station criticality finding closed?
Yes. NC-2025-03 was raised in November 2025. Criticality Method CM-03 v2 was approved on 9 February, and internal audit confirmed it on 41 of 41 pumping stations in September. The closure evidence is in the audit pack.
Send the two 6.2 requests
Sent: R-031 to Helena Varga for the SAMP review record and R-032 to Priya Nandakumar for the FY2026–27 reconciliation, both due Tue 3 Nov with a reminder every 5 days. Clause 6.2 reads 80 % once both are back and checked.
12 screens from the working solution, on its sample data. Pick one to see it large.
The audit, how evidence is graded, how requests go out and who owns each clause are settings. Changes are saved as a draft and take effect when the Director approves them.
| Setting | Default | Choose from |
|---|---|---|
| Drafts never count as evidence | On | On · Off — a document marked draft or without an approval is graded “draft” |
| Performance reports older than this need work | 3 months | A number of months |
| Review records older than this are missing | 12 months | A number of months |
| Evidence must cover both businesses | On | On · Off — electricity and water, where the line applies to both |
| Re-check every document when it changes | On | On · Off — the clause mapper and evidence checker run on every new version |
| Requests due before the audit | 14 days | A number of days before day 1 of the audit |
| Reminder every | 5 days | A number of days, until the document arrives |
| Send requests without review | Off | On · Off — off: every request is sent by a person |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample utility data · “target” = the design goal, measured in the pilot · “estimated” = our estimate (about 6 weeks per audit cycle, for a utility running electricity and water) · “typical” = published figures (Glocert, common ISO 55001 audit findings — a major finding closed and verified before certification, typically with a follow-up audit within about 90 days; AWWA, 2025 — 21 % of water utility staff can retire within 5 years). Context: NQA, ISO 55001 transition gap analysis (2024); ISO TC 251; UKAS transition to ISO 55001:2024 by 31 July 2027 (Water Magazine, 2026). People, Lumina Utilities, Ardenvale Assurance, sites and documents named on this page are fictional — characters and sample data in the working solution.
Software that shows, clause by clause, whether an asset management system has the evidence an ISO 55001 auditor will ask for. ISO 55001 Audit Readiness maps your own documents to every requirement line of ISO 55001:2024, cites the passage that evidences each one, and names what is out of date, still a draft or missing — with its owner and a drafted request.
You ask in plain words — “Are we ready for clause 6.2?” The clause mapper matches passages from your documents to the clause's lines, the evidence checker checks version, approval, date and scope, the gap finder names what is missing, and the request drafter writes a request to each owner. In the sample case it read 1,246 documents and answered in 4.6 seconds.
Yes. It maps all 27 subclauses and 142 requirement lines of the 2024 edition, and marks the clauses that are new or revised — including 4.5 decision-making, 6.2.1 the SAMP's content, 6.3 planning of changes, 7.6 data and information, 7.7 knowledge, 10.3 predictive action and the new management review inputs in 9.3. Certified organisations must move to the 2024 edition by 31 July 2027.
Yes. The auditor question answerer answers from the evidence library only, cites each passage and logs the question, the answer and who showed it. If no evidence exists it says so plainly. Before the audit, the audit plan shows the questions each session is likely to bring.
No. The gap finder names what is missing and what the auditor is likely to ask; no agent grades a nonconformity — only the auditor does. The solution prepares your evidence; the certification body still audits it.
Yes. An evidence rule checks that evidence covers both businesses where a line applies to both. In the sample case it found an objectives briefing record for nine electricity depots but none for the six water depots, and an asset data standard that covered electricity assets only.
Yes. Agents draft requests; only the Asset Management Systems Lead sends them, and documents sent back are checked before they count. The Director of Asset Management accepts known gaps with an action plan, approves changes to the evidence rules and signs the audit pack before anything is shared with the auditor.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your SAMP, asset management plans, document register and last audit report — and it goes live once every quality gate has passed. We will walk you through it on your own evidence first.
Defects caught while they grow: every structure compared with last year's flight.
1-min demoAsset Health IndexThe same capital budget removes 2.5× the risk, every score traced to its evidence.
1-min demoMaintenance Knowledge SearchDecades of fixes, searchable before the expert retires.
1-min demoWe'll run ISO 55001 Audit Readiness on a sample of your own SAMP, plans and last audit report.