# Compare batching when each run has setup work

Illustrative planning brief; no automatic product import.

Synthetic planning case: Six copy checks take twenty minutes each. Every review batch requires thirty minutes of setup. All six are available before one common deadline.

## Decision

One six-item batch uses 150 minutes; three two-item batches use 210. The sixty-minute setup saving is conditional on the common availability and deadline, not a universal batching recommendation.

## Owned work

- Confirm arrival and deadline conditions
  - Owner role: Work coordinator
  - Acceptance evidence: All six items are available before the same review cutoff.
- Charge setup per actual batch
  - Owner role: Reviewer
  - Acceptance evidence: One versus three setups explains the sixty-minute demand difference.
- Check waiting consequences
  - Owner role: Delivery lead
  - Acceptance evidence: The chosen batch still meets each required deadline and evidence boundary.

## Workflow

1. Confirm arrival and deadline conditions. Check: All six items are available before the same review cutoff.
2. Charge setup per actual batch. Check: One versus three setups explains the sixty-minute demand difference.
3. Check waiting consequences. Check: The chosen batch still meets each required deadline and evidence boundary.

## Judgment

The example does not measure quality, actual effort or respondent waiting. Its common-cutoff assumption is essential.


## Filled manual planning note

One six-item batch uses 150 minutes; three two-item batches use 210. The sixty-minute setup saving is conditional on the common availability and deadline, not a universal batching recommendation. Execution=6×20=120 minutes. Setup is 1×30 or 3×30; total demand is 150 or 210. Different arrival or due times can reverse which plan is feasible. The example does not measure quality, actual effort or respondent waiting. Its common-cutoff assumption is essential.


## Before / after

Before: Three batches require 210 stated minutes under the supplied setup rule.

After: One eligible common-cutoff batch requires 150 stated minutes, with waiting and quality still to review.


## Workflow questions

### Does the lower total mean batching is always faster for users?

No. Items may wait longer for a batch; this example compares staffing demand under a common cutoff.

### Can I claim a sixty-minute real saving?

Not from invented times. Verify actual setup and review evidence first.

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

Plan | Batches | Execution | Setup | Total
--- | --- | --- | --- | ---
One batch of six | 1 | 120 min | 30 min | 150 min
Three batches of two | 3 | 120 min | 90 min | 210 min

### Reasoning

Execution=6×20=120 minutes. Setup is 1×30 or 3×30; total demand is 150 or 210. Different arrival or due times can reverse which plan is feasible.

### Bounded result

One six-item batch uses 150 minutes; three two-item batches use 210. The sixty-minute setup saving is conditional on the common availability and deadline, not a universal batching recommendation.

### Distinct decision

The decision compares setup frequency and deadline feasibility rather than removing preparation from a work budget.

### Limits

The example does not measure quality, actual effort or respondent waiting. Its common-cutoff assumption is essential.

### Definitions and method context

- GAO Schedule Assessment Guide — https://www.gao.gov/products/gao-16-89g — General schedule-model context. All records, local policies and arithmetic are original toy examples, not a certified or optimized schedule.