Zoo Relocation Project—Part 6: Closure and Benefits Realisation

Public opening is not project closure. Part 6 takes the Zoo Relocation through contract closeout, lessons learned, benefits tracking, and the final audit of outcomes against the CEO's original brief.

Series recap. Parts 1–5 carried the project from the CEO's letter through initiation, planning, and phased execution to the public opening. Part 6 addresses what happens after the ribbon is cut — a phase novice PMs routinely neglect and one that the Group Report rubric explicitly requires (Success measurement).

The Challenge

Ask a first-year student when a project ends, and they will say "when deliverables are handed over." Ask the sponsor of a real capital project and you get a very different answer: "when the business case benefits are realised, or when we abandon trying."

These two definitions are separated by months or years. The CEO's letter contains two objectives that cannot be evaluated until well after the new site opens: "Generate $20 million profit" requires a revenue cycle to measure, and "long-term survival a critical success factor" requires observation periods of months to years per species. Neither is evaluable on opening day. This gap — between the PM's "done" and the sponsor's "benefits realised" — is the largest cause of disputed project closures in practice.

The PM Framework Applied

PMBOK's Close Project or Phase (4.7) is brief in the guide. What it under-emphasises — and what PRINCE2, MSP, and the UK Infrastructure and Projects Authority emphasise heavily — is the distinction between project closure and benefits realisation:

Project Delivery

Execution

Commissioning

Public Opening

Project Closure

Contract Closeout

Admin Closure

Lessons Learned

Handover

Benefits Realisation

Benefits Tracking

Post-Implementation Review

Benefits Validation

Relationship details

From	Relationship	To
Project Delivery	leads to	Project Closure
Project Closure	leads to	Benefits Realisation

Delivery is the PM's traditional domain. Closure is a brief transition period still owned by the PM. Benefits Realisation extends beyond the PM's direct involvement — but the PM sets up the tracking framework before departing, because nobody else will.

Step 1: Contract Closeout

Every procurement contract must be formally closed: verify deliverables accepted, resolve outstanding claims, pay final invoices, release performance bonds, archive contract documentation, issue formal closeout letters.

For the Zoo: specialist transport, enclosure construction, veterinary consulting, legal and planning advisors, and interim facilities contracts from the dual-site period. Warranty claims on construction are particularly common — closeout should happen while records and memories are fresh.

Defence-sector parallel. On a BAE or Thales project, contract closeout includes a formal supplier performance review feeding the prime's preferred-supplier database. Closing a contract without this throws away intelligence future projects will need.

Step 2: Administrative Closure

Release team members back to home departments or external employers; close project accounts; archive all documentation (plans, schedules, change requests, risk register snapshots, minutes); terminate project-specific tools and accesses; produce final reports; formally declare the project complete.

Archiving deserves particular emphasis. A Zoo archive including the final risk register (annotated with which risks materialised), lessons learned, and final budget-versus-baseline analysis becomes invaluable for any future capital project the Zoo undertakes.

Step 3: Lessons Learned

A four-category model:

Lessons Learned

What Went Well

What Did Not

What We Learned

Do Differently

Early regulator engagement — prevented permit delays

Staff in planning retained — specialist knowledge

Staged approach preserved — revenue during transition

60% reuse estimate — was over-optimistic

Dual-site ops — under-resourced

Crisis comms tested — too late

Structural survey must precede — reuse assumptions

Dual ops need dedicated — surge staffing budget

Front-load structural surveys — to first 30 days

Add surge staffing reserve — to day-one budget

Relationship details

From	Relationship	To
Lessons Learned	leads to	What Went Well
Lessons Learned	leads to	What Did Not
Lessons Learned	leads to	What We Learned
Lessons Learned	leads to	Do Differently
What Went Well	leads to	Early regulator engagement — prevented permit delays
What Went Well	leads to	Staff in planning retained — specialist knowledge
What Went Well	leads to	Staged approach preserved — revenue during transition
What Did Not	leads to	60% reuse estimate — was over-optimistic
What Did Not	leads to	Dual-site ops — under-resourced
What Did Not	leads to	Crisis comms tested — too late
What We Learned	leads to	Structural survey must precede — reuse assumptions
What We Learned	leads to	Dual ops need dedicated — surge staffing budget
Do Differently	leads to	Front-load structural surveys — to first 30 days
Do Differently	leads to	Add surge staffing reserve — to day-one budget

The value of lessons learned is entirely contingent on whether they are read by future projects. An archive full of beautifully-written documents nobody retrieves is organisational theatre, not learning.

Step 4: Handover to Operations

The deliverable is a functioning Zoo. The operator is the ongoing business, not the project team. Handover is the formal transfer of responsibility. A defensible handover pack includes:

• As-built documentation — reflecting what was actually built, not what was designed
• Operations and maintenance manuals for every system
• Warranty and support contacts with expiry dates
• Training records proving operational staff are trained
• Residual risks still live and now owned by operations
• Open issues operations must complete
• Benefits realisation framework for measuring business-case outcomes

Handover must be formal with signatures, not a quiet email. Until accepted by operations, the PM technically retains responsibility — an ambiguity that causes chaos when something goes wrong in the first weeks after opening.

Step 5: Benefits Realisation Framework

This separates mature from amateur PM. The CEO's success criteria cannot be measured at closure. The PM's final duty is to establish how they will be measured in the months and years ahead.

Each row has a named owner, measurement method, and reporting cadence. Benefits realisation must include a re-baseline mechanism — if benefits are not on track, something must happen (remedial action, revised target, or formal acknowledgement of partial success). Without this it is just bureaucratic record-keeping.

Step 6: Post-Implementation Review

Six months after closure, the organisation conducts a PIR — a different exercise from lessons learned. Lessons learned reflects on how the project was run. The PIR reflects on whether the project achieved its business purpose. Typically conducted by an independent party — internal audit, external consultant, or senior executive outside the sponsor's line.

Project Closure — Formal completion

M1 Handover — Operational ownership transferred

M3 Operations Review — Early performance check

M6 Post‑Implementation Review — Benefits vs intent

M12 First Benefits Report — Measured outcomes

M24 Final Benefits Validation — Sustained value confirmed

Relationship details

From	Relationship	To
Project Closure — Formal completion	leads to	M1 Handover — Operational ownership transferred
M1 Handover — Operational ownership transferred	leads to	M3 Operations Review — Early performance check
M3 Operations Review — Early performance check	leads to	M6 Post‑Implementation Review — Benefits vs intent
M6 Post‑Implementation Review — Benefits vs intent	leads to	M12 First Benefits Report — Measured outcomes
M12 First Benefits Report — Measured outcomes	leads to	M24 Final Benefits Validation — Sustained value confirmed

Step 7: The Final Audit Against the CEO's Letter

The final formal act of closure is returning to the original CEO letter and auditing every requirement against actual outcome:

This table is the most important artefact of closure. It is the PM's accountability statement, honest about partial successes (reuse missed due to structural issues) and pending items (24-month survival data). A board that receives this table has everything it needs to formally declare the project complete.

The Pitfalls

• Treating public opening as closure. The PM walks away, contractors are paid off, and three months later a retaining wall cracks and nobody knows who the engineer was.
• Skipping contract closeout. Unclosed contracts create legal exposure persisting long after the team has dispersed.
• Archiving sloppily. An archive that is not retrievable is not an archive.
• Lessons learned nobody reads. Value depends entirely on retrieval by future projects.
• Forgetting benefits realisation. The most common closure failure — treating delivery as success and walking away.
• Personalising the final audit. A PM whose project missed one criterion is not a failure; a PM who hides a missed criterion is.
• Not celebrating. Ceremonial closure matters for organisational memory and staff morale.

Knowledge Check

1. Six months after opening, two relocated reptile species show mortality significantly above baseline, bringing overall survival below the 95% target. The PM has long departed. Who acts, and what does the benefits framework require?
2. Final reuse came in at 42% against a 60% target. Is this a project failure? Justify your answer in terms of success criteria versus constraints.
3. Lessons learned recommends front-loading structural surveys of reuse candidates. Eighteen months later, the Zoo plans an aviary expansion. What mechanism ensures the lesson is applied, and whose responsibility is enforcement?

Key Takeaways

• Public opening is not project closure. Closure is an administrative process that happens after delivery.
• Benefits realisation happens after closure and extends months or years into the future.
• Contract closeout, administrative closure, lessons learned, and handover are four distinct closure activities.
• Handover must be formal, documented, and signed.
• Lessons learned are only valuable if retrieved by future projects.
• The Post-Implementation Review (months after closure, independent party) evaluates whether the business case proved out.
• The final audit is the PM's honest accountability statement.

---

Series conclusion. Over six articles we have taken the Zoo Relocation from a one-page CEO letter to a signed benefits realisation handover, applying every major PMBOK knowledge area. The value of walking through a single case study at depth is that it makes the connections between knowledge areas visible — how the charter informs stakeholder management, how stakeholder management shapes the communications plan, how the risk register modifies the staging plan, how the staging plan informs closure criteria. A PM who understands only individual processes can manage tasks. A PM who understands the connections can manage projects.

References

• Project Management Institute 2017, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 6th edn, PMI, Newtown Square, PA.
• Office of Government Commerce 2011, Managing Successful Programmes, 4th edn, TSO, London.
• Infrastructure and Projects Authority 2020, Guide for Effective Benefits Management in Major Projects, HM Government, London.
• Bradley, G 2016, Benefit Realisation Management, 2nd edn, Routledge, Abingdon.
• Turner, JR 2014, Handbook of Project-Based Management, 4th edn, McGraw-Hill, New York.
• University of South Australia 2015, MPM411 Zoo Relocation Project Brief, UniSA, Adelaide.