Most “operational readiness frameworks” are a diagram. Boxes, arrows, a pyramid if the designer was feeling ambitious, and nothing underneath that tells you who owns each box, when its work must finish, or what evidence proves it is done. A diagram describes readiness. A framework governs it. The difference shows up at handover, which is the worst possible place to discover it.
This is the anatomy of a working operational readiness framework: the streams it must cover, the phases it moves through, and the governance that holds it together. It is the structure behind the 27-checkpoint readiness checklist we publish separately. The checklist tells you what must be true; the framework is how a project organises the work that makes it true.
Quick Links
- The short answer
- Why the three-pillar version is not enough
- The nine streams, grouped by what they protect
- The timeline: influence falls as steel rises
- Governance: what makes a gate a gate
- The three phases a framework moves through
- Anchor it to a standard, or defend it forever
- Four ways frameworks fail
- Frequently asked questions
The short answer
An operational readiness framework organises the work of preparing an organisation to operate a new asset. A complete one has four parts: nine readiness streams covering the organisation, the asset and the licence to operate; a timeline counted back from first ore; governance, meaning a named lead, stream owners, and review gates that examine evidence; and assurance that maps to a recognised standard rather than a house method.
Why the popular three-pillar version is not enough
Ask a search engine about operational readiness and you will meet the same summary everywhere: people, processes, systems. It is a fine description and a dangerous framework. The streams that actually stop plants (operating approvals that were never separated from construction approvals, a year-one budget nobody built, social-licence conditions nobody confirmed) all hide inside “processes” until the week they surface. A three-pillar summary gives those streams no owner, no deadline and no gate.
A framework earns the name when every stream that can stop the plant has all three.
The nine streams, grouped by what they protect
Each stream carries an owner and a set of deliverables. The checkpoint-level detail and completion dates are published separately, so here is what each stream exists to produce.
The organisation and its people
- Organisational readiness: the readiness program itself. A named lead, a costed plan with its own budget and schedule, and defined review gates. The stream that makes the other eight real.
- People and capability: the operations and maintenance organisation designed down to position level. Recruitment is sequenced against construction milestones, and key appointments are made early enough to own their own decisions.
- Operating model and processes: what your team does versus contractors, the work management process designed end to end, and a ramp-up curve with written assumptions.
The asset and its systems
- Asset management and maintenance readiness: criticality, maintenance strategy from the design, preventive maintenance built before the equipment arrives.
- Systems and technology: the asset register and hierarchy, vendor data secured through the EPC and OEM contracts, a CMMS loaded and proven before start-up.
- Supply chain and logistics: spares analysed and ordered against lead times, a materials catalogue built to a standard.
The licence and the money
- HSE, risk and regulatory compliance: statutory registers, operating approvals tracked in their own right, statutory position holders appointed.
- Finance, commercial and working capital: a bottom-up year-one budget, operating contracts tested against design intent, the asset live in the financial system.
- Stakeholder and community readiness: engagement running, commitments registered, a grievance mechanism that outlives construction.
Three groups, one test. If your framework’s streams all sit in the middle group, you have a maintenance readiness plan wearing a framework’s name tag. See maintenance readiness vs operational readiness for why that gap decides the first year.
The timeline: influence falls as steel rises
A framework without a timeline is a wish list with structure. Every stream’s work is dated backwards from first ore, for one reason: your ability to shape cost and reliability is highest at the design table and falls with every phase the project completes. Data standards belong in EPC and OEM purchase orders before they are executed. Maintenance strategy is built from drawings while construction runs. The CMMS proves itself before commissioning needs it. Defer any of these past its window and you are no longer scheduling work. You are pricing recovery.
Months before first ore that the framework has to start, because the decisions that shape cost and reliability are made at the design table and get harder to change with every phase the project completes.
That is why the framework runs with construction rather than after it, and why the honest answer to when the framework should start is at design, 24 to 30 months before first ore.
Governance: what makes a gate a gate
Governance is where most frameworks quietly fail. The working version has three parts:
- One named lead. A readiness lead who answers to the operator, not to the construction contract, with the whole nine-stream scope reporting through them. Who should carry that accountability is its own decision, and it shapes everything downstream.
- Nine stream owners. Named people, not departments. A stream owned by “the project” is owned by nobody.
- Review gates that examine evidence. Each gate has a named approver and a defined question, tied to the project’s own stage gates. And each gate reviews evidence, meaning the loaded CMMS, the executed contract clause, the populated register, rather than status reports. A gate that accepts a status report instead of evidence is a meeting, not a gate.
The three phases a framework moves through
However a project labels them, working frameworks run the same arc, and it is how we structure our own operational readiness engagements:
- Diagnose. Establish where the project actually sits against first ore, stream by stream, scored on evidence. A fixed-scope diagnostic exists for exactly this, and a free self-score gives a first read in minutes.
- Blueprint. Design the framework for this project: streams scoped, owners named, deliverables dated against the schedule, gates aligned to the project’s stage gates.
- Build and assure. Deliver the streams, and assure them, with evidence collected as the work completes so that handover is a confirmation rather than an investigation.
Anchor it to a standard, or defend it forever
A house-brand framework invites a question at every gate: says who? Anchoring the framework to ISO 55001 answers it once. The asset management and reliability architecture is written to the standard, the maintenance build is structured to hold up under audit, and the assurance trail is one a financier’s due diligence team already recognises. We have written the operational readiness standard a major greenfield gold project is being delivered under on exactly this basis. The framework governs how readiness is scoped, gated and assured across the build, and it survives scrutiny because it maps to something bigger than the firm that wrote it.
Four ways frameworks fail
- The diagram without governance. Streams named, nobody owning them, no gates. Describes the work; governs nothing.
- The summary mistaken for structure. People, processes and systems, with the licence and the money left implicit, until an approval or a budget stops the plant.
- The binder without the build. Governance documents in beautiful order sitting on an empty CMMS. The framework was real; the readiness was not.
- Gates that wave things through. Approvers accept intent, the gap compounds quietly, and the framework certifies a project that is not ready. Evidence at every gate is the whole discipline.
Put a framework under your project
If your project has a diagram where the framework should be, start with where you actually stand. The free readiness scorecard scores all nine streams against your first ore date in about five minutes, and the diagnostic scores them against evidence seen. The projects that ramp on plan are not the ones with the best diagrams. They are the ones where every stream had an owner, a date, and a gate that checked.
Frequently asked questions
What is an operational readiness framework?
An operational readiness framework is the structure a project uses to organise, govern and assure the work of becoming ready to operate a new asset. A complete framework defines the readiness streams, dates every stream’s work back from first production, names a lead for the program and an owner for each stream, and reviews progress at gates that examine evidence rather than status reports.
What is the difference between an operational readiness framework and a checklist?
The checklist states what must be true and by when: verifiable conditions with completion dates. The framework is how the project organises the work that makes those conditions true, through stream owners, a costed plan, review gates and an assurance trail. Projects need both. A checklist without a framework has no one to close its gaps, and a framework without a checklist has nothing concrete to gate against.
How many streams should an operational readiness framework have?
Enough that every way the plant can fail to operate has an owner. In our framework that is nine: organisational readiness, people and capability, operating model and processes, asset management and maintenance readiness, systems and technology, supply chain and logistics, HSE, risk and regulatory compliance, finance, commercial and working capital, and stakeholder and community readiness. Three-pillar summaries compress the last three into “processes”, which is where projects get surprised.
What are the phases of an operational readiness framework?
Three, whatever a project calls them. Diagnose where the project sits against first production, stream by stream and on evidence. Blueprint the framework, meaning streams, owners, dated deliverables and gates aligned to the project’s stage gates. Then build and assure, collecting evidence as work completes so handover confirms readiness rather than discovering its absence.
Does ISO 55001 require operational readiness?
Not by name. ISO 55001 specifies an asset management system, not a project methodology. But a readiness framework built to the standard inherits its authority: the asset management architecture, maintenance build and assurance trail align with what auditors, financiers and future certification already recognise, which is why anchoring readiness to ISO 55001 beats defending a house method gate by gate.