Readiness Criteria
How to Define and Prove Readiness
Readiness criteria make “ready” measurable. They define the conditions that must be demonstrated, the evidence that must exist, and the capability that must be present before an organization can make an informed readiness decision for a defined operating state or transfer boundary.
ICXA REFERENCE DEFINITION — SYNTHESIZED FROM THE OPERATIONAL READINESS STANDARDS
A readiness criterion is a measurable, evidence-linked condition established for a defined Readiness Envelope and decision, used to determine whether the required Operational Readiness capability has been demonstrated across the integrated People, Organization, Asset, and Systems & Processes core capabilities.
Key distinction: A checklist asks whether tasks or documents are complete. A readiness criterion asks whether a defined capability or condition has been demonstrated strongly enough to support a decision.
Readiness criteria are decision criteria, not activity lists
A useful readiness criterion is written for a specific readiness decision, not simply for a project activity. It states what condition must be true, for what scope, at what point, and what evidence will demonstrate that condition.
The ICxA Operational Readiness requirements require organizations to establish measurable readiness criteria for the four integrated core capabilities and coordinate those criteria with progressive reviews and decisions. Operational Readiness activities must also be integrated with the master schedule so that readiness constraints, evidence needs, reviews, escalation points, transition dates and decision points are visible.
Readiness criteria therefore convert a broad statement such as “operations is ready” into a set of traceable, reviewable propositions that can be tested against evidence, capability status, risk and uncertainty.
A readiness criterion should identify 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. Required Condition
The measurable capability, condition or result that must be demonstrated.
4. Evidence
The controlled evidence needed to demonstrate the criterion and the owner of that evidence.
5. Threshold
The acceptance threshold, decision state or condition for proceeding.
6. Risk Treatment
How deficiencies, uncertainty, dependencies, exceptions and residual risks will be surfaced and treated.
Readiness is always bounded
A readiness statement is not meaningful without a defined Readiness Envelope. ICxA uses the Readiness Envelope to define the scope limit for Operational Readiness planning, evidence, review and recommendation across system, asset, organizational, operational-responsibility and transfer boundaries.
The same project can therefore have different readiness states for different operating boundaries. A facility may be technically available while the receiving organization, maintenance capability, information systems or operational authority for the relevant envelope are not yet ready.
Readiness criteria must cover the whole operating capability
ICxA requires the four Operational Readiness core capabilities to be evaluated as one integrated socio-technical system. Criteria should not be limited to the physical asset.
People
Criteria should test: competence, role clarity, staffing, capacity, resilience, authority to operate and demonstrated capability for normal, abnormal and emergency scenarios.
Illustrative criterion: “Before operational control is assumed, all control-room roles for this Readiness Envelope have demonstrated the required role-based competencies and authority to operate, with current evidence and adequate shift coverage for normal and emergency operation.”
Organization
Criteria should test: governance, operating processes, decision authority, escalation, interfaces, emergency preparedness, physical security and organizational integration.
Illustrative criterion: “The operating authority, escalation path, interface responsibilities and emergency decision rights for the Readiness Envelope have been demonstrated through a recorded scenario or exercise and accepted by the receiving operational authority.”
Asset
Criteria should test: physical and functional condition, compliance, integrity, operability, maintainability, preservation, external inputs and ability to sustain and recover operation.
Illustrative criterion: “The asset conditions required for the proposed operating state are verified, known temporary conditions and constraints are documented, and required utilities, spares and third-party support are available for the defined operating period.”
Systems & Processes
Criteria should test: procedures, work management, operational information, maintenance systems, digital and non-digital enabling systems, configuration and change control.
Illustrative criterion: “Approved operating and maintenance procedures, asset data, work-management functions and enabling systems required for Day One operation are current, accessible to users and aligned to the approved asset configuration.”
Apply the system-wide operating constraints of safe · sustainable · reliable · adaptive operation across all four capabilities.
Criteria must be linked to evidence before the decision
The ICxA requirements state that the organization first defines readiness and the associated readiness criteria for the applicable decision. Operational Readiness Evidence is then traced to those criteria, kept current at the decision point and interpreted within the relevant organizational and risk context.
Readiness Decision
→
Readiness Envelop
→
Readiness Criteria
→
Controlled Evidence
Readiness Decision
→
Readiness Envelop
→
Readiness Criteria
→
Controlled Evidence
For decisions that also require Level 1 Outcome Authorization, the relevant readiness evidence is evaluated against the applicable Outcome Evidence Need. The Outcome Auditor evaluates evidence sufficiency independently; the Outcome Director makes the Outcome Authorization decision. A Readiness Recommendation supports that decision but does not replace it.
Evidence volume is not evidence sufficiency
A large handover package or completed document register does not establish readiness. Evidence must be relevant to the criterion, traceable to the Readiness Envelope, current at the decision point, credible, and interpreted in the operating and risk context. Technical evidence becomes Operational Readiness Evidence only when it is mapped to readiness criteria and considered together with the other core capabilities and readiness risks.
Practical implication: the project should be able to show not only that a record exists, but which readiness criterion it supports, which Readiness Envelope it applies to, whether it is current, and what decision it informs.
Weak criteria versus decision-useful criteria
The difference is not more words. The difference is whether the statement can support a controlled decision.
Capability
Weak Statement
Decision-Useful Criterion
People
“Operators trained.”
“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
“Roles defined.”
“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
“Equipment complete.”
“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
“CMMS ready.”
“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.”
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 staffing, competence, operating authority, emergency preparedness, procedures, asset data, maintenance systems, external services, spares, or unresolved operating constraints. A physical progress percentage does not test whether the receiving organization can safely and effectively operate, maintain, support and sustain the asset.
Readiness criteria expose these transition risks before the in-service decision by requiring each material capability claim to be supported by current evidence for the defined Readiness Envelope.
Readiness criteria versus common substitutes
Common Substitute
What It Tells You
Why It Is Not Enough
Activity checklist
Whether planned activities were marked complete.
Completion of an activity does not prove the resulting operational capability.
Document register
Whether expected documents exist.
Existence does not prove currency, usability, configuration alignment or decision relevance.
Construction progress
How much physical scope is reported complete.
Physical completion does not establish organizational, people or process readiness.
Milestone date
When a transition is planned to occur.
A date does not demonstrate that the prerequisite readiness conditions are satisfied.
Punch-list count
How many identified items remain open.
Count alone does not express readiness risk, consequence, uncertainty or capability impact.
Readiness criterion
Whether a measurable capability or condition has been demonstrated for a defined decision and boundary.
It is decision-useful only when tied to controlled evidence, risk and a defined threshold.
A practical six-step method
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. Define the required capability. Determine what must be true across People, Organization, Asset, and Systems & Processes for that operating state.
4. Write measurable criteria. Express each material condition so that a reviewer can determine whether it is demonstrated, not merely intended.
5. Map evidence and owners. Identify the controlled evidence needed for each criterion, who produces it, who reviews it, and when it must be current.
6. Define treatment of gaps and uncertainty. Establish how readiness risks, dependencies, exceptions, mitigations, conditions and escalation are handled before the recommendation and decision.
Integrate readiness criteria with the schedule
Readiness criteria should not sit in a separate spreadsheet disconnected from project controls. ICxA requires Operational Readiness activities to be integrated with the project master schedule or equivalent planning control so that readiness constraints, deliverables, evidence needs, reviews, escalation points, transition dates and decisions are visible. This makes readiness forecastable rather than discoverable only at the end.
A readiness review tests criteria, evidence, capability and risk together
A Readiness Review is not a document-completeness meeting. It reviews the defined readiness criteria, Operational Readiness Evidence, integrated status of the four core capabilities, material readiness risks, uncertainty, conditions and the status of the Readiness Envelope at the leadership and authority level appropriate to the decision.
The review should make unresolved readiness gaps visible as operational risks. Deficiencies should be described in terms of consequence, uncertainty, mitigation, accountable owner and decision effect rather than reduced to a generic punch-list count.
The recommendation and the authorization are different
The designated Operational Readiness role prepares the Readiness Recommendation for the defined Readiness Envelope. The controlled recommendation states whether progression should proceed, proceed with conditions or be held. Where Level 1 Outcome Authorization applies, the Readiness Recommendation and Operational Readiness Decision Package support the authorization process but do not themselves authorize the outcome.
Frequently asked questions
What is a readiness criterion?
“A readiness criterion is a measurable, evidence-linked condition established for a defined Readiness Envelope and decision, used to determine whether the required Operational Readiness capability has been demonstrated across the integrated People, Organization, Asset, and Systems & Processes core capabilities.”
What is the difference between a readiness criterion and a readiness condition?
“ICXA-20202 defines a readiness condition as a specified condition that must be satisfied as a prerequisite for readiness confirmation, a Readiness Recommendation, Transfer of Operational Control or submission into the applicable Outcome Assurance authorization process. ‘Readiness criterion’ is used in ICXA-20201 for the measurable criteria against which readiness and evidence are evaluated. On this page, ICxA uses ‘readiness criterion’ as the measurable, decision-useful expression of the applicable readiness condition or capability requirement.”
Are readiness criteria the same as a checklist?
No. A checklist can confirm that tasks or documents are complete. A readiness criterion tests whether a defined condition or capability has been demonstrated with suitable evidence for a specific decision and boundary.
Do readiness criteria apply only to the asset?
No. ICxA requires readiness to be evaluated across People, Organization, Asset, and Systems & Processes as an integrated socio-technical system.
When should readiness criteria be defined?
During readiness planning, before the applicable readiness decision and early enough to shape evidence generation, capability development, schedule integration and risk management. The criteria should not be invented at the review to match whatever evidence happens to exist.
What evidence is needed for a readiness criterion?
Evidence depends on the criterion, decision, Readiness Envelope and risk. It must be controlled, traceable, current and decision-relevant. 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.
Readiness should be proven before the transition, not inferred after it
Readiness criteria give projects and operating organizations a common language for deciding whether a transition is actually supportable. They make the required capability explicit, connect it to evidence, expose readiness risk early and provide a traceable basis for the decision to proceed, proceed with conditions or hold.