# A weekly project summary that supports choices

Illustrative planning brief; no automatic product import.

Illustrative week: intake routing was accepted, an admin view moved out of scope, and the next delivery depends on a support walkthrough.

## Decision

Keep the next commitment conditional on the support walkthrough, with a named owner and review point.

## Owned work

- Delivered outcome
  - Owner role: Project manager
  - Acceptance evidence: The summary links acceptance evidence for intake routing.
- Changed commitment
  - Owner role: Product owner
  - Acceptance evidence: The admin-view deferral is stated with its scope or capacity reason.
- Next decision
  - Owner role: Support lead
  - Acceptance evidence: The walkthrough owner and the condition for starting the next delivery are recorded.

## Workflow

1. Summarize outcomes accepted this week and link the underlying evidence.
2. Explain material scope or date changes and their consequences.
3. Close with the decisions stakeholders need to make and the next review point.

## Judgment

Do not represent a task count or a green status label as proof of business impact.


## Illustrative weekly project summary

Accepted this week: intake routing, with acceptance evidence linked from its task.
Changed scope: the admin view is deferred to keep the first delivery bounded.
Next dependency: support must complete its workflow walkthrough before the next commitment is chosen.
Decision needed: support lead confirms the walkthrough owner and reports any missing operating instructions.
Next review: revisit the delivery boundary after that walkthrough, rather than treating the next phase as already committed.


## Workflow questions

### Should we include a completion percentage?

Only when its denominator and interpretation are meaningful. A percentage of mixed-size tasks can hide the delivery outcome.

### How long should the summary be?

Long enough to explain material changes and decisions. Use references for detail instead of recreating the entire task board.

## Product connection

Prepare an evidence-led weekly summary alongside TeamBoostAI reporting assistance; check the result against actual task records.

Confirm account availability before adopting this manual outline.