Mike Mullaney All articles
Client Delivery

Closing Time: The Twelve-Point Handover Check I Run Before Any Project Ends

Mike Mullaney
Closing Time: The Twelve-Point Handover Check I Run Before Any Project Ends

Photo by Photo by Vitaly Gariev on Unsplash on Unsplash

There's a particular kind of silence that follows a project which has technically ended but never been properly closed. The final workshop happens, everyone says the right things, and then the shared channel goes quiet. Eight months later the client is paying someone else to unpick a decision nobody wrote down, and you're half-wondering why the phone never rang again.

I've been on both sides of that. And the honest conclusion is that repeat work rarely disappears because the delivery was bad. It disappears because the ending was untidy — and untidy endings are memorable in a way that competent delivery simply isn't.

So here's the routine I now run on every engagement, whether it's a three-week diagnostic or a nine-month programme. It takes about half a day. It has paid for itself several times over.

Start with the paper trail, not the goodbye

Before you think about the closing meeting, get the documents straight. A decent handover pack needs three things: a plain-English runbook for whatever you've built or changed, a decision log covering what was chosen and what was rejected, and an honest section headed 'what we didn't do'.

That last page is uncomfortable to write and it's the most valuable thing in the pack. Every project leaves something on the table. Writing it down means the client hears it from you in a considered way, rather than discovering it in April and deciding it was your fault.

Access is where good consultants quietly fail

Almost every project involves somebody's login. Domains, DNS, hosting, analytics, ad accounts, the CRM, the payment gateway, the code repository, the shared password vault.

Two rules. First, ownership sits with the client from day one, not on the last day — nothing creates resentment faster than a supplier who appears to hold the keys to the kingdom. Second, close-out means revocation as well as transfer. Your own access should be gone, on a date you can point to in writing. If their IT lead asks you to keep an admin account 'just in case', that's fine, but put an end date on it in an email.

The number of UK SMEs I've met who discovered their website was still being billed to a former agency's card is genuinely startling.

Keep less data than you think you need

Under UK GDPR, 'we kept everything just in case' is not a retention policy. Before you close, agree what you're holding, where it lives and when it goes. If you're retaining project files for a contractual or statutory reason, say so and put a date on it. If you're not, delete them and confirm that you've done it.

This is a quietly excellent trust signal. Very few suppliers tell a client their data has been deleted on schedule. The ones who do get remembered at the next procurement round.

Deal with the money before the warm words

Final invoice raised, expenses reconciled, any overrun on days discussed and agreed — all before the closing meeting, not after it. Nothing sours a good relationship faster than a surprise invoice landing three weeks after the thank-you email.

If they use a purchase order or a procurement portal, confirm the invoice has actually landed and is sitting in a payment run. 'Sent' and 'in the system' are not the same thing, and February is a bad month to find out the difference.

Tell them what happens if it breaks

Support arrangements are the most common gap in any handover. Who do they ring? What's covered and what's chargeable? Even if the honest answer is 'nobody, but here's the number of someone good', get it in writing. A client who knows where to go when something wobbles is a client who stays calm and stays in touch.

Hand over numbers they can actually read

If you've improved anything, leave them able to measure it without you. That means a baseline, one simple dashboard, and a short paragraph explaining what 'good' looks like in six months. Not a forty-tab spreadsheet that nobody will open once you've gone.

Ask for the reference while it's still warm

The right moment to ask for a testimonial is roughly 72 hours after a good closing session — not six months later when the specifics have blurred. Ask for something particular, offer to draft it, and make it easy to say yes to.

Then ask the two questions most of us are too reserved to ask: who else might need this, and can I write it up as a case study? Both are far easier to answer on a high than in a cold email in March.

The twelve checks

  1. Handover pack written and sent
  2. Decision log included, with the reasoning
  3. 'What we didn't do' documented honestly
  4. Client-owned accounts transferred into client ownership
  5. Your own access revoked, with a written record
  6. Credentials rotated or reset
  7. Retention agreed and recorded
  8. Data deleted or archived as agreed, confirmed in writing
  9. Final invoice raised and receipt confirmed
  10. Metrics baseline and a simple dashboard handed over
  11. Testimonial and referral ask made, with a draft offered
  12. A 30-day check-in booked in the diary

The bit that isn't in the contract

Item twelve is the one that turns a finished project into the next one. A short call four weeks later, no agenda and no invoice, catches whatever has drifted — or surfaces whatever they now want next. It's fifteen minutes of your time and, by a distance, the highest-return item on this list.

Projects end. The relationship doesn't have to.

All Articles

Related Articles

Nobody Claps for Fixed Invoicing — and That's Exactly the Problem

Nobody Claps for Fixed Invoicing — and That's Exactly the Problem