Project preparation
What should a civil infrastructure recovery project brief contain?
A project brief is not a sales deck. Its job is to give the owner, engineers, suppliers and locally responsible entities one verifiable starting point. Incomplete information does not prevent a start, but every unknown must be visible.
- Published
- Published
- Reading time
- 5 minutes
- Prepared and reviewed by:
- CIVIFORWARD Technical Desk
State why the project exists
Record the location, asset owner, operator, final beneficiaries and civilian end use. The first page should also say whether the recovery target is a building, a piece of equipment, a public service or a complete operating chain.
- Location and service boundary
- Ownership, authority and operating responsibility
- The service currently interrupted
- The minimum operating level to be restored
Separate field evidence from judgement
Photos, coordinates, drawings, nameplates, inspection records and historical operating data are evidence. Cause of damage, repairability and budget are conclusions still to be tested. Mixing the two distorts quotations and responsibility boundaries.
- Verified facts
- Statements from site personnel
- Engineering assumptions
- Unknowns that require inspection
Include entry conditions and the funding path
At minimum, describe site access and safety, local permits, procurement procedure, source of funds, payment gates, insurance and transport constraints. Without these, equipment selection and schedule statements remain preliminary assumptions.
Rewrite goals as acceptance outcomes
“Restore water supply” should be broken into population served, flow, water-quality basis, continuous operating time, energy use, consumables and operator needs. Each target needs evidence, an owner and an acceptance method.
Verification points and references
Use boundary
This note is a method for organising early project information. It is not an engineering appraisal, cost conclusion or project approval.