# Update team guidance after a workflow changes

Illustrative planning brief; no automatic product import.

Illustrative change: a report review now requires a timezone check, but the operating note still describes the old acceptance steps.

## Decision

Revise the affected guidance and have a receiver validate the new review path.

## Owned work

- Identify the changed behavior
  - Owner role: Process owner
  - Acceptance evidence: The new review condition and affected guidance are explicit.
- Revise the bounded note
  - Owner role: Documentation owner
  - Acceptance evidence: The note explains the current path and retires conflicting instructions.
- Check receiver usability
  - Owner role: Team reviewer
  - Acceptance evidence: A teammate follows the revised note and reports missing context.

## Workflow

1. Locate the operating note that still omits the timezone acceptance check.
2. Replace the conflicting step with the current check, its evidence and the responsible reviewer; preserve the superseded revision as history.
3. Ask a receiving teammate to follow the revised note on a synthetic report and identify any remaining ambiguity.

## Judgment

Do not copy credentials or private account examples into team documentation.


## Filled illustrative planning example

Synthetic note revision: verify the displayed timezone against the report period before requesting acceptance. Receiver trial: a teammate follows the note and identifies the timezone reviewer. The old instruction is retained as history, not a competing current procedure.


## Working artifact

- Process owner / The timezone check and acceptance reviewer in the current operating note. / Confirms the new condition matches the actual workflow.
- Documentation owner / Revised instruction and superseded revision reference. / Confirms conflicting current instructions are retired.
- Receiving teammate / Synthetic report used to follow the revised path. / Reports missing context before the note is accepted.


## Workflow questions

### Should we rewrite the whole handbook?

Only when that solves the current behavior gap; a focused update is often enough.

### How do we know the note is useful?

A receiving teammate can follow the intended workflow and identify its review owner.

## 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.