Operational readiness: one live status, with the gap named
Readiness is where people assurance and asset assurance meet. reads both against a defined requirement and returns a status a supervisor can act on, not a figure that needs interpreting.
A status on its own is not useful. What makes it actionable is the named gap underneath it.
Green: requirements met — the required people and assets are available
Amber: attention needed — a nearing expiry, outstanding action or reduced capacity
Red: critical gap — a required competency, crew position or asset is unavailable
Drilldown that follows the operation's own shape
Aggregate readiness scores hide the thing that matters. A strong overall figure can sit on top of a single site that cannot field a required role. lets you move from a global view down through country, site and team, so a headline number can always be opened.
The same drilldown works in the other direction. A gap raised at team level is visible in the aggregate view rather than waiting for a monthly report, which shortens the distance between the person who finds a problem and the person who can resolve it.
Readiness as a working tool, not a monthly artefact
Because readiness is derived from live person and asset records, it updates as those records change — a completed assessment, a check-in, a raised defect, a returned asset. The shift handover conversation can then begin from the current position instead of rebuilding it.
It also changes how planning is prioritised. Training and maintenance effort can be directed at the gaps that actually reduce operational capability, rather than spread evenly across a schedule.
Being clear about what this does and does not mean
Readiness visibility does not guarantee an outcome
makes the current position and its gaps visible. It does not replace command decisions, statutory safety systems, alarms or dispatch, and it cannot guarantee the outcome of any operation or emergency.
A live answer, backed by evidence
Every status traces back to the competence, attendance, inspection and certification records that produced it.
Questions worth asking of your own operation
If an event happened in the next ten minutes, which teams could respond at full requirement?
Where does your current readiness figure come from, and how old is it?
Who is notified when a team drops below requirement, and how?