Pillar 03

Operational readiness: one live status, with the gap named

Readiness is where people assurance and asset assurance meet. VORAST reads both against a defined requirement and returns a status a supervisor can act on, not a figure that needs interpreting.

Unknown is not a pass

A missing requirement profile or missing evidence cannot be treated as Ready. The dashboard distinguishes Ready, Degraded, Not ready and Escalation required, with a freshness timestamp, first failure and suggested response. Evidence percentages support the judgement; they never override a critical failure.

Green, amber, red — and what sits behind each

A status on its own is not useful. What makes it actionable is the named gap underneath it.

  • Ready: the configured critical and advisory requirements are met
  • Degraded: an advisory requirement fails; the capability is reduced
  • Not ready: a critical requirement fails, regardless of high evidence percentages; missing evidence or a missing profile is unknown, never a pass

Drilldown that follows the operation's own shape

Evidence percentages can be high while a critical role is uncovered. The station verdict follows requirements rather than an average; move from organisation and country through site to station or watch to see the first failure and the evidence behind it.

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

VORAST 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?
  • Which in-app gap and suggested response appears when a team drops below requirement?

See what ready looks like for your operation.

Bring your questions about people, assets and response capability. We will show how a connected view could work across your sites and teams.

Request a demo