# Budget paired work in person-hours

Illustrative planning brief; no automatic product import.

Synthetic planning case: A troubleshooting rehearsal needs two participants together for three elapsed hours. The staffing plan reserves three person-hours in total.

## Decision

Reserve six person-hours for the three-hour pair session, and separately verify that both people share the full window.

## Owned work

- Define required participation
  - Owner role: Rehearsal owner
  - Acceptance evidence: Both roles must attend the full three-hour session.
- Charge each availability ledger
  - Owner role: Coordinator
  - Acceptance evidence: Three hours are reserved for each participant, six person-hours combined.
- Verify the joint booking
  - Owner role: Participants
  - Acceptance evidence: Both confirm the same full window before the rehearsal is committed.

## Workflow

1. Define required participation. Check: Both roles must attend the full three-hour session.
2. Charge each availability ledger. Check: Three hours are reserved for each participant, six person-hours combined.
3. Verify the joint booking. Check: Both confirm the same full window before the rehearsal is committed.

## Judgment

Person-hours measure staffing demand under this protocol, not a productivity score or a promise that pairing is faster.


## Filled manual planning note

Reserve six person-hours for the three-hour pair session, and separately verify that both people share the full window. Two participants×three hours=6 person-hours. The session still occupies three elapsed hours, not six elapsed hours. Person-hours measure staffing demand under this protocol, not a productivity score or a promise that pairing is faster.


## Workflow questions

### Does pairing halve the work duration?

Nothing in these records proves a speed effect. They only describe the required joint session.

### Can six person-hours guarantee a usable joint slot?

No. Separate calendar availability must overlap for the full three hours.

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

Participant | Joint elapsed window | Staffing demand
--- | --- | ---
Facilitator | 3 hours | 3 person-hours
Operator | 3 hours | 3 person-hours
Pair total | 3 elapsed hours | 6 person-hours

### Reasoning

Two participants×three hours=6 person-hours. The session still occupies three elapsed hours, not six elapsed hours.

### Bounded result

Reserve six person-hours for the three-hour pair session, and separately verify that both people share the full window.

### Distinct decision

The guide reconciles paired elapsed time with resource consumption; it does not recommend pairing as a universal technique.

### Limits

Person-hours measure staffing demand under this protocol, not a productivity score or a promise that pairing is faster.

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