ISO 55001 now requires you to write down how you decide

Try to audit an investment decision taken three years ago.

The papers are all there. Four options were appraised, one was recommended, the recommendation was approved by people entitled to approve it. Nothing is missing and nothing is irregular.

Now try to establish whether the right option was chosen. You cannot, and the reason has nothing to do with the strength of the evidence. There is nothing to test the decision against. No criteria were written down before the appraisal, so there is no standard by which the choice could be wrong. All you can do is form your own view and set it beside theirs, which is not assurance. It is two opinions.

The 2024 edition of ISO 55001 has made that gap a nonconformity.

What Clause 4 now contains

The context clause has five parts. The first four are familiar from the 2014 edition: understanding the organisation and its context, understanding the needs and expectations of stakeholders, determining the scope of the asset management system, and the asset management system itself.

The fifth is new. Clause 4.5, asset management decision-making, has three subclauses:

• 4.5.1 Framework
• 4.5.2 Criteria
• 4.5.3 Methods, processes and tools

ISO lists its addition among the main changes from the first edition, alongside the strategic asset management plan and knowledge.

A new clause in a management system standard reads, to most people being asked to conform with it, as one more thing to document. It is worth knowing what the committee thought it was for, because the stated reason is narrower and more useful than the requirement on its own.

Read that way the clause is not asking for a document. It is asking whether a decision taken at the bottom of an organisation can be traced to an objective set at the top, and the framework, criteria and methods are the three things without which that trace cannot exist. An organisation that can produce all three and still cannot follow one decision back to one objective has satisfied the clause and missed the point of it.

A note on what follows. This article describes what the clause covers and where it sits. It does not reproduce the requirements, and anyone implementing against it needs the standard itself rather than a description of it.

Why a committee added this

Read the 2024 revision of ISO 55000 next to it and the direction is hard to miss.

ISO 55000 is the vocabulary and overview document, revised at the same time. Among its own listed changes: the principles of asset management were revised, outcomes were introduced, maturity was introduced, and the explanation of the elements of an asset management system was deleted.

That last one is the interesting deletion. The 2014 edition spent effort describing what an asset management system is made of. The 2024 edition removed that description and, in the requirements standard, added a clause about how decisions get made.

The revised principles point the same way. ISO 55000:2024 gives three: value, alignment and leadership. Alignment is defined as asset management aligning financial, technical and operational decisions with the organisational objectives.

So the standard has moved from describing a system to requiring decisions, and from documenting what exists to evidencing how choices are made. An organisation that reads 4.5 as another document to produce has read it backwards.

What the 2024 edition of ISO 55001 changed, clause by clause, marking each as new, revised or renamed.

Clause	What changed	Status
3	Common core terms, from the Harmonized Structure	New
4.5	Asset management decision-making	New
6.1.2, 6.1.3	Risk and opportunities, separated	Revised
6.2.1	Strategic asset management plan	New
6.3	Planning of changes	New
7.6	Data and information	Revised
7.7	Knowledge	New
8.1	Operational planning and control, including life cycle management	Revised
8.3	Externally provided processes, products, technologies and services	Renamed
10.3	Predictive action, formerly preventive action	Renamed

A committee only clarifies something when it has watched the point being missed. The clauses marked new are the ones where that happened often enough to need text of their own.

The three parts, and which one is hard

The framework is the easiest and the one most organisations can half-produce already. Who decides what, at what value, under whose delegation. Most large organisations have a delegation of authority matrix somewhere, usually written by finance for the purpose of controlling commitment rather than for the purpose of managing assets. It is a start and it is rarely sufficient, because it says who may sign and not what they are supposed to weigh.

Methods, processes and tools is the one people expect to be hard and generally is not. Naming the method is mostly an act of description. The value in the requirement is subtler: an organisation that has to name its method can no longer answer "judgement", and once a method is named it can be examined, taught and applied consistently by someone else.

The criteria are the hard part, and they are hard for a reason that has nothing to do with drafting.

Criteria expose what the organisation actually optimises for. Writing them down forces a choice that most capital governance has been carefully arranged to avoid making explicitly: whether a decision is being taken on capital cost, on whole-life cost, on service outcome, on risk exposure, on political deliverability, or on some unstated weighting of all five that shifts depending on who is in the room.

Criteria that stop at capital cost will, reliably and forever, select assets that are cheap to build and expensive to own.

Everybody involved knows this. It is not a controversial proposition. And yet the criteria are usually not written, because writing them creates an obligation to apply them, and applying them occasionally produces the answer the organisation did not want.

That is precisely why the clause is useful, and precisely why it will be the one most organisations fail first.

What happens when the operating cost has no owner

, read: Operations is told to take part in the business case. Nobody asks it to sign.Operations is told to take part in the business case. Nobody asks it to sign.

Why context has to come first

There is an order to Clause 4 and it is not arbitrary, though as with the rest of the standard, ISO does not claim it as an implementation sequence. The dependency is real regardless.

You cannot write decision criteria until you know which decisions are yours. That is what scope establishes, and scope depends in turn on knowing what the organisation is for and who relies on it. An organisation that drafts criteria before settling scope will write criteria for decisions it does not control and omit the ones it does.

This matters more than it sounds, because the most common failure at this stage is a sequencing failure, and it is a comfortable one.

The instinct, almost universally, is to write the asset management policy first. It is the shortest document, the most quotable, the easiest to get signed, and it makes visible progress in the first month. So it gets written, approved and framed, and it says the organisation will manage its assets in a manner that maximises value while ensuring safety, sustainability and compliance.

Nobody can act on that, because a policy written before the criteria is a statement of intent about decisions nobody has yet defined how to make. The right order runs the other way: establish what you control, work out how choices within it will be judged, and only then declare the intent that governs them. A policy written after the criteria is short too, but it is short because the difficult things have already been settled somewhere else.

Doing this while the assets are arriving

The organisations in this region establishing asset management functions right now are mostly doing it under a deadline, and many of them are delivery organisations becoming owning organisations.

That produces a particular version of the problem. The asset base was specified by someone else, under criteria that were never written down, often by people who have since left. The new function is asked to document a decision-making framework for an estate whose foundational decisions are already taken and cannot be revisited.

The temptation is to write the framework to describe what happened, which produces a document that is accurate, compliant and completely inert. The alternative is to write it for the decisions still to come, which on any large asset base is most of them by value: renewals, disposals, capacity changes, the entire operating and maintenance regime, and every future capital programme.

What examining this looks like

The absence of documented criteria is now a nonconformity against the standard rather than an observation about maturity, which changes the conversation with a board considerably.

Beyond that, the useful tests are ordinary. Ask for the criteria. Check they cover the whole life of the asset and not only the capital cost. Take one significant option decision and trace it back through them, confirming the recorded rationale matches what the criteria say should have mattered. Confirm the delegation limits exist in writing and test one commitment against them.

The assurance framework asks the same question of a single programme rather than of the organisation, at the point the options are appraised, where the criteria either existed beforehand or did not.

None of those tests requires a specialist. They require somebody to ask for a document that either exists or does not.

---

Sources. ISO 55001:2024, Asset management, Asset management system, Requirements, second edition, July 2024, prepared by ISO/TC 251, ISO standard 83054. Clause 4 structure, the subclause titles of 4.5 and the list of main changes are taken from the contents and foreword as published by ISO. ISO 55000:2024, Asset management, Vocabulary, overview and principles, second edition, July 2024, ISO standard 83053, for the revised principles at Clause 4.2 and for its own list of main changes, including the deletion of the explanation of the elements of an asset management system and the introduction of maturity. Guidance on applying ISO 55001 is published separately as ISO 55002. The requirement text of both standards is described here rather than reproduced.