# Champion Continuity Map

Ruff Justice | Recreated educational template

Keep important customer workflows and relationships from depending on one person.

## Customer outcome
What useful result needs to continue?

[Your notes]

## Critical workflow
What dashboard, report, process, or decision supports that result?

[Your notes]

## Current coverage
Who operates it, who benefits, and who can approve changes? Use role names in shared copies.

[Your notes]

## Continuity gap
What knowledge or access would disappear if the primary contact left?

[Your notes]

## Successor enablement
What does the next owner need to learn, see, or practice?

[Your notes]

## Action and owner
Who will do what, and by when? Include your technical partner where appropriate.

[Your notes]

## Evidence and review
How will the customer demonstrate that the workflow can continue? When will you check?

[Your notes]

## Use responsibly
More contacts do not automatically mean stronger coverage. Confirm that each relationship has a relevant purpose and respect the customer’s preferred coordination.

Newly created for Ruff Justice. Not a former-employer document. Keep confidential information out of shared copies.

## When to use it
Use when a champion changes roles, leaves, or becomes unavailable, or as a proactive account-planning exercise.

## How to use it
1. Start with the work the customer needs to continue, not just contact names.
2. Identify who owns, performs, and benefits from each workflow. Ask the customer to validate the map.
3. Agree on knowledge-transfer and enablement actions, then check whether the successor can use the workflow.

## Fictional worked example
a replacement operations lead needs to use an existing weekly capacity report. The technical partner runs a working session; the customer lead then walks through the report independently. Review with the sponsor after that handoff.

## Related case
The Ghost Champion