# Convert capacity days with an explicit hours rule

Illustrative planning brief; no automatic product import.

Synthetic planning case: A draft allocates two availability days to a review. The agreed convention is five available review-hours per day, while the request needs twelve hours.

## Decision

Under this convention, two days provide ten review-hours and the request exceeds that by two. Retain the five-hour conversion rule with the plan.

## Owned work

- Recover the day convention
  - Owner role: Capacity owner
  - Acceptance evidence: An availability day means five review-hours in this plan.
- Convert before comparison
  - Owner role: Planner
  - Acceptance evidence: The two-day allocation is ten review-hours, not an assumed sixteen.
- Resolve the difference
  - Owner role: Review lead
  - Acceptance evidence: The two-hour gap is assigned a scope or capacity decision.

## Workflow

1. Recover the day convention. Check: An availability day means five review-hours in this plan.
2. Convert before comparison. Check: The two-day allocation is ten review-hours, not an assumed sixteen.
3. Resolve the difference. Check: The two-hour gap is assigned a scope or capacity decision.

## Judgment

A conversion rule does not prove actual effort or account for skill constraints. Preserve the original quantity and its convention.


## Filled manual planning note

Under this convention, two days provide ten review-hours and the request exceeds that by two. Retain the five-hour conversion rule with the plan. 2×5=10 available review-hours; 12−10=2 hours excess. An eight-hour day must not be substituted without changing the declared availability rule. A conversion rule does not prove actual effort or account for skill constraints. Preserve the original quantity and its convention.


## Workflow questions

### Does this define a company working day?

No. It is the supplied available-review-time convention for the example.

### Can calendar days be used as effort days?

Not automatically. Calendar duration, available time and actual effort are different quantities.

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

Planning input | Value | Convention
--- | --- | ---
Available days | 2 | Availability days, not calendar duration
Hours per availability day | 5 | Supplied local rule
Requested review work | 12 hours | Same review pool

### Reasoning

2×5=10 available review-hours; 12−10=2 hours excess. An eight-hour day must not be substituted without changing the declared availability rule.

### Bounded result

Under this convention, two days provide ten review-hours and the request exceeds that by two. Retain the five-hour conversion rule with the plan.

### Distinct decision

The artifact audits planning-unit conversion, separate from product display formatting or elapsed cycle-time clocks.

### Limits

A conversion rule does not prove actual effort or account for skill constraints. Preserve the original quantity and its convention.

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