Government Office Relocation
Stakeholder-driven scope change managed through quarterly cumulative-impact reviews. Programme held inside a 5% scope creep envelope.
- Value
- $38M
- Duration
- 18 months
- Outcome
- Delivered
- Cumulative change tracked weekly
- Stage-gate reviews held
- Quarterly cumulative-impact reviews stop death-by-trivial-change
- Stage gates need teeth or they become slide reviews
Project context
A consolidation of three government department offices into a single 11,000 m² fit-out across two floors of a heritage-listed office building in central Wellington. Scope included the strip-out of the existing tenancies, a base-build upgrade to the mechanical services and life-safety systems, a full Category 1 fit-out for 850 staff including secure zones, meeting suites, a ministerial floor and a public-facing reception, and the relocation of three live IT environments. The contract was a construction-management arrangement with the government as principal, a project manager appointed under a separate consultancy contract, and 14 trade contracts let directly. Programme at award was 18 months. Total fit-out value NZD 56 million (approximately USD 38 million). The defining risk on this project from day one was scope change driven by a large stakeholder group with overlapping authority.
Why small changes are the real risk on government fit-outs
Government office fit-outs rarely fail through a single large scope change. They fail through the cumulative weight of small changes — a door moved here, a meeting room re-sized there, an AV upgrade in one zone, a security re-classification in another — each of which is too small to trigger a formal change-control conversation but which collectively shift the programme and the budget by 15–20% over the life of the job. On this project, the project manager set an explicit rule at kick-off: any change above NZD 10,000 went through formal change control, and a quarterly cumulative-impact review was held to roll up all changes below that threshold. This was the single most important governance decision on the project.
The quarterly cumulative-impact review
Every quarter, the project controls team produced a one-page summary of every change below the formal threshold made in the previous three months, with the cumulative cost and the cumulative schedule impact. The summary was presented to the steering committee with an explicit decision: continue, pause, or re-scope. Three of the six quarterly reviews resulted in a 'pause and consolidate' decision, where the team stopped accepting small changes for four weeks while the cumulative impact was absorbed into the working schedule. The total cumulative change at substantial completion was NZD 2.7 million, 4.8% of contract value, against an industry benchmark of 12–18% on comparable government fit-outs. The quarterly review was the mechanism that kept the project inside its envelope.
Stage gates that actually decided something
The project ran six formal stage gates: concept design, developed design, technical design, pre-construction, mid-construction, and pre-handover. Each gate had explicit pass criteria documented in advance, with named decision-makers and a 'do not pass' option that was used twice — once at developed design when the secure zones design was incomplete, and once at pre-construction when the IT relocation plan had not been signed by the operator. A stage gate that cannot fail is a slide review, not a gate. On this project, the gates had teeth because the principal had explicitly empowered the project manager to recommend non-pass and had committed to back that recommendation publicly. Both non-pass decisions added four to six weeks to the gate but saved an estimated four to six months of downstream rework.
IT relocation and the operator interface
The relocation of three live IT environments into the new tenancy was the single most complex sub-programme on the project, with a 72-hour cutover window over a long weekend and zero tolerance for a missed window. The IT operator was a separate government agency with its own programme and its own governance. The project manager treated the IT interface with the same discipline as a structural interface: a named interface owner on both sides, a weekly 30-minute interface meeting, and a documented interface register with 64 items at peak. The cutover was achieved inside the 72-hour window with three non-critical items deferred to the following weekend.
What this project says about stakeholder-heavy fit-outs
The hardest part of a government fit-out is not the construction. It is the stakeholder management. The construction is well-understood, the trades are competent, the design is straightforward. What is consistently under-managed is the volume of small, individually-reasonable change requests from a large stakeholder group. The disciplines that work are: a formal change-control threshold that catches the meaningful changes, a quarterly cumulative-impact review that catches the death-by-a-thousand-cuts, and stage gates with explicit pass criteria and the authority to fail. These three disciplines together kept this project inside a 5% scope-creep envelope on a job where the regional norm would have been 15%. The cost of running these disciplines is approximately five days of project-management time per quarter. The return is measured in millions.