# Make stakeholder approval a reviewable checkpoint

Illustrative planning brief; no automatic product import.

Illustrative checkpoint: a sponsor likes a demonstration but has not decided whether the proposed exclusions are acceptable.

## Decision

Ask for explicit acceptance or changes against the scoped outcome and exclusions.

## Owned work

- State the decision
  - Owner role: Project lead
  - Acceptance evidence: The request asks approval of a named outcome and its exclusions.
- Provide evidence
  - Owner role: Reviewer
  - Acceptance evidence: The demonstration or review evidence supports that decision.
- Record the response
  - Owner role: Sponsor
  - Acceptance evidence: Acceptance, changes or a missing condition is documented clearly.

## Workflow

1. Name the outcome and exclusions the sponsor is being asked to approve.
2. Provide the reviewed demonstration and identify any acceptance condition that the demonstration did not exercise.
3. Record accept, changes requested or conditional acceptance; attach an owner and closing evidence to each condition.

## Judgment

A positive comment or meeting attendance does not automatically approve scope, spending or publication.


## Filled illustrative planning example

Synthetic request: accept a report-label correction, excluding historical data restatement. The sponsor accepts the display change but asks for a note explaining the exclusion. Acceptance remains conditional until that note is reviewed.


## Workflow questions

### What if the sponsor says “looks good”?

Clarify which outcome and exclusions were accepted before treating that as a complete decision.

### Can approval be conditional?

Yes. Record the condition, its owner and the evidence needed to satisfy it.

## Product connection

Use the manual work brief to discuss task ownership, review evidence and next actions in TeamBoost. Release execution remains a separate project workflow; the download performs no deployment or import.

Confirm account availability before adopting this manual outline.