Recover the day convention
Owner role · Capacity owner
Evidence: An availability day means five review-hours in this plan.
Capacity and availability / Delivery leads, planning owners and acceptance reviewers
Decision deskConvert capacity days with an explicit hours rule
Preserve the supplied availability convention when reconciling day and hour estimates.
The artifact audits planning-unit conversion, separate from product display formatting or elapsed cycle-time clocks.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Original worked case · Manual planning resource
Inspect the decision, not just the summary.
Start with the invented evidence, follow the reasoning, and retain its limits when adapting the brief.
01 · Inspect the inputs
Every record stays visible
| 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 |
Use horizontal scrolling for wide tables. These records are invented, not customer data.
02 · Follow the reasoning
How the case leads to a decision
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.
The 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.
Definitions and method context
Records, decisions and policies are original synthetic examples. External references supply context; they do not validate these cases or TeamBoostAI capabilities.
GAO Schedule Assessment Guide ↗
General schedule-model context. All records, local policies and arithmetic are original toy examples, not a certified or optimized schedule.
External references checked 6 October 2026. Demand for these topics has not been measured.
Decision desk
Decide before adding more work
Decision to make: 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.
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.
Convert before comparison
Owner role · Planner
Evidence: The two-day allocation is ten review-hours, not an assumed sixteen.
Resolve the difference
Owner role · Review lead
Evidence: The two-hour gap is assigned a scope or capacity decision.
Filled manual planning note
Invented planning text. Adapt it to your evidence and confirmed owners.
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.
Questions about this workflow
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.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
Put the outline to work
- Recover the day convention. Check: An availability day means five review-hours in this plan.
- Convert before comparison. Check: The two-day allocation is ten review-hours, not an assumed sixteen.
- Resolve the difference. Check: The two-hour gap is assigned a scope or capacity decision.
From a useful outline to team work
Explore TeamBoostAI for your team
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 the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.