# Purchase-to-Value Scope Check

Ruff Justice | Recreated educational template

Distinguish unused entitlement from a solvable adoption gap or a changed business plan.

## Original intent
What outcome, team, or deployment was the purchase intended to support?

[Your notes]

## Current use and value
Who uses the product now, and what do they get from it?

[Your notes]

## Unrealized scope
What has not been deployed or adopted?

[Your notes]

## Reason for the gap
Is this a learning need, technical dependency, timing issue, funding decision, or changed priority?

[Your notes]

## Customer-confirmed next step
What action is relevant now? Who on the customer side owns it?

[Your notes]

## Commercial coordination
Does the scope need review with the authorized commercial owner?

[Your notes]

## Review evidence
What observation would tell both sides the plan is working?

[Your notes]

## Use responsibly
Do not assume an oversized purchase means someone acted irresponsibly. Revisit the assumptions with the customer and account team without assigning blame.

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

## When to use it
Use when usage is below the purchased scope or when a planned rollout stalls.

## How to use it
1. Compare original purchase assumptions with the customer’s current needs.
2. Separate active value, delayed scope, and scope that is no longer relevant.
3. Agree on an adoption action or a commercial conversation based on the actual gap.

## Fictional worked example
one business unit is using the product, but a second rollout was postponed. The team confirms whether that second rollout is still funded before assigning a generic adoption campaign.

## Related case
The Oversold Deal