Certified is not ready

It is possible to have every subsystem certified and still not have a railway that is ready to open. The two are related, but they are not the same, and the space between them is where a surprising number of programmes get caught.

What certification tells you

Certification says the parts meet the standard. The signalling system has been assessed. The rolling stock has its approvals. The fire systems are listed and tested. Each element, taken on its own, satisfies the requirements placed on it. That is necessary — but it is not sufficient.

What readiness tells you

Operational readiness asks a different question: does the whole thing work, safely, together, on the first day of service — with real staff, real procedures, real degraded-mode scenarios and real interfaces between systems that were each certified in isolation? Readiness lives at the seams: the handover between systems, the operating and maintenance procedures, the competence of the people, the emergency plans, the interfaces that no single certificate covers.

Certification is about the parts. Readiness is about the whole.

Minding the gap

The gap catches programmes because certification is tracked closely — it has owners, milestones and paperwork — while readiness is often assumed to fall out of it automatically. It does not. Readiness has to be assured in its own right: integrated testing across subsystem boundaries, operational trials, procedure validation, and a clear-eyed view of what happens when something fails on day one. A programme that manages certification diligently but treats readiness as an afterthought can arrive at its opening date with a stack of certificates and a railway that still is not ready to carry passengers.

The discipline is to assure both, explicitly, and never to let a certificate be mistaken for a railway.