Completing projects and reviewing benefits

Decide what completion actually means

A project is not complete merely because the budget has been spent or the planned finish date has arrived. Compare delivered work with the approved scope and authorised changes. Establish which requirements have been met, what remains unresolved and who can accept the result.

For the fictional Juniper Workshop collection service, installed cabinets are only one deliverable. The booking process, access tests, staff preparation and operating instructions may also be necessary for acceptance. All Juniper facts and figures here are original illustrative assumptions.

Sometimes management must choose between completing and abandoning an unfinished project. Past spending informs accountability and lessons, but an irrecoverable amount is not a benefit of continuing. Compare future consequences of the available choices, including closure costs, recoveries and obligations.

Obtain acceptance and transfer operational ownership

Agree acceptance criteria before the final review. Retain test results, approvals and a record of authorised changes. If minor work remains, identify the item, responsible person, deadline and any effect on use; do not hide it under an unexplained “substantially complete” label.

Acceptance should involve the authorised customer or sponsor and the people who will operate the result. A signed document is useful evidence, but an uninformed signature cannot make an unworkable handover effective. Discuss concerns while they can still influence delivery.

Concept sources: Emad E. Aziz, Project closing: the small process group with big impact, PMI, 2015 — formal acceptance, transition to operations and release of project resources are substantive closure activities.

Operations needs relevant records, training, support contacts and access permissions. Avoid leaving the temporary team responsible indefinitely for routine service work, or transferring responsibility without the resources to perform it.

Reconcile the money before declaring the cost final

The final bank payment is not necessarily the final project cost. Work received but not yet invoiced, open commitments, disputed amounts and remaining closure activity can all affect the position. Reconcile approved budgets and changes with recorded costs and supported estimates of outstanding obligations.

Explain significant differences: changed scope, price changes, rework, estimation error and timing have different implications. Preserve the original baseline and authorised revisions so a reader can distinguish initial forecasting quality from later decisions. Cash paid, cost recognised and total expected commitment answer different questions.

After approval to close the financial records, prevent unrelated new spending being charged to the project. Keep an authorised route for late invoices or corrections and assign responsibility for any continuing warranty or contractual matters. Closing a cost code should not mean losing track of an obligation.

Release resources and capture usable lessons

People, equipment and remaining materials need deliberate disposition. Arrange staff return or reassignment, transfer useful equipment to its operational owner, and assess surplus items for authorised reuse, return or disposal. Idle stock and unassigned equipment can still create storage costs and responsibility gaps.

Capture learning while the people involved can explain decisions. A final workshop helps, but waiting until every specialist has departed loses context. Separate evidence from hindsight: a decision can have been reasonable using the information then available even if the eventual outcome was disappointing.

A lesson becomes useful when an owner changes a checklist, estimate, contract approach or working practice. A large archive of reports is not evidence that future decisions improved. Preserve the reasoning and conditions so another team can judge whether the lesson applies to its circumstances.

Review benefits after delivery

Delivery measures and benefit measures answer different questions. Cabinet installation and staff training are outputs. Successful customer collections are an operational outcome. Improved convenience, reduced avoidable handling or stronger retention may be benefits, but they require evidence after the service is used.

Concept sources: APM, Benefits management and project success — benefits can arise after handover and need continuing accountability.

Set a baseline, target, measure, review date and owner while the business case is being developed. Juniper might measure failed collections as a proportion of attempted collections. Suppose the baseline is 8%, the target is 3% and the first review shows 4%. The rate has improved by four percentage points but remains one percentage point above target. Review volumes, customer mix and other changes before attributing the improvement entirely to the project.

Financial claims also need care. Suppose the new process releases 75 staff hours each month, valued internally at $30 an hour. That indicates $2,250 of capacity, not automatically $2,250 less cash paid. If actual overtime spending falls by $600 while additional service costs are $250, the identified monthly net cash saving is $350. The released capacity may still be valuable; report its use separately and avoid counting the same benefit twice.

Concept sources: Neil White, Benefits management — an opportunity not just a process, APM, 2019 — operational changes and nonfinancial improvements can enable later financial benefits.

Use the review to make the next decision better

A post-completion review should revisit strategic fit, stakeholder experience, costs, outcomes and remaining risks. Use interviews, operating records or feedback suited to the question. Separate dissatisfaction caused by an unmet requirement from a new preference outside the agreed scope; both can matter, but they imply different action.

Benefits that have not yet appeared need an owner and a further review date. If assumptions have failed, decide whether to adjust operations, undertake a separately justified improvement or accept that the expected benefit will not be realised. Do not rewrite the original expectation to make every result appear successful.

Self-check: Juniper opened on time and within budget. Customers use the service, but expected handling-cost savings have not appeared. Is the project successful?

Answer: It met important delivery criteria, but the benefit claim remains unproven. Check whether the process changed as intended, whether released time is being used differently, whether costs actually fell and whether additional service costs offset savings. Report delivery performance and benefit performance separately. The operational owner and sponsor should agree the next action rather than treating launch as the end of accountability.

Sources and further reading

Study-guide reading: Strategic Management Accounting, Module 4, printed pages 203–207 — completion, strategic and stakeholder review, financial closure, resources and organisational learning.

Concept sources: Aziz, Project closing: the small process group with big impact, 2015

Concept sources: APM, Benefits management and project success

Concept sources: White, Benefits management — an opportunity not just a process, 2019