Capacity · Measurement
Measure what the hours did
Three checks, in order. Each one depends on the one before it.
- Hours released
- Output completed
- Quality accepted
- Demand served
- Margin realized
Separate example. The numbers below use one weekly client report. Each check ends with how to apply it to the setup examples.
What changed?
Did the defined work improve, or did the measurement simply change? Time the same work before and after, with review and fixes inside both numbers.
30 minsaved per report
90 − 60 minutes, on the same kind of report.
× 20 reportsa week
Multiply only by comparable tasks completed. Other kinds of work do not inherit this saving.
= 10 h released600 min a week
Hours released are the starting point. They gain value once the team applies them to useful work.
What keeps the comparison fair
Same defined taskBefore and after match
If the task got simpler or the standard got lower, the time difference says little about the routine.
Enough real examplesOver the same kind of period
One quick week or one unusually easy report can mislead you. Log enough cases on each side to compare like with like.
Everything includedReview, fixes and upkeep
For the setup examples, time one real task from start to approved finish, with review, fixes and upkeep included. Then compare it with how long the same task took before.
Hours and output per hour are two different readingsWorked out from the same two timings
- Before: 1 report per 90 min1.0x
- After: 1 report per 60 min1.5x
90 ÷ 60 = 1.5x output per hour on this task. The same change also reads as about 33% less time per report. The two percentages describe one change, so they are not interchangeable.
This derived rate holds only if accepted quality stays the same, and it applies only to this report. It says nothing yet about revenue.
- Was the time used?Follow these 10 hours to finished work
- What limited the upside?Find what capped the gain
Original measurement steps and report exampleHow to measure hours freed, with the source calculation
What changed?
How to measure hours freed
- Time one defined task from start to finished and approved, including review and corrections.
- Log enough real examples, before and after, over the same kind of period.
- Multiply the minutes saved by the number of comparable tasks completed.
Illustrative example · one weekly client report
Before90 min
After60 min
DraftReviewFixes
(90 − 60 min) × 20 reports a week = 600 min = 10 h released
Hours released are the starting point. They gain value once the team applies them to useful work.
For the setup examples · time one real task from start to approved finish, with review, fixes and upkeep included. Compare it with how long the same task took before.
Was the time used?
Did released time become useful work? Follow the hours to a named job and count what passed review. Hours released are not automatically revenue.
6 h assignedTo queued client onboarding
Write down which released hours were assigned, and to what work. Queued work matters here: these hours went to something already waiting.
2 onboardings completedCount only work that passed review
Count finished outputs such as proposals, onboardings, reports and follow-ups. Time counts once it produces finished work, so an onboarding that is started but unfinished stays out of this number.
4 h still availableA remainder, not necessarily waste
The example says only that these hours were not assigned this week. Before calling them wasted, ask whether suitable work was waiting. If it was not, the limit may be demand, not effort.
6 ÷ 10 = 60% of released hours used
Count the gain onceHours and finished work describe one gain
The 6 hours and the 2 onboardings are the same effort seen two ways: time spent, then what it produced. Report them side by side and never add them together as two benefits.
Any financial result is a later and separate check. It depends on useful redeployment, demand, quality and cost.
Capacity is room to grow. Name where the 10 h or 40 h in the setup examples goes, such as client onboarding or delivery, and count the finished work each week.
- What changed?See how the 10 hours were measured
- What limited the upside?See why freed hours may have nowhere to go
Original checks and worked weekHours assigned and work completed, with the source calculation
Was the time used?
Hours assigned and work completed
- Write down which released hours were assigned, and to what work.
- Count finished outputs such as proposals, onboardings, reports and follow-ups.
- Count only work that passed review. Time counts once it produces finished work.
Illustrative example · one week
10 h released6 h used
Assigned to queued client onboardingStill available
6 h assigned to queued client onboarding · 2 onboardings completed · 6 ÷ 10 = 60% of released hours used
Capacity is room to grow. Decide where the freed hours go, then track what that work actually completed.
For the setup examples · name where the 10 h or 40 h goes, such as client onboarding or delivery, and count the finished work each week.
What limited the upside?
What stopped the improvement from becoming larger? Free hours cannot pass the tightest link. This check is useful because it shows what to fix next.
The third client waits however many hours are free. More released time alone would not change this week’s result.
Check each link in order
1Hours releasedRoom to work, not yet a result
This is where the chain starts. See how released hours are measured in What changed?
2Output completedDelivery · where this example stops
Next question: how much can the team actually start and finish this week, and what sets that number?
If delivery is the limit, more hours elsewhere will not move the result. The next improvement belongs here.
3Quality acceptedQuality · does it stay accepted?
Next question: how much work comes back? Track rework rate so faster work stays accepted work.
4Demand servedDemand · is real work waiting?
Next question: how much real client work is waiting? Count it before assigning freed hours. With none waiting, the time back has nowhere to go yet.
5Margin realizedCost · what is left after costs?
Next question: what remains after costs? Subtract AI setup and running cost before calling anything a return.
Then repeat: fix the tightest link and check again, because the limit can move to another link. A single percentage does not show that.
Original checks and two published studiesDifferent work and different measures: sourced support, not a promised return
What limited the upside?
Demand, delivery, quality, cost
- Demand · Count the real client work waiting before assigning freed hours to it.
- Delivery · If 3 new clients are waiting and the team can start 2 this week, the third waits however many hours are free.
- Quality · Track rework rate so faster work stays accepted work.
- Cost · Subtract AI setup and running cost before calling anything a return.
- Hours released
- Output completed
- Quality accepted
- Demand served
- Margin realized
Two published examples · different work, different measures
Writing tasks · In a controlled test on selected professional writing tasks, people using ChatGPT took 40% less time on average, and graders scored their work 18% higher. Noy and Zhang, Science, 2023
Customer support · At one software company's support team, AI suggestions helped agents solve 15% more customer problems in the same staff time on average, across 5,172 agents. Results varied by person. Brynjolfsson, Li and Raymond, QJE, 2025
These studies measured different things in different settings. Your own numbers come from your own task logs.
For the setup examples · count the client work waiting each week before assigning freed hours. With none waiting, the time back has nowhere to go yet.