Preview the ICxA Standards - No Cost Free access for Associate Members Access the Standards

Bankable Readiness

Readiness that is defined, proven and tied to capital

A project is not bankable without a credible readiness maturity plan. Readiness conditions and criteria make “ready” measurable. Independent assessment of evidence proves it. The Readiness Holdback ties that proof to the release of capital.

What readiness covers: Readiness on this page means every aspect of readiness set out in the ICxA Standards. System readiness and operational readiness are the two largest, and the Standards define several others. A project is bankable when all of them are planned, assessed and maturing, not when one of them is.

1. Define: readiness conditions and criteria

Readiness conditions identify the capabilities that must exist for a defined operating state or transfer boundary. Criteria state what each condition must satisfy and what evidence will show it. Together they convert a broad statement such as “the project is ready” into a set of traceable, reviewable propositions, each of which can be tested against evidence to give a condition state.

The definitions and worked examples in this part are drawn from the Operational Readiness Standards. The same structure of condition, criterion and evidence is how each aspect of readiness in the ICxA Standards, system readiness included, is made measurable.

ICXA REFERENCE DEFINITION — SYNTHESIZED FROM THE OPERATIONAL READINESS STANDARDS

Readiness is the demonstrated state in which the capabilities, arrangements and conditions required for the intended operational transition are sufficiently established to support the intended operation, with material residual risks understood and appropriately controlled.

A readiness condition is an observable or assessable aspect of operational capability, preparedness or transition capability that exists at a defined point in the transition from construction to operations and may influence transition performance or risk.

A readiness criterion is the defined expectation, requirement, threshold or decision rule, established for a defined Readiness Envelope and decision, against which the state of a readiness condition is judged across the integrated People, Organization, Asset, and Systems & Processes core capabilities.

Key distinction: A checklist records whether readiness activities and documents are complete. A readiness condition is the capability those activities are meant to produce, and its criterion asks whether that capability has been demonstrated strongly enough to support the decision. Training completed is an activity; required operator competence is the condition.

What a readiness criterion must identify

A useful readiness criterion is written for a specific readiness decision, not for a project activity. It identifies six things.

  1. Decision. The readiness decision or transition the criterion supports.
  2. Readiness Envelope. The system, asset, organizational, operational-responsibility and transfer boundary to which it applies.
  3. Readiness condition. The capability whose state is being assessed, described neutrally as a condition rather than as an activity, document or outcome.
  4. Indicators and evidence. What will be observed or measured, the controlled evidence that substantiates it, and the owner of that evidence.
  5. Threshold. The threshold or decision rule the evidence is judged against, and the condition state required for proceeding.
  6. Risk treatment. How deficiencies, uncertainty, dependencies, exceptions and residual risks will be surfaced and treated.

Readiness is always bounded. The same project can have different readiness states for different Readiness Envelopes: a facility may be technically available while the receiving organization, maintenance capability, information systems or operational authority for that envelope are not yet ready.

Worked example: the four core capabilities of operational readiness

For operational readiness, ICxA requires four core capabilities to be evaluated as one integrated socio-technical system, under the system-wide constraints of safe, sustainable, reliable and adaptive operation. Criteria should not be limited to the physical asset. Each example below sets a weak statement against a criterion that can support a controlled decision.

People

Criteria test: competence, role clarity, staffing, capacity, resilience, authority to operate and demonstrated capability for normal, abnormal and emergency scenarios.

Weak statement: “Operators trained.”

Decision-useful criterion: “Before operational control is assumed for Unit 1, each person assigned to a control-room role has demonstrated the role-based competencies required for normal, abnormal and emergency scenarios; qualification evidence is current; exceptions are recorded; and minimum shift coverage is available.”

Organization

Criteria test: governance, operating processes, decision authority, escalation, interfaces, emergency preparedness, physical security and organizational integration.

Weak statement: “Roles defined.”

Decision-useful criterion: “Decision authority, operational control, escalation and interface responsibilities for the Readiness Envelope are approved and have been demonstrated through a recorded operating scenario before operational control is assumed.”

Asset

Criteria test: physical and functional condition, compliance, integrity, operability, maintainability, preservation, external inputs and ability to sustain and recover operation.

Weak statement: “Equipment complete.”

Decision-useful criterion: “For the proposed Day One operating state, required asset conditions, compliance status, temporary configurations, operating constraints, maintainability provisions, utilities, spares and critical external support are documented and acceptable for the defined Readiness Envelope.”

Systems & Processes

Criteria test: procedures, work management, operational information, maintenance systems, digital and non-digital enabling systems, configuration and change control.

Weak statement: “CMMS ready.”

Decision-useful criterion: “Before the readiness decision, the maintenance and work-management functions required for Day One operation are configured for the approved asset hierarchy, accessible to authorized users, populated with the minimum decision-relevant asset information, and demonstrated through representative work scenarios.”

How criteria are built

Criteria are set during readiness planning, early enough to shape evidence generation and capability development. They are not invented at the review to match whatever evidence happens to exist. The method has six steps.

  1. Define the readiness decision. State the operating state, transfer, transition or other decision the criteria must support.
  2. Define the Readiness Envelope. Establish the asset, system, organizational, responsibility and transfer boundaries.
  3. Identify the readiness conditions. Determine which capabilities must exist, and phrase each neutrally so its state can be assessed.
  4. Set indicators and criteria. State what will be observed or measured and the threshold or decision rule it is judged against.
  5. Map evidence and owners. Identify the controlled evidence needed, who produces it, who reviews it, when it must be current, and how independent it needs to be.
  6. Define treatment of gaps and uncertainty. Establish how readiness risks, dependencies, exceptions, mitigations and escalation are handled before the recommendation and decision.

Criteria are integrated with the project master schedule, so that readiness constraints, evidence needs, reviews and decision points are visible. This makes readiness forecastable rather than discoverable only at the end.

A checklist, a document register, a construction progress figure, a milestone date and a punch-list count each describe activity or status. None of them gives the assessed state of a defined capability, judged against an explicit criterion, for a defined decision and boundary.

2. Prove: evidence, assessment and authorization

The organization first defines readiness and the associated readiness criteria for the applicable decision. Readiness evidence is then traced to those criteria, kept current at the decision point and interpreted within the relevant organizational and risk context.

Five terms keep that discipline. The readiness condition is what is assessed. Indicators are what is observed or measured. Evidence is what substantiates the observation. The criterion is what the evidence is judged against. The condition state is the resulting conclusion, recorded at a defined point in time or transition milestone. A readiness activity such as training, commissioning or a turnover review is the means by which a condition is developed, not proof that it exists.

The traceability chain: Readiness Decision → Readiness Envelope → Readiness Condition → Readiness Criteria → Indicators → Evidence → Evidence Confidence → Condition State

Evidence volume is not evidence sufficiency

A large handover package or completed document register does not establish readiness. Evidence must be relevant to the condition and criterion, traceable to the Readiness Envelope, current at the decision point, credible, and interpreted in the operating and risk context. The confidence that can be placed in it depends on its provenance, contemporaneity, completeness, relevance, independence, consistency and auditability. Two projects reporting the same state may rest on very different evidence, and an asserted state without sufficient supporting evidence is not demonstrated readiness.

Why “98% complete” is not a readiness criterion: A project can be 98% physically complete and still be materially unready for operation. The remaining risk may sit in untested systems, staffing, competence, operating authority, emergency preparedness, procedures, asset data, maintenance systems, external services, spares or unresolved operating constraints. Equally, readiness does not mean 100% complete. Major projects routinely enter operation with residual work and temporary arrangements. The question is whether the conditions required for the intended transition are sufficiently established and demonstrated, with residual risks understood and controlled.

Installed does not mean ready. A date does not mean ready. A completed checklist does not mean ready.

Review, recommendation and authorization

A Readiness Review is not a document-completeness meeting. It reviews the state of each readiness condition against its criteria, the readiness evidence and the confidence it carries, material readiness risks and the status of the Readiness Envelope, at the leadership and authority level appropriate to the decision. Deficiencies are described in terms of consequence, uncertainty, mitigation, accountable owner and decision effect, not reduced to a punch-list count.

The review produces a Readiness Recommendation, which states whether progression should proceed, proceed with conditions or be held. Where Level 1 Outcome Authorization applies, the Outcome Auditor evaluates evidence sufficiency independently and the Outcome Director makes the Outcome Authorization decision. A Readiness Recommendation supports that decision but does not replace it.

3. Finance: the Readiness Holdback

Readiness conditions and criteria make readiness measurable. The Readiness Holdback turns that measurement into a financing instrument. It ties each construction drawdown to the assessed state of the readiness conditions due by that date, so that the cost of non-readiness is paid when it is created, not discovered at start-up.

Capital projects are funded against construction progress. Because condition states are not assessed at drawdown, a project can draw every dollar on schedule while the causes of a late start-up build unnoticed. When the delay surfaces, the money is spent, liquidated damages are capped, insurance responds after the event and lenders face a restructuring. The Readiness Holdback moves that cost forward to the drawdown where the shortfall is assessed, and places it with the borrower and its sponsors.

Immediate

The consequence lands at the drawdown where the shortfall is assessed, not at commissioning or completion.

Sized to delay

The amount reflects what non-readiness costs, never what readiness work costs.

Progressive

It grows while readiness maturity stalls, holds while it recovers, and releases when it is back on plan.

Deterministic

Every input is fixed at financial close or assessed against criteria fixed at financial close.

No credible readiness maturity plan, no financial close

The instrument begins before the first draw. A readiness maturity plan is a condition precedent to financial close. It sets out the readiness conditions for the project across every aspect of readiness in the ICxA Standards, system readiness and operational readiness among them. For each condition it states the criterion to be met, the evidence that will show it, the owner of that evidence, and the date by which the condition must reach its required condition state.

Credible means assessed. The Outcome Auditor evaluates the plan independently and the Outcome Director authorizes it. The authorized plan is written into the credit agreement as the Required Maturity Curve, and it cannot be changed without lender consent.

WORKING DEFINITION FOR THE INSTRUMENT

Readiness maturity is the proportion of the readiness conditions due at an assessment date, across all aspects of readiness, whose assessed condition state meets its criterion, supported by evidence of sufficient confidence. It is expressed on a scale of 0 to 100. It is a measurement of demonstrated capability, not a grade.

How it works at each drawdown

Condition states are assessed on a fixed cycle, typically quarterly, and each assessment governs the draws until the next one.

  1. Assess the condition states. The Outcome Auditor evaluates the readiness evidence against the criteria fixed at financial close and reports the condition state of each readiness condition due. The result is the Measured Maturity.
  2. Compare with the plan. Measured Maturity is compared with the Required Maturity for that date. A shortfall beyond the Tolerance Band is the Maturity Gap.
  3. Price the gap. The gap is converted into implied months of start-up delay and priced at the monthly Cost of Non-Readiness.
  4. Apply recognition. A recognition share is applied to the priced amount. It steps up at every assessment where the gap has failed to narrow.
  5. Adjust the draw. The facility agent withholds or releases the difference between that target and the balance already held.
  6. Fund the difference. The borrower funds any withheld amount from sponsor equity. The contractor is still paid in full for construction progress.

Maturity Gap = Required Maturity − Measured Maturity − Tolerance Band, never below zero
Implied Delay = Maturity Gap × Delay Conversion Factor
Priced Exposure = Implied Delay × Cost of Non-Readiness Rate
Target Holdback = Priced Exposure × Recognition Share

Anyone holding the terms agreed at financial close and the assessed condition states can reproduce the amount. The facility agent has no discretion over it.

Illustrative example

A $5B project with $4B of debt and quarterly draws of about $200M. Readiness maturity stalls from the third quarter and recovers from the sixth, and the holdback follows it up and back down to zero. Choose how the project behaves and adjust the terms to see the holdback respond.

The arithmetic at the default terms, for the project that recovers:

Quarter Required Maturity Measured Maturity Gap beyond band Priced Exposure Recognition Share Withheld or released Holdback balance
Q1 10 10 0 $0 – $0 $0
Q2 18 16 0 $0 – $0 $0
Q3 26 20 3 $18M 25% +$4.5M $4.5M
Q4 34 22 9 $54M 50% +$22.5M $27.0M
Q5 42 24 15 $90M 75% +$40.5M $67.5M
Q6 50 38 9 $54M 75% −$27.0M $40.5M
Q7 58 54 1 $6M 75% −$36.0M $4.5M
Q8 66 65 0 $0 held $0 $4.5M
Q9 74 74 0 $0 reset −$4.5M $0

The $4.5M withheld from the third quarter’s draw is about 2% of that draw. The $40.5M withheld from the fifth quarter’s draw is about 20%, bringing the balance held to $67.5M.

Terms fixed at financial close

Term What it is Illustrative value
Required Maturity Curve The readiness maturity the project must have reached at each assessment date, taken from the authorized readiness maturity plan 10 at the first quarter, rising 8 points a quarter
Tolerance Band The shortfall that triggers nothing 3 points
Delay Conversion Factor Implied months of start-up delay per point of gap beyond the band 0.2 months per point
Cost of Non-Readiness Rate The cost of one month of start-up delay: interest on the debt plus the owner’s fixed costs $30M per month
Recognition Schedule The share of Priced Exposure withheld, stepping up while the gap fails to narrow 25%, 50%, 75%, 100%
Release Test Consecutive assessments inside the band needed to clear the balance 2
Remediation Trigger The point at which further draws are suspended Gap still not narrowing after recognition reaches 100%
Sponsor Standby Committed equity, backed by a letter of credit, that funds withheld amounts and steps down as readiness maturity is demonstrated $180M

What happens to the money

Withheld

A withheld amount is deferred debt, not cancelled debt. It stays undrawn in the facility while sponsor equity, drawn on the standby, covers construction payments.

Released

As readiness maturity recovers the target falls, and the difference is drawn at the next draw. The last of the balance clears after two consecutive assessments inside the band.

Escalated

If the gap will not close, further draws are suspended until the Outcome Director authorizes a recovery plan. A missed recovery plan is an event of default.

Who does what

The party that assesses is never the party that pays. The Outcome Auditor evaluates evidence sufficiency independently and is appointed by the lenders, with the cost passed to the borrower as it is for the independent engineer. The Outcome Director authorizes the readiness maturity plan and any recovery plan.

The independent engineer carries the assessment in the drawdown certificate alongside construction progress and cost to complete. The borrower supplies the evidence, and the sponsors fund what is withheld. ICxA maintains the standards the assessment rests on and credentials the people qualified to fill the two outcome roles. It takes no part in any transaction.

All figures in this section are illustrative. It describes a proposed mechanism and is not legal, financial or insurance advice. Any use in a financing requires drafting by lenders’ counsel.

Help shape the Readiness Holdback

ICxA is developing this instrument with lenders, insurers, independent engineers and lenders’ counsel. If you finance, insure or advise on capital projects, there are three ways to take part.

Talk to ICxA

Discuss the instrument, or test its terms against a financing you know.

Apply it through your LTA

See what a lender adds to its technical advisor’s mandate to have readiness assessed.

Contribute to the evidence

Delay and loss data is what will size the instrument’s terms. See the joint research with IMIA.

Frequently asked questions

Does readiness here mean operational readiness?

No. Readiness covers every aspect of readiness set out in the ICxA Standards. System readiness and operational readiness are the two largest, and the Standards define several others. The worked examples on this page come from the Operational Readiness Standards, but a readiness maturity plan and the Readiness Holdback apply to all of them together.

What is the difference between a readiness criterion and a readiness condition?

The readiness condition is the capability being assessed, such as required operator competence or critical deficiency status. The readiness criterion is what it is judged against, such as required critical roles being competency-verified before the relevant start-up milestone. The condition state is the conclusion the evidence supports at that point. ICXA-20202 uses readiness condition in its prerequisite sense: a specified condition that must be satisfied before readiness confirmation, a Readiness Recommendation, Transfer of Operational Control or submission into the applicable Outcome Assurance authorization process. In that sense a condition is satisfied when its state meets its criteria for the decision concerned. ICXA-20201 uses readiness criterion for the measurable criteria against which readiness and evidence are evaluated.

Are readiness criteria the same as a checklist?

No. A checklist can confirm that tasks or documents are complete. A readiness condition and its criterion test whether the capability those tasks were meant to produce has been demonstrated with suitable evidence for a specific decision and boundary. Completing an activity can be evidence of progress, but it is not proof that the condition exists.

Does readiness mean everything is complete?

No. Readiness is judged by sufficiency for the intended transition, not by absolute completion. Projects routinely enter operation with residual work, open items and temporary arrangements. Readiness means the capabilities required for the operating state being entered are sufficiently established and demonstrated, with material residual risks understood and controlled. A condition judged sufficient for a limited initial operating mode may not be sufficient for full commercial operation.

What evidence is needed for a readiness criterion?

Evidence depends on the condition, criterion, decision, Readiness Envelope and risk. It must be controlled, traceable, current and decision-relevant, and evidence that demonstrates the capability carries more weight than evidence that only records that an activity was completed. Demonstrations, scenarios, technical records, competency evidence, procedures, digital-system evidence, asset information and operational records can all be relevant depending on the criterion.

Does meeting readiness criteria authorize operation?

Not necessarily. Readiness criteria support a Readiness Review, Readiness Recommendation and readiness decision. Where the transition also requires Level 1 Outcome Authorization, authorization remains a separate governance decision based on independently evaluated evidence and explicit acceptance of residual risk.

Is the Readiness Holdback a penalty?

No. It is deferred debt, not a fee or a fine. A withheld amount stays in the facility and is released when readiness maturity returns to the required curve. The cost to the sponsors is that equity goes in earlier than planned and the shortfall is visible to the lending syndicate.

Who appoints the Outcome Auditor in a financing?

The lenders, with the cost passed to the borrower, as it is for the independent engineer. The party that assesses readiness is never the party that pays for a shortfall.

Is the contractor still paid when an amount is withheld?

Yes. The borrower funds the withheld amount from sponsor equity, so payments for construction progress continue and the construction contract is unaffected. The holdback acts on the borrower and its sponsors, however readiness has been scoped with contractors.