Six stages, each ending in a deliverable
Network projects rarely fail on technology; they fail in the gaps between stages, where nothing can be signed off. This page sets out six stages from first contact to steady state: what happens, what is handed over at the end, and who signs.
The six stages
Network projects come adrift not on technology but on missing deliverables between stages: a survey with no written conclusion, a proposal with no bill of materials, a cutover with no rollback plan. The six stages below each end in something that can be accepted.
| Stage | Deliverable at the end | Signed by |
|---|---|---|
| 01 Inventory | Current-state and risk register | Customer contact |
| 02 Proposal and quote | Proposal, bill of materials, quotation | Commercial leads on both sides |
| 03 Contract and kick-off | Contract, SLA annex, implementation plan | Authorized representatives |
| 04 Build and cutover | Configuration baseline, cutover record, rollback plan | Project manager |
| 05 Acceptance and handover | Acceptance report, asset register, operations manual | Customer acceptor |
| 06 Steady-state operations | Monthly SLA scorecard, quarterly review minutes | Service manager |
01 — Inventory
We count devices, circuits, vendor contracts and open issues. Nothing is bought and nothing is reconfigured: the current state is written down as a document you can argue with.
Output: a current-state and risk register stating which equipment still has life, where the risks are, where operational load sits and when existing contracts expire. Scope and duration follow the project.
02 — Proposal and quote
A proposal has to land as a list: what goes in each site, which link, who installs it and when. The quote comes from the same source as the proposal, with no later costs buried in it.
Output: proposal, bill of materials and quotation. The four service lines — managed operations, implementation, spares and support, advisory — are priced separately, so a customer can buy just one.
03 — Contract and kick-off
The contract annex pins two things down: the severity definitions (what counts as a P1) and the acceptance criteria (what counts as passed). Leave either vague and every incident and every acceptance becomes a fresh argument.
Output: contract, SLA annex and implementation plan. The kick-off confirms the customer contact, the working windows and the change approval path.
04 — Build and cutover
Multi-site work runs at night with trading as usual by day. A rollback plan exists before the cutover, the configuration baseline is captured during it, and the asset register is checked afterwards.
Output: configuration baseline, cutover record and rollback plan. Where no downtime window exists, the cutover design is reviewed separately at design stage.
05 — Acceptance and handover
Acceptance follows the criteria agreed in the contract, with no extra conditions added late. Handover clears assets, configuration, accounts and contacts in one go, so operations does not have to go back and ask the build team what happened.
Output: acceptance report, asset register and operations manual. Projects under MLPS or industry audit add log retention, policy configuration and remediation records.
06 — Steady state
A monthly SLA scorecard and a quarterly service review. The scores feed the next period's adjustments — including whether to extend to other sites, which is a decision that should rest on data, not on a hunch.
Output: monthly scorecard and quarterly review minutes. The quarterly review also checks asset changes against contract headroom.
See office addresses and contact details →