The readiness system
ReadyOps is a readiness assurance system. It sets the obligations that apply to this project, attaches evidence to those obligations, and rolls status up to the gate. Uploading a file does not make you ready.
The board leadership sees
Obligations, evidence and gate status on one board. An SRO can read the state of the initiative in five minutes.
| Deliverable | Context | Evidence | Status |
|---|---|---|---|
| As-Built Drawings & Models Construction |
Civils — roads and grounds | Substantiated | Accepted |
| Construction Completion Certificate Construction |
Main process building | Partial | In progress |
| Certificate of Design Safety & environment |
Pressure systems | None | Not started |
| Alarm & Trip Schedules Safety & environment |
Process control system | Submitted | Submitted |
The unit of work
Most handover tools treat the file as the unit. ReadyOps does not. The system first establishes what must be ready for this classification, these systems, these asset classes and this gate. Then it asks for the evidence that proves it.
What the system delivers
Nine working surfaces. One model of control. This is what stays on the initiative after the review.
Name the initiative. Set classification, systems, asset classes, capability flags and the target stage gate. That scope decides which obligations apply.
The master list is filtered to this project and written as that project’s deliverables. Those obligations stay fixed. Mapping is not a tidy-up after the files arrive.
Quality against the requirement — not against the existence of a file. High understanding with no coverage still shows as not ready.
Evidence lives under the deliverable it substantiates. One file can support more than one outcome where the link is real. A register in the library is not a closed obligation.
What stops Day One becomes an owned action. Action planning and action management sit on the same project context as the board.
Project readiness is a roll-up. Breakdown by Defence Line of Development and by function shows where the heat is — including lines that look busy and are still Level 1.
How heat is shown
The breakdown is not a dashboard of activity. It is whether each line of defence and each function can actually run on Day One.
How the system runs
Classification, systems, asset classes, capability and target gate decide what applies.
The master list becomes this project’s deliverables. Those stay fixed.
Record what you actually have. Variants explain how a requirement is met.
Documents sit under the deliverable they substantiate. One file can serve more than one outcome.
Score quality. Track instance status. Acceptance sits above the file list.
Gaps become actions. Status rolls up by DLoD, function and gate. Then Day One is declared — or not.
What it is not
ReadyOps is requirements-led. We do not invent a mapping to make the file list tidy. We do not open with software. The review names the gap. This is the board that stays.
How it arrives
We open with one live initiative. If control has to run without a hero, this is the board we install.