# Explain work status with a reason and next check

Illustrative planning brief; no automatic product import.

Illustrative board: one task awaits a product rule, another awaits acceptance review, and a third is paused because its outcome is no longer in scope.

## Decision

Give each state a next owner action instead of grouping all three tasks under “in progress.”

## Owned work

- Waiting for clarification
  - Owner role: Product owner
  - Acceptance evidence: The status names the unresolved rule and the task step it blocks.
- Waiting for acceptance
  - Owner role: Reviewer
  - Acceptance evidence: The status links ready evidence and requests a review decision.
- Paused after scope change
  - Owner role: Project lead
  - Acceptance evidence: The status records the deferral reason and the condition for reconsidering the task.

## Workflow

1. Choose the state that describes the current work condition.
2. Add the specific reason and the role responsible for the next action.
3. Update the reason when the condition changes or at the agreed review point.

## Judgment

These example states are planning concepts, not a verified list of configurable TeamBoostAI status values.


## Filled illustrative decision

In the illustrative update, the date-filter task awaits a product rule, the export task awaits acceptance evidence, and the portal task is deferred out of scope. Each line names a different next action. Reporting all three as in progress would conceal which decisions can actually move the work forward.


## Workflow questions

### Should every status have a long explanation?

No. A short reason is enough when it names the condition and next action. Link detailed evidence where needed.

### Does “waiting” mean poor performance?

No. It can reflect an external decision, review queue or dependency. Assess the work condition rather than inferring individual effort.

## Product connection

Explain why a TeamBoostAI task’s status changed and what the next owner needs, rather than using the label as an effort score.

Confirm account availability before adopting this manual outline.