# Separate review attempts from accepted outcomes

Illustrative planning brief; no automatic product import.

Synthetic planning case: Proof A requires two review attempts, B one and C three before acceptance. Each attempt occupies thirty supplied review-minutes; each proof is accepted once.

## Decision

The period contains six review attempts and three accepted proofs, using 180 stated minutes. Keep workload and outcome counts separate.

## Owned work

- Preserve attempt histories
  - Owner role: Review recorder
  - Acceptance evidence: Each revision attempt remains linked to its proof identity.
- Reconcile service demand
  - Owner role: Capacity planner
  - Acceptance evidence: Six attempts consume 180 supplied minutes in this model.
- Label outcomes independently
  - Owner role: Reporting owner
  - Acceptance evidence: Three distinct accepted proofs are not reported as six deliveries.

## Workflow

1. Preserve attempt histories. Check: Each revision attempt remains linked to its proof identity.
2. Reconcile service demand. Check: Six attempts consume 180 supplied minutes in this model.
3. Label outcomes independently. Check: Three distinct accepted proofs are not reported as six deliveries.

## Judgment

Equal attempt duration is an invented assumption. Actual workload needs actual durations and meaningful review boundaries.


## Filled manual planning note

The period contains six review attempts and three accepted proofs, using 180 stated minutes. Keep workload and outcome counts separate. Attempts=2+1+3=6; accepted proofs=1+1+1=3. At thirty minutes per attempt, total demand=6×30=180 minutes, not 3×30. Equal attempt duration is an invented assumption. Actual workload needs actual durations and meaningful review boundaries.


## Workflow questions

### Are unsuccessful attempts automatically wasted work?

No. They may reveal required corrections; this ledger records workload rather than judging value.

### Can attempt counts compare reviewers fairly?

Not alone. Scope, difficulty, criteria and quality differ and need context.

## Product connection

Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product.

Confirm account availability before adopting this manual outline.

## Original worked case

Synthetic records, manual planning only. No account import or live analytics.

### Inspect the invented case records

Proof | Attempts | Accepted outcomes | Review-minutes
--- | --- | --- | ---
A | 2 | 1 | 60
B | 1 | 1 | 30
C | 3 | 1 | 90

### Reasoning

Attempts=2+1+3=6; accepted proofs=1+1+1=3. At thirty minutes per attempt, total demand=6×30=180 minutes, not 3×30.

### Bounded result

The period contains six review attempts and three accepted proofs, using 180 stated minutes. Keep workload and outcome counts separate.

### Distinct decision

The decision reconciles repeated review service with distinct accepted outcomes.

### Limits

Equal attempt duration is an invented assumption. Actual workload needs actual durations and meaningful review boundaries.

### Definitions and method context

- The Kanban Guide — https://kanbanguides.org/the-kanban-guide/ — Workflow and flow-measure context. Queue policies and staffing scenarios are explicitly local examples, not delivery guarantees.