TASK THROUGHPUT
Check whether a shared goal fits the sessions you can actually protect
This calculator turns four task inventories into demand and compares that demand with usable work sessions. Blocked days and protected buffer reduce calendar availability before throughput is evaluated. It supports a capacity decision, not a promise that dependencies or uncertain tasks will cooperate.
| Layer | Basis | Rate | Total | Unit |
|---|
Detailed calculation process
Formula, declared symbols, substitutions, intermediate results, and reconciliation
D = R + B + A + V; S = min(Ws, 7W − d − b); M = Sq − D
Demand is the sum of independently inventoried tasks. Usable sessions are capped by both planned cadence and remaining civil days; capacity margin is throughput capacity minus demand.
| Symbol | Meaning | Unit / default |
|---|---|---|
| R, B, A, V | review, build, administration, and verification demand | 12, 28, 8, 10 tasks |
| W, s | planning weeks and nominal sessions each week | 8 weeks; 3 sessions/week |
| d, b | blocked civil days and protected buffer days | 6 and 5 days |
| q, M | accepted tasks per session and final task margin | 3 tasks/session; tasks |
- Total demand D=12+28+8+10=58 tasks.
- Nominal sessions Snom=8×3=24.
- Usable civil days Sday=8×7−6−5=45 days.
- Controlling sessions S=min(24,45)=24 sessions.
- Throughput capacity=24×3=72 tasks.
- Final reconciliation M=72−58=14 tasks; 58 demand plus 14 margin returns the 72-task capacity.
Six-step schedule check
- Write a done rule for each task.
- Inventory research separately from production.
- Reserve administration and review work.
- Remove known blocked civil days.
- Protect a buffer before claiming capacity.
- Compare required pace with demonstrated pace.
Five schedule foundations
Demand
All unfinished tasks in scope.
Nominal session
A planned work appointment.
Usable day
A civil day left after deductions.
Throughput
Average tasks completed per session.
Margin
Capacity minus demand.
Deep dives
Task size drift
If “task” ranges from a phone call to a week of work, throughput is meaningless.
Dependency risk
Enough sessions cannot fix a predecessor that arrives late.
Buffer ownership
Protected days should absorb surprises, not become pre-booked production days.
Evidence
Use a dated backlog, calendar blocks, and completion history from similarly sized tasks. Positive margin indicates arithmetic headroom; zero means no buffer; negative margin requires a change before commitment.
Limits
- No task order or critical path.
- One average throughput for all sessions.
- Blocked days are exact user entries.
- No skill-specific ownership.
- No guarantee that nominal sessions occur.
Glossary
- Backlog
- Frozen list of unfinished tasks.
- Buffer day
- Day intentionally left uncommitted.
- Capacity
- Sessions times tasks per session.
- Critical path
- Dependency chain controlling finish date.
- Scope
- Work included in the goal.
- Throughput variance
- Change in completed tasks per session.
Cases
Community event: review tasks push demand above capacity, so the pair reduces features.
Apartment move: ample margin remains, but a landlord approval dependency still needs a dated owner.
Important note
A positive margin does not prove the deadline is safe when a task is uncertain, externally controlled, or sequential.
Result interpretation
Positive capacity does not prove the sequence is feasible
The default 14-task margin says the declared sessions can process the inventory at the average rate. It does not reserve the right task in the right week. Inspect the ledger by class: if verification cannot begin until build work finishes, preserve its sessions late in the horizon rather than spending the whole margin early.
Decision and sensitivity
Separate rate risk from calendar risk
One additional session per week raises nominal capacity by 8×3=24 tasks, while one extra blocked day changes nothing until usable days fall below nominal sessions. A rate decline from three to 2.5 tasks per session reduces capacity to 60 and margin to only two tasks, making throughput evidence the governing sensitivity in the default case.
Questions
Why separate task classes?
They reveal which work definition changed instead of hiding all demand in one total. Review, build, administration, and verification can have different owners and completion rules.
Do blocked days automatically remove sessions?
They constrain usable civil days; the smaller of usable days and nominal sessions controls. Enter only days that genuinely prevent a planned session.
Can capacity be fractional?
Tasks per session may be fractional as a long-run average. For a short plan, round only after inspecting whether the final partial task can actually be completed.
What does a negative margin mean?
Demand exceeds arithmetic throughput under the entered assumptions. It does not identify which task should be removed or who should work more.
Does the tool schedule task order?
No. It tests aggregate capacity, not dependencies or critical paths. A positive task margin can coexist with an impossible sequence.
When is a project tool better?
Use one when tasks have owners, prerequisites, fixed appointments, or scarce resources. Those constraints cannot be represented by a sessions-times-rate total.
Why keep buffer days separate from blocked days?
Blocked days are already unavailable; buffer days are deliberately held back for uncertainty. Combining them prevents you from seeing how much contingency remains.
What if tasks have very different sizes?
Replace the task count with weighted work units or split the schedule by class. A single tasks-per-session rate is meaningful only for a reasonably stable task definition.
Can unused sessions carry into the next week?
The total model allows unused capacity anywhere in the horizon, but it does not prove that work can be shifted across weeks. Fixed-date tasks need a dated schedule.
How should completed work be treated?
Remove accepted completed tasks from the demand inventory and retain the dated baseline. Do not increase throughput merely because prior work is already done.