# Define the unit assigned in a work experiment

Illustrative planning brief; no automatic product import.

Synthetic planning case: A pilot assigns each of four teams to one work protocol. Each team then completes three task rehearsals. A recap calls the twelve task records twelve independently assigned experimental units.

## Decision

There are four assigned team units and twelve task observations in this design. Preserve their grouping; task count does not establish twelve independent assignments.

## Owned work

- Record the actual assignment unit
  - Owner role: Pilot owner
  - Acceptance evidence: The protocol was allocated to teams, not independently to each task.
- Preserve grouped observations
  - Owner role: Recorder
  - Acceptance evidence: Each task remains linked to its team exposure.
- Review analysis assumptions
  - Owner role: Method lead
  - Acceptance evidence: Any independence or effective-sample claim is justified separately; twelve rows alone are not twelve assignments.

## Workflow

1. Record the actual assignment unit. Check: The protocol was allocated to teams, not independently to each task.
2. Preserve grouped observations. Check: Each task remains linked to its team exposure.
3. Review analysis assumptions. Check: Any independence or effective-sample claim is justified separately; twelve rows alone are not twelve assignments.

## Judgment

This synthetic design supplies no statistical model or independent-sample guarantee.


## Filled manual planning note

There are four assigned team units and twelve task observations in this design. Preserve their grouping; task count does not establish twelve independent assignments. Four teams×three observations=12 records, but assignment occurred four times at team level. Within-team observations may share people and conditions. This synthetic design supplies no statistical model or independent-sample guarantee.


## Workflow questions

### Can all twelve observations still be retained?

Yes. Grouping and appropriate interpretation are the issue, not deleting useful records.

### Does team assignment prove randomness?

No. The actual assignment method also needs documentation.

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

Team | Assigned protocol | Task observations | Assignment unit
--- | --- | --- | ---
T1 | A | 3 | Team
T2 | A | 3 | Team
T3 | B | 3 | Team
T4 | B | 3 | Team

### Reasoning

Four teams×three observations=12 records, but assignment occurred four times at team level. Within-team observations may share people and conditions.

### Bounded result

There are four assigned team units and twelve task observations in this design. Preserve their grouping; task count does not establish twelve independent assignments.

### Distinct decision

The guide distinguishes the assignment unit from the number of observed task records.

### Limits

This synthetic design supplies no statistical model or independent-sample guarantee.

### Definitions and method context

- NIST combinatorial testing — https://www.nist.gov/publications/combinatorial-testing — Combination-coverage context. Invented review/state examples do not prove full fault coverage, certification or product behavior.