Hand over

Continuity Brief

A living context pack per engagement, so someone joining an account in week thirty reads the reasoning instead of excavating it.

Opens with the one dependency that matters most
Decisions with the reason beside them, not just the outcome
Stakeholder context, including how people prefer to work
Names where the record is thin, so you ask rather than assume

What it looks like

The real interface, on a sample engagement.

Hand over

Continuity brief — Acme Corp Expansion

Generated for an incoming engagement manager. Everything the record knows, in the order it matters.

Prepared for J. Okafor · covering 8 months · 14 decisions, 2 open commitments

Read this first

This engagement is commercially capped, not fixed-fee, and the reason matters: the cap was traded for a dedicated architect commitment that is still running and still unbilled. The same architect is the only person who can read the ERP mappings.

If you change one thing in your first fortnight, make it that dependency.

How we got here

14 Jan
Moved from fixed fee to capped T&M at $380k
ERP feed delay invalidated fixed milestones
11 Feb
Committed dedicated solution architect through Phase 2
Traded for client acceptance of the cap
2 Mar
Deferred KC and Memphis consolidation to Q1
Peak-season service risk
25 Aug
Key-person risk raised on ERP mapping
Single architect holds all mapping context

Still open

Architect coverage through Phase 2 — unbilled, no end date
Migration plan and cutover window — 2 days overdue

People, and how they work

Karen Liu — Sponsor
On medical leave. No delegated authority named; three decisions idle since August.
New CFO (April)
Was not party to the January pricing decision. Treats the cap as open.

Where the record is thin

Two areas have little in the record and are worth asking about directly rather than assuming: the procurement approval path since Dale left, and whether the Q1 deferral was ever confirmed in writing by the client COO.