A completed installation and a functioning resilience service are different milestones. A proposal should explain how it intends to move from one to the other.
Consider an illustrative water service. The record of installation might establish that equipment was delivered and commissioned. It would not, on its own, establish that someone can maintain it, that recurring costs are covered, or that the service will keep meeting its intended need.
Name the operator—not just the project lead
Identify the institution responsible for day-to-day operation after the initial project period. Clarify its mandate, staffing, access to maintenance support and relationship to the asset owner.
Where responsibility is proposed rather than agreed, label it that way. A stakeholder mentioned in a proposal is not necessarily a confirmed operator.
Separate committed resources from assumptions
A costed operating plan should distinguish routine operation, preventive maintenance, repair, replacement, monitoring and contingency requirements. State the planning period and the assumptions behind the estimates.
Show which resources are committed, which depend on a future decision and which remain unfunded. Expected user revenue, a future grant and an approved operating allocation should not appear as the same financing state.
Define the evidence of continuing performance
Specify what will be observed and at what frequency. Depending on the service, useful records might include downtime, maintenance completed, resource use, user access or a measure of service quality.
Describe the measurement method and its limits. Completion photographs and expenditure records may support an installation claim; they do not necessarily support a claim about continuing service or resilience outcomes.
Agree what happens when performance changes
A monitoring plan needs a response route. If a performance threshold is missed, who receives the signal? Who checks it? Who can change the operating plan, approve repair, or pause an unsafe activity?
Use proportionate triggers. A small maintenance issue, a repeated service interruption and an unresolved safety concern may require different decisions and escalation routes.
Keep handover and continuity reviewable
Record the handover, open conditions and next review date. When staff or institutions change, the incoming team should be able to see the service obligations, outstanding work and basis of earlier decisions.
This is the Governance Spine in practice: identify a gap, make it visible, route responsibility and review, and preserve a record that others can examine. A complete operating plan does not guarantee resilience. It makes the assumptions behind that claim more open to scrutiny.
Before calling it resilient
Ask for a costed operating plan that names the responsible institution, distinguishes committed finance from funding assumptions, and defines the evidence and triggers for corrective action.
The key question is not only “Can we install it?” It is also “Who will keep the service working, with which resources, and what happens when conditions change?”
About this version
This article was prepared on the date shown. Illustrative examples are not reports of a particular programme.
Fracture → Signal → Spine → Assurance