# Compare queues only when their membership aligns

Illustrative planning brief; no automatic product import.

Synthetic planning case: An opening worksheet includes projects P and Q: A/P,B/P,C/Q,D/Q. The closing worksheet changes to P only: A/P,B/P,E/P. E is a newly arrived P request; the later state of Q is not observed.

## Decision

The raw view falls from four to three, but the aligned P cohort grows from two to three. Two excluded Q records explain the scope bridge; no accepted exit follows from the unmatched totals.

## Owned work

- Recover both view definitions
  - Owner role: Reporting owner
  - Acceptance evidence: The first worksheet covers P+Q and the second only P.
- Build the scope bridge
  - Owner role: Queue reviewer
  - Acceptance evidence: The comparable opening P set has two requests; two Q IDs are excluded.
- Interpret the aligned change
  - Owner role: Coordinator
  - Acceptance evidence: P grows by one arrival; the whole P+Q closing state is still unknown.

## Workflow

1. Recover both view definitions. Check: The first worksheet covers P+Q and the second only P.
2. Build the scope bridge. Check: The comparable opening P set has two requests; two Q IDs are excluded.
3. Interpret the aligned change. Check: P grows by one arrival; the whole P+Q closing state is still unknown.

## Judgment

The example assumes known P membership and E arrival. A changed view is not evidence of global service or record deletion.


## Filled manual planning note

The raw view falls from four to three, but the aligned P cohort grows from two to three. Two excluded Q records explain the scope bridge; no accepted exit follows from the unmatched totals. The old opening total 4 comprises 2 P plus 2 Q. Aligned P change=3−2=+1, while raw view change=3−4=−1. Later Q outcomes remain unknown, not silently completed or deleted. The example assumes known P membership and E arrival. A changed view is not evidence of global service or record deletion.


## Before / after

Before: Unmatched view totals 4 and 3 are interpreted as one serviced request.

After: Aligned P snapshots 2 and 3 show one arrival; later Q state is unknown.


## Workflow questions

### Did one request get reviewed because four became three?

No. The views use different scopes; the aligned P records show one arrival instead.

### Can Q records be called gone at the closing date?

No. Their later state was not observed in the P-only worksheet.

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

View or bridge | Included IDs | Count | Meaning
--- | --- | --- | ---
Opening P+Q | A,B,C,D | 4 | Old scope
Opening aligned to P | A,B | 2 | Comparable opening
Excluded opening Q | C,D | 2 | Outside new scope
Closing P | A,B,E | 3 | New P arrival E

### Reasoning

The old opening total 4 comprises 2 P plus 2 Q. Aligned P change=3−2=+1, while raw view change=3−4=−1. Later Q outcomes remain unknown, not silently completed or deleted.

### Bounded result

The raw view falls from four to three, but the aligned P cohort grows from two to three. Two excluded Q records explain the scope bridge; no accepted exit follows from the unmatched totals.

### Distinct decision

This bridges changed queue-view scope before comparing snapshots, rather than balancing transfers inside one unchanged queue.

### Limits

The example assumes known P membership and E arrival. A changed view is not evidence of global service or record deletion.

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