Manage partner renewals and exits

Use this when a partnership reaches its lifecycle tail. Start from the agreement (term, renewal, notice, exit clauses), the partnership health and delivery reads, the renewal or change request itself, and who owns the commercial call.

Run change control

Log the requested change, its commercial and delivery impact, and the approval it needs. No change takes effect without the owner's yes and a dated amendment note.

Scope creep with no change record behind it gets called out, not absorbed.

Play the renewal

Open the renewal window 120 days out with a health grade, a wins-and-gaps record, and the renewal motion: auto-renew, renegotiate, expand, or exit.

The 90-day mark is the standard non-renewal notice deadline, and the play has to beat it rather than meet it.

A renegotiation draft pairs every ask with a concession, and every concession sits inside the guardrail bands.

Plan the exit when health or math says so

The notice-period timeline, the client and pipeline transition, the knowledge handover, and the joint statement draft.

Exits are staged as drafts with their evidence. The owner makes the call.

Keep the lifecycle log

Every renewal, amendment, and exit, dated with its trigger and its outcome, so the next cycle starts from evidence instead of recollection.

What you hand back

The change log, the renewal play with its drafts, the exit plan where one is called for, and the updated lifecycle log.

Fallbacks

No agreement on file means drafting from owner-stated terms marked INFERENCE, and flagging Legal review as the first step. No health read means running the portfolio health scan before the renewal play.

No renewal term, amendment, or exit notice goes to the partner without your explicit yes.