Build a weekly capacity board, identify an overload and compare two feasible responses without hiding unmet work.
The fictional Rowan Team has three contributors. After routine duties and leave, available project capacity is Ada 12 hours, Ben 10 and Chen 8. Proposed assignments require Ada 16, Ben 8 and Chen 6. A 4-hour review task currently assigned to Ada can be performed by Ben or Chen after a 1-hour handover, counted against the receiver.
| Person | Available hours | Assigned hours |
|---|---|---|
| Ada | 12 | 16 |
| Ben | 10 | 8 |
| Chen | 8 | 6 |
Available capacity is the time realistically available for the planned work after known commitments. Keep leave, recurring duties and focused-work assumptions visible. An allocation plan is not a performance ranking. People with different availability can have equally important roles, and the plan should not conceal overtime as free capacity.
Create a capacity ledger explaining the available hours for each person and list two sources of uncertainty.
Weekly capacity baseline
Record your result and evidence here or in a separate file.
The board uses 12,10 and 8 available hours rather than a generic 40-hour assumption.
Separate total working time from the portion available to this project.
A resource plan needs a task-to-skill match as well as an hour total. A person may have spare capacity without the required context or authority. Record who can perform and review each task, and include transition effort. This makes the reason for an assignment reviewable instead of treating contributors as interchangeable hour buckets.
Create a skill and backup matrix for the movable review task. Include the 1-hour handover on the receiving side.
Skill-aware assignment map
Record your result and evidence here or in a separate file.
Both receiver options include the handover and an explicit review responsibility.
Add the context-transfer cost before declaring that a reassignment solves the overload.
Compare assigned work with available capacity for each person before looking at the team total. Here the team has 30 hours available and 30 assigned, yet Ada is 4 hours over. Aggregation hides this constraint. Capacity balance is a planning signal; it does not prove that an individual is working inefficiently.
Calculate load, spare or excess hours and utilization for all three people.
Capacity calculation sheet
Record your result and evidence here or in a separate file.
Ada is 4 hours over at 133.3%; Ben and Chen each have 2 spare hours.
Inspect person-level constraints when the team total appears balanced.
Moving the entire 4-hour task to either colleague also adds 1 hour of handover, exceeding that person’s 2 spare hours. A valid response may reduce scope, move the date, split work where technically possible or obtain approved additional capacity. State the operational consequence of each choice instead of assuming that delegation removes effort.
Compare deferring the 4-hour task with moving it to Ben and explicitly deferring 3 hours of Ben’s other work.
Two feasible response scenarios
Record your result and evidence here or in a separate file.
Both scenarios fit individual capacity and show the work or date that changes.
Do not hide the receiver’s 3-hour overload after including handover.
A capacity review should surface risks early and invite corrections to estimates. Ask about blocked work, unclear priorities and sustainable commitments. Track changes as planning decisions, not personal failures. A weekly review can compare actual and estimated effort to improve the next plan without using a small sample as a productivity league table.
Write a 15-minute review agenda and revise the board when Ada loses 2 available hours.
Capacity review and revised decision
Record your result and evidence here or in a separate file.
The revision shows the new shortfall and records a priority decision rather than invisible overtime.
Ask which commitment changes when capacity falls; do not keep every original promise.
Submit the baseline, skill matrix, calculations, two feasible alternatives and revised board. Explain the chosen trade-off in a short stakeholder note that does not blame the overloaded contributor.
Every scenario fits individual capacity or explicitly identifies an unresolved shortfall; no hidden overtime is assumed.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
Total demand equals total availability at 30 hours, but Ada has 16/12=133.3% utilization. Ben is 80% and Chen 75%. Moving the 4-hour task adds 1 hour to the receiver, so Ben becomes 13/10 or Chen 11/8. Reassignment alone does not solve the plan.
This is deterministic weekly planning, not an optimization engine or a measure of employee performance.