Skip to content

Handover is not the finish line — so who takes the baton?

Added to your CPD log

View or edit this activity in your CPD log.

Go to My CPD
Only APM members have access to CPD features Become a member Already added to CPD log

View or edit this activity in your CPD log.

Go to My CPD
Added to your Saved Content Go to my Saved Content
benefits management

Ask a project manager when their job ends and most will give you a version of the same answer: at handover. Define the scope, mobilise, deliver, transition into use, close. The iron triangle of time, cost and quality tells us whether we did it well.

I believe that this is the wrong answer — not just for some exotic category of projects, but for all of them.

No project exists to be delivered. Every project exists to deliver benefits: something useful, that gets used, that creates value. Time, cost and quality measure the job; they do not measure the purpose. A project that closes on schedule and on budget but delivers nothing that anyone uses is a beautiful house with no door. Most of us have seen one. Plenty of us, if we're candid, have built one.

The profession knows this in principle — benefits management has been part of our body of knowledge for years, and may go back thousands of years. But our habits still treat handover as the finish line, and the benefits as somebody else's problem downstream. And there is one class of project where that habit is most expensive: projects that change a place and the people in it. Regeneration schemes, community facilities, housing, the renewal of derelict sites. Here the benefits don't merely continue after handover — they begin there, and then compound for thirty or fifty years, either renewing themselves or quietly leaking away.

Consider two identical community housing schemes. Same design, same build, same handover date. In the first, the affordable homes are sold at a discount to their first buyers. Ten years later those buyers have sold at market rates, the discount has vanished into private capital gain, and the scheme is no more affordable than the street around it. In the second, the homes are held by a steward — a community land trust — with resale prices tied permanently to local incomes. Thirty years on, they are still affordable, because an institution exists whose job is to keep them that way.

Same project. Same handover. Utterly different thirty-year outcome. The only difference was a governance decision: whether anyone was constituted to hold the benefit after the project team had gone.

That is what I mean by a steward: not a person, because people move on, but an institution — a trust, a community benefit society, an asset-transfer arrangement with conditions attached — that owns the benefit, an owner that outlives the project. In benefits-management terms, if the benefit owner does not survive handover, the benefits realisation plan is likely a fiction. We have assigned accountability for value that nobody is actually holding.

Some will object that the long-term outcome is the operator's job, or the client's, or local government's — not ours. I think that gives away something the profession should be claiming. The decisions that determine the thirty-year outcome are made inside the project, before handover, and nowhere else: whether affordability is locked in or leaks away; whether a steward exists and how it is constituted; whether the benefit has a named owner with the means to act. By the time the operator inherits the asset, the outcome is largely determined. Our window is precisely the window in which it is won or lost.

So here is the shift I would ask of any project professional, on any project, and most urgently on those that touch communities. Ask three questions at the start, not the end. What would a genuinely net-positive outcome look like here, measured against what would have happened anyway? Who will own the benefit in thirty years? And what must we design in now, before handover, so that they can?

None of this requires new tools. It requires us to stop describing ourselves as people who deliver projects, and start describing ourselves as people who deliver benefits — and to treat handover not as the finish line but as the moment the steward takes the baton. Our job is not done when we hand over. Our job is to make sure there is someone to hand over to.

Hugo explores the evidence behind this argument — including community land trusts, the Big Local programme, and the distinction between sustainability and regeneration — in his current series in PM World Journal. 

 

You may also be interested in:

 

0 comments

Join the conversation!

Log in to post a comment, or create an account if you don't have one already.