Present findings and hand over
26 primitives in this stage — 24 skills · 2 agents. Concept-stage catalogue, kept vendor-agnostic.
Watch the transition window and flag emerging gaps →
“I want to know if something's quietly going wrong before they tell me it went wrong.”
Run access revocation and retention/deletion checklist →
“The engagement is closed. I need to make sure we're not sitting on open access or holding data we shouldn't.”
Design the narrative spine and section order →
“The sections are all done — but they're not a story yet. I need someone to tell me what comes first.”
Write the executive summary / key-message slide →
“The partner wants to read this in two minutes on the train. I need one page that actually lands the message.”
Copyedit and proofread for language and tone →
“The analysis is solid but the writing is patchy — three different people, three different styles. I need it to sound like one firm.”
Decide what belongs in the appendix vs working files →
“I have thirty tabs of workings. Some of it should go in the pack. Most of it shouldn't. I need a principled cut.”
Review the package against the brief and expectations →
“I'm too close to this. I need a fresh read that asks whether we've actually answered what they hired us to answer.”
Stress-test the key numbers and claims →
“I need to be able to defend every number in the room. I don't want to find a discrepancy when the CFO asks.”
Prepare the partner sign-off brief →
“The partner has thirty minutes. I need a brief that tells them exactly what's changed and what they're approving — not a deck to re-read.”
Anticipate the room and rehearse the narrative →
“I know the material. I don't know which way the room will go. I want to have thought through the hard moments before they happen.”
Frame the objection response →
“They pushed back hard on the central recommendation. I need to respond without either caving or losing the room.”
Decide concede, hold, or escalate →
“I need to know in the moment whether I'm defending a position that should be defended or one I should let go.”
Classify and bound the change requests →
“The feedback capture from that session is a mess — half of it isn't about the deliverable. I need to know what we're actually committed to changing.”
Apply the agreed changes to the deliverable →
“I have a clean list of what to change. I need to work through it without accidentally reopening things we agreed not to revisit.”
Draft the acceptance request and conditions →
“I need them to formally say yes — not just a nodding emoji on email. This needs to be documented and unambiguous.”
Build the handover session walkthrough plan →
“I want them to walk out of that session able to run it themselves — not dependent on calling us back for basics.”
Capture and resolve open questions from the session →
“Questions came up I wasn't expecting. I need to make sure none of them fall through the cracks after the session ends.”
Draft the operating guide and decision log →
“Six months from now, they'll be running this without us. The operating guide is the thing that means they don't need to call.”
Build the asset and access transfer checklist →
“The last thing I want is a call three weeks later saying they can't access something we forgot to hand over.”
Resolve an incoming transition-period query →
“They've got a question and I want to turn it around fast — and know whether it means something was missed.”
Draft the final invoice from deliverables and budget →
“The work is done. I need the invoice to reflect exactly what we delivered, clearly enough that no one argues it.”
Check SoW commitments against delivered artefacts →
“Before I close this out, I want a clear line of sight from every SoW commitment to the thing we actually delivered.”
Draft the completion sign-off request →
“I need them to formally close this. Not a handshake — a document that says it's done.”
Prepare the retrospective facilitation pack →
“I want this retro to actually produce something useful. That means doing the prep, not winging it in the room.”
Synthesise raw retro notes into a structured record →
“We had a good conversation. I need it turned into something we'll actually act on and remember next time.”
Organise materials into an archive manifest →
“In two years, someone will want to find a number from this project. I need the archive to make that possible in under five minutes.”