Identify the shared pool
Owner role · Capacity owner
Evidence: Both project allocations point to the same 24-hour availability record.
Capacity and availability / Delivery leads, planning owners and acceptance reviewers
Task boardShared capacity counted twice across projects
Reconcile a single resource pool before accepting two project allocations.
This audits duplicate use of one availability pool across project allocations; it is not merely a sprint availability checklist.
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
| Capacity or request | Person-hours | Scope |
|---|---|---|
| Shared pool | 24 | One pool |
| North request | 16 | Uses shared pool |
| South request | 12 | Uses the same 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
16+12=28 requested; 28−24=4 uncovered person-hours. Adding the same 24-hour pool to each project does not create 48 hours.
The bounded result
The combined request is 28 person-hours against one 24-hour pool. Resolve the four-hour over-allocation before accepting both project plans.
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.
Turn the situation into owned work
Illustrative task boardSynthetic planning case: A shared editing pool has 24 person-hours available this week. Project North requests 16 and South requests 12; both project plans describe the full pool as theirs.
Reconcile combined demand
Owner role · Planning lead
Evidence: The combined 28-hour request and four-hour excess are visible.
Agree the displacement
Owner role · Project owners
Evidence: A named request is reduced, moved or supplied by separately confirmed capacity.
Decision to make: The combined request is 28 person-hours against one 24-hour pool. Resolve the four-hour over-allocation before accepting both project plans.
Filled manual planning note
Invented planning text. Adapt it to your evidence and confirmed owners.
The combined request is 28 person-hours against one 24-hour pool. Resolve the four-hour over-allocation before accepting both project plans. 16+12=28 requested; 28−24=4 uncovered person-hours. Adding the same 24-hour pool to each project does not create 48 hours. Availability and demand are supplied planning inputs, not measured productivity. A different skill or calendar constraint may still block a feasible total.
Put the outline to work
- Identify the shared pool. Check: Both project allocations point to the same 24-hour availability record.
- Reconcile combined demand. Check: The combined 28-hour request and four-hour excess are visible.
- Agree the displacement. Check: A named request is reduced, moved or supplied by separately confirmed capacity.
Questions about this workflow
Can each project pass its own capacity check?
Yes, each request is below 24; the shared-pool check still fails when requests are combined.
Does the four-hour gap imply overtime?
No. Additional availability requires a separate agreement; the ledger does not authorize it.
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.
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.