Labor productivity formula: output ÷ labor hours. Output can be physical (units, tasks) or financial (revenue, value added); the input is the hours worked to produce it. Per person: divide the result by headcount. Per day: divide the hours by 8, or use working days as the input directly.
Productivity Calculator
Productivity is output divided by input. Enter what your team produced and the hours it took, and read labor productivity per hour, per person and per day — then drag the what-if slider to see what a few percent more is worth.
What is productivity?
Productivity is the ratio of output to input: how much you get out for what you put in. In a business it usually means labor productivity — output (units, tasks, revenue) divided by the labor hours it took. 1,200 units in 160 hours is a productivity of 7.5 units per hour; $500,000 of revenue from 12 people is $41,667 per employee.
It is not the same as efficiency. Productivity asks how much came out; efficiency asks how little went in for it. A team can be very productive by working long hours and still be inefficient — which is why the number is only useful when the input hours are real, not estimated.
How to calculate productivity
Four steps, one division — the calculator above does them all at once.
-
Pick the output. Units produced, tasks closed, orders shipped, tickets solved, or revenue earned — whatever your team is there to deliver.
-
Measure the input. Total hours worked by everyone who produced that output, over the same period. Tracked hours beat estimated ones.
-
Divide output by input. That is productivity per hour. Divide by headcount for productivity per person, or by working days for a daily rate.
-
Compare it. Against last month, another team, or a target. Percent change = (new − old) ÷ old × 100.
The productivity formula
One equation, three common shapes. The live line under it mirrors the numbers you entered above.
Productivity = Output ÷ Input
Productivity change formula
Change (%) = (new productivity − old productivity) ÷ old productivity × 100. Compare productivity rates, not raw output — 1,200 units in 210 hours (5.71/h) versus 1,000 in 200 (5.0/h) is a 14.3 % gain, even though total hours went up.
Four ways to measure productivity
Same equation, different numerator and denominator. Pick the one that matches the decision you are making.
Labor productivity
Output ÷ hours worked. The workhorse metric for teams, shifts and production lines. Use it to compare periods and spot where hours go without output.
units per hourRevenue per employee
Revenue ÷ headcount for a period. What investors and benchmarks quote; turn it into revenue per employee-hour to compare teams with different schedules.
$ per employeeProductivity rate
Actual output ÷ standard (expected) output × 100. Tells you how a person or line performs against a target — 100 % is on plan.
% of standardMultifactor productivity
Output ÷ (labor + capital + materials). The economist's version; useful when hours are not the only input that matters, harder to keep honest.
output per total inputProductivity vs efficiency
People use them interchangeably; they measure different things. Both matter — and both need the same raw material: real hours.
Productivity: how much came out
Output ÷ input. Raising it means more units, tasks or revenue for the hours you already spend. It rewards effectiveness — doing the right work.
Efficiency: how little went in
Useful output ÷ total input. Raising it means the same result with less waste — fewer idle hours, less rework. It rewards process — doing the work right.
Why you need both
A team can post record productivity by working 60-hour weeks and be deeply inefficient. Track productive versus idle time and you see which lever is actually moving the number.
Worked examples
Three teams, three shapes of the same division.
1,200 units in 160 hours
Four operators, 40 hours each. Labor productivity = 1,200 ÷ 160 = 7.5 units per hour; 300 units per person for the week; 60 per person per 8-hour day.
$48,000 in 320 billable hours
Revenue productivity = 48,000 ÷ 320 = $150 per hour. If the same team logged 400 hours to earn it, productivity would be $120 per hour — a 20 % drop nobody would notice from revenue alone.
900 tickets, then 1,050 tickets
Same 12 people, same 1,920 hours a month. Productivity went from 0.469 to 0.547 tickets per hour — a +16.7 % change. Or: the old 900 tickets would now take 1,646 hours, saving 274 hours a month.
What a productivity gain is worth
Based on the numbers in the calculator above — change them and this board follows.
| Productivity gain | Extra output, same hours | Hours saved, same output |
|---|---|---|
| +5 % | — | — |
| +10 % | — | — |
| +15 % | — | — |
| +20 % | — | — |
Enter your numbers above to fill this board.
Typical teams find 5–15 % once they see where hours actually go — idle time, context switching, unplanned work. That is the range WebWork's productivity insights are built to surface.
Stop typing the input. Track it.
The calculator is only as good as the hours you enter. WebWork records work time automatically — active versus idle, per person, project and app — and shows productivity insights that update every day, so the ratio is live instead of a once-a-month estimate.
No credit card | Cancel anytime
From a one-off number to a live metric
This page divides the numbers you remembered to type in. WebWork's productivity tracker divides the real ones — every tracked hour, active time versus idle time, output per project and person — so you can see productivity move week to week and know why. Free trial, no card needed.
Try WebWork FreeExplore WebWork
This calculator is one small piece of WebWork — a full time tracking and productivity platform for teams.
Productivity tracker
See where the day actually goes — active vs idle time, apps, tasks and focus, per person or team.
See the productivity trackerWorkforce analytics software
Reports on hours, productivity and costs across teams and projects — the numbers behind every decision.
See workforce analyticsEmployee monitoring software
Transparent visibility into how work hours are spent — activity levels, apps and optional screenshots.
See employee monitoringTime tracker for employees
Simple for employees, complete for managers — automatic hours, timesheets and reports for the whole team.
See the employee time trackerProductivity Calculator FAQ
Divide output by input: productivity = output ÷ input. For labor productivity the input is hours worked, so 1,200 units in 160 hours is 7.5 units per hour. Divide by headcount for productivity per person, or by working days for a daily figure. The calculator does all three from the same two numbers.
Labor productivity = output ÷ labor hours. Output can be units, tasks, orders, tickets or revenue; labor hours are the total hours worked by everyone who produced it. Economists use the same formula with GDP as output and total hours worked as input.
Revenue per employee = revenue for a period ÷ number of employees. For a fairer comparison between teams with different schedules, divide again by hours worked per employee to get revenue per employee-hour. Use the "Per employee" mode above.
Change (%) = (new productivity − old productivity) ÷ old productivity × 100. Compare the rates (output per hour), not the raw totals: 1,200 units in 210 hours (5.71 per hour) versus 1,000 in 200 (5.0 per hour) is +14.3 %, even though hours rose.
Productivity is output ÷ input — how much you produce for the hours spent. Efficiency is useful output ÷ total input — how little is wasted getting there. A team can raise productivity by working more hours while its efficiency falls; you need tracked productive versus idle time to tell the two apart.
There is no universal benchmark — a good number is one that is rising against your own baseline. Compare like with like: the same output definition, real tracked hours, and the same period length. Revenue per employee benchmarks vary from under $100,000 in labor-heavy services to over $500,000 in software.
Productivity rate = actual output ÷ standard (expected) output × 100. It expresses performance against a target: 100 % means on plan, 110 % means a tenth ahead. It is common on production lines and in call centres where a standard rate per hour exists.
Hours, whenever you have them — days hide overtime and part-time schedules. If you only have days, the calculator's "per person per 8-hour day" figure converts hours to a daily rate; you can also enter days × 8 as the hours input.
It applies a percentage improvement to your current productivity and shows two equivalent results: how much more output you would get in the same hours, or how many hours you would save producing the same output. Both are the same gain expressed for different decisions — capacity or cost.
WebWork tracks work time automatically and separates active from idle time, by person, project and application. Its productivity insights turn that into productivity levels and trends per team member and per project — the input side of this equation, measured instead of estimated. Try it free; a demo shows it on your own team.