Work Demand calculator

Team Capacity Cost Calculator

What Are Rework and Extra Time Costing This Team?

Use this team capacity cost calculator to estimate how much paid time is being consumed by rework, avoidable meetings, repeated review, chasing, and context rebuilding. Emergent Skills calls this directly traceable extra labor the visible floor of execution drag. The calculator does not diagnose what causes the pattern. It reports the share of salary already being spent on the extra time you enter. Elapsed delay and any effect on access to skill sit above that floor and are not measured here. If one priority is stuck, an optional line models the value it defers, kept separate from the floor. Three inputs produce a directional planning scenario, not a measured result.

Two minutes. Your assumptions. Built for the COO, CFO, Chief of Staff, and the operators responsible for delayed priorities.

The scenario

Estimate the cost of rework and extra labor on one team

The result uses your team size, loaded annual cost, and directly traceable extra hours. Change an assumption and the scenario changes with it.

Three inputs

Team size

Count the people whose output is judgment, analysis, or decisions. Not total headcount.


Use the loaded figure your finance team uses. If none is available, enter a documented planning estimate that includes pay, benefits, payroll taxes, and overhead.

Count only time reasonably attributable to chasing, repeated review, avoidable meetings, rework, or context rebuilding. Exclude elapsed waiting, productive work, and speculative missed value.

1 hr

  
Use a number you can defend. One hour is a round starting unit, not a benchmark and not a measured rate. Move the slider to the amount this team can reasonably reconstruct from actual work.
How to reconstruct this number from one real week

Take one person on this team and their last five working days. Add up the time that went to:

  • meetings that could have been a message, or that ended without a decision
  • work redone after a late change to scope, inputs, or ownership
  • a review or approval that went around more than once
  • chasing a reply, an owner, or a missing input (the chasing itself, not the waiting)
  • rebuilding context after a handoff or an interruption

Divide the total by five. That is the number for the slider. If it lands well above one hour, that is common and the scenario scales with it. If it lands below, use the lower figure. Either way it is a number the team can show its work on, which is what a CFO will ask for.

Calculation assumptions (adjust if yours differ)
Working days the team is actually in the work, after holidays and average time off.
Actual hours worked in a typical day. For salaried people carrying judgment work, this is often 9 to 10 rather than the contracted 8.

 

The hourly rate divides loaded annual cost by the hours actually worked, because this page apportions salary that has already been spent. A shorter costing convention such as 1,800 hours prices an incremental hour you might buy, which is a different question. Using it here would charge the extra time at a rate above what was actually paid for it, and the share of the day would stop reconciling to the share of payroll.

The directional estimate

Annual loaded cost of the extra time entered $0   Salary already in the payroll line, not a new cost and not recoverable cash.

The same team at three time assumptions The extra hours entered is the only soft input on this page, so the honest range is what happens when that one number moves. These are not a confidence interval.

30 minutes per person per day$0
1 hour per person per day$0
2 hours per person per day$0
Challenge the time assumption first. The extra hours entered above are the assumption this whole figure rests on, and the first thing a CFO should push on. Everything else here is arithmetic.
Team extra time per working day 0 Hours across the whole team, per working day.
Loaded cost of extra time per working day $0 Annual scenario divided by operating days.
Loaded cost per hour $0  
 

Optional, and starts at zero. Model a reduction in the extra hours per person per day, not a return on an investment.

0%

Move the slider to model a reduction. A reduction returns capacity, not new cash hours automatically. What happens to that capacity is a business decision: faster delivery, more output, lower overtime, better quality, or a smaller future cost base. An open calendar is not yet profit.

Value deferred while a priority stays stalled Optional, and starts empty. If a specific priority sits behind this team's extra time, enter the annual value its business case assigns to it. This models deferred value on its own line. It is never added to the floor above.



Enter an annual value to model what each week of delay defers. Deferred, not lost, and not a cash figure. Whether it is recovered depends on whether the window is still open when the work resumes: the market, the budget cycle, the sponsor's attention. Calendar weeks are used because delay is elapsed time, not working time. The value is yours; this page only divides it.
What this does and does not count. Included: only the extra time entered above, valued at the loaded cost of an hour actually worked. This is the visible drag floor. Excluded from the floor: elapsed delay, opportunity value, sustained overload and attrition exposure, and any effect on judgment, focus, communication, creativity, or work quality. Those sit above the floor and require separate evidence. If you entered an annual value for a stalled priority, its deferred value is reported on its own line above and is never added to the floor. This is a planning scenario, not a measured outcome or a forecast of cash savings.

The calculator estimates a direct-labor scenario. It cannot locate the pattern or test the capacity effect.
The Stalled Priority Snapshot reconstructs one live work path with up to three people who move, approve, or unblock it. In 90 minutes it separates hands-on work from waiting, estimates directly traceable extra labor, reports elapsed delay separately, and defines one 14-day routing experiment with an owner, a metric, a target, and a decision rule. A one-page readout follows within 24 hours. $1,500 flat.

Book a Stalled Priority Snapshot Or start with the Work Demand Diagnostic

Snapshot: local routing hypothesis. Diagnostic: shared pattern. Audit: measurement across flows and roles. Pilot: reversibility.
The Snapshot fee credits toward the Diagnostic if booked within 30 days. On-site available in the NY/NJ metro.

 

Use the estimate to investigate what is slowing the work

This calculator estimates the loaded cost of directly traceable extra time. It does not show whether rework, repeated review, avoidable meetings, or another work-demand condition is responsible. The Snapshot tests one local work path. The Diagnostic examines whether the pattern is shared. The Audit measures across multiple flows and roles and builds the economic model. The Pilot tests whether changing the conditions improves an agreed operational-efficiency metric. Each stage earns, redirects, or stops the next.

Book a Stalled Priority Snapshot

Founder-led engagements. Snapshot: 90 minutes, $1,500, credits toward the Diagnostic.

Team Capacity Cost Calculator method note: annual loaded-cost scenario = team size × direct extra hours per person per day × operating days per year × loaded hourly cost, where loaded hourly cost = fully loaded annual cost ÷ (operating days × operating hours in a working day). Dividing by hours actually worked is what makes the share of the day and the share of payroll reconcile to the same figure. The output is directional planning math based entirely on user-entered assumptions, not a benchmark, a diagnosis, a measured outcome, or a forecast of cash savings. It is the visible drag floor. Elapsed delay, opportunity value, sustained overload exposure, and any effect on access to skill are excluded and require separate evidence. The optional deferred-value line divides the annual value entered for a stalled priority by 52 calendar weeks, multiplies by weeks stalled when entered, and reports the result separately. It is never added to the floor. Part of Emergent Skills, Performance Infrastructure for Demanding Knowledge Work.