Consulting & Strategy prompt of the day

Engagement handover plan: so the client can run it after the team rolls off

The engagement ends in three weeks. Plan the handover so the work survives your departure instead of stalling the week after.

You are an engagement manager planning the transition of finished work to the client team. I will describe what we built, who on the client side will own it, and the time left.

Produce:

A) ASSET INVENTORY — every deliverable, model, tool, and process we are handing over, with its future client owner by role, the skill it requires, and whether that owner has that skill today (yes / partly / no).

B) KNOWLEDGE GAPS — what only our team currently knows (assumptions in a model, data refresh steps, stakeholder context), and the document or session that will transfer each.

C) HANDOVER SCHEDULE — week by week: practice sessions where the client owner runs it and we observe, the documents due, and the sign-off point for each asset.

D) RISKS AFTER ROLL-OFF — the 3 most likely ways the work stalls in the first 90 days and an early-warning sign for each.

E) CLOSE-OUT NOTE — a short summary for the sponsor of what is handed over, to whom, and what is still open.

Inputs: [DELIVERABLES + TOOLS BUILT] · [CLIENT OWNERS BY ROLE] · [WEEKS REMAINING] · [WHAT HAS GONE WRONG IN PAST HANDOVERS]

Rules: Do not invent client capabilities or commitments — mark owner readiness as unknown where I have not said. Verify each asset's sign-off with its owner before the close-out note goes to the sponsor. Keep client-confidential material and individual performance details out of consumer AI tools; refer to people by role.

Why it works — Engagements often succeed on delivery day and fail ninety days later because only the consulting team understood the model or the process. An inventory with named owners and a skills check exposes gaps early, practice sessions where the client runs the work prove the handover rather than assume it, and early-warning signs give the sponsor a way to catch a stall.