# Review a client change against the current commitment

Illustrative planning brief; no automatic product import.

Illustrative request: a client adds a comparison view while a report delivery is already under review.

## Decision

Choose accept, reduce or defer the request and explain the affected delivery boundary.

## Owned work

- Clarify the requested change
  - Owner role: Client lead
  - Acceptance evidence: The smallest needed comparison and its purpose are confirmed.
- Assess displaced work
  - Owner role: Delivery owner
  - Acceptance evidence: The change’s effect on review, scope or timing is visible.
- Record the agreed tradeoff
  - Owner role: Commitment owner
  - Acceptance evidence: The accepted boundary and remaining exclusions are communicated.

## Workflow

1. Recover the current agreed scope before assessing the request.
2. Explain the concrete tradeoff, not a generic delay warning.
3. Record the authorized change and the next review point.

## Judgment

This guide coordinates delivery decisions; it does not interpret contract obligations or give commercial/legal advice.


## Illustrative delivery brief

Current commitment: accepted report boundary.
Requested change: one comparison view.
Tradeoff: identify the actual review/scope effect.
Decision: accept a bounded change, reduce it or defer with a reason.


## Workflow questions

### Does a client message change the plan automatically?

No. The responsible commitment owner needs to agree the revised boundary.

### Can we accept only part of the request?

Yes, when the reduced outcome and exclusions are explicit and agreed.

## Product connection

Document the agreed scope tradeoff before revising the delivery tasks your team tracks in TeamBoostAI.

Confirm account availability before adopting this manual outline.