Assure partner-led delivery

Use this when partners deliver client work in your name. Start from the in-flight engagement book (partner, client, scope, dates, staffing), the delivery status per engagement, the escalation history, and the client success criteria.

Own the book

One row per engagement: partner, client, scope, milestone dates, the staffed team, and a red/yellow/green delivery grade with one line of evidence behind it. A grade with no evidence stays UNKNOWN.

The book is rebuilt weekly from the tracker, never from memory.

Run the weekly delivery review

Most-at-risk first, one decision per engagement: on track, needs support, restaff, or escalate.

Before any escalation, build the peer map — functional peers with equal decision authority on both sides — and escalate peer-to-peer first.

A staffing gap gets a dated restaff line with an owner. Anything red two weeks running gets an executive escalation draft.

Rescue at-risk engagements

Name the failure mode — staffing, skill, scope, or client-side — pick one save motion with a date, and log it.

A third straight red week triggers the save-or-exit call with its evidence attached.

Close the loop quarterly

A per-partner delivery-quality read: on-time rate, escalation count, client satisfaction. It feeds the portfolio review and the renewal call, so delivery shows up in the commercial decision rather than beside it.

What you hand back

The graded engagement book, the weekly review log with its decisions, the active rescue plans, and the quarterly delivery-quality read.

Fallbacks

No tracker means building the book from owner-pasted status notes marked INFERENCE, with standing up the tracker as the first action. No success criteria means drafting them from scope and confirming with the owner.

No staffing change, escalation, or client-facing message goes out without your explicit yes.