Employee Time Waste Calculator

What this tool does and who it is for

It turns "this takes about twenty minutes a day" into an annual number of hours and an annual cost, per task and per person. That is useful on its own, and it is the input every other automation decision needs.

It is for owners and managers who suspect a lot of the week disappears into copy-and-paste but have never put a figure on it, and for anyone building a business case who needs the figure to survive scrutiny. If you want a payback period rather than a cost, take the output into the ROI calculator. If you want to know whether your business is in a state to automate at all, start with the readiness assessment.

How to read the output, with a worked example

Take a task that takes twenty minutes a day. Most calculators annualise it as twenty minutes times five days times fifty-two weeks: 5,200 minutes, or 86.7 hours a year. That number is wrong, and it is wrong in a predictable direction.

Nobody is at work fifty-two weeks a year. UK statutory holiday entitlement is 5.6 weeks, which is 28 days for someone on a five-day week, and an employer may choose to count bank holidays inside that 28. So the days on which a daily task actually happens look like this:

The naive figure overstates the real one by 12.1%, or £165 a year for one person on one task. Across a team of eight doing the same task, that is £1,320 of savings that were never there to save. It is a small enough error to survive a conversation and a large enough one to matter in a proposal.

England and Wales have eight bank holidays in 2026. Scotland and Northern Ireland each have ten, and Scotland's include a one-off World Cup bank holiday on 15 June. If your team is spread across the UK, the denominator is not even the same for everyone.

One deliberate inconsistency, which is not an inconsistency. The £17.67 hourly figure comes from dividing a fully loaded annual cost by 1,950 paid hours, and paid hours include holiday, because you pay for holiday. The task, however, only happens on days somebody is at their desk. Loaded rate over paid hours, task frequency over available days. Mixing those two up is the most common error in this whole exercise. The team savings dashboard works the loaded rate out from scratch.

The residual step is where the saving actually goes

Say you automate 70% of that twenty-minute task. The tempting arithmetic is 70% of 77.3 hours, so 54.1 hours saved.

In practice the person still opens the thing. Six minutes of genuinely human work remains, plus roughly three minutes to stop what they were doing, load the context and get back out again. Nine minutes, not six. The real saving is eleven minutes a run, not fourteen: 232 × 11 minutes is 42.5 hours, about 21% below the figure the percentage suggested.

This is why the best automation candidates are the ones that go to zero human touches, not the ones with the largest percentage. A task automated 100% and run 232 times saves every one of its minutes. A task automated 90% still needs somebody to look at it 232 times.

The method: what the calculator is doing

Four inputs per task. Minutes per run, taken from watching it once rather than estimating, because estimates of tasks under five minutes are consistently low. Runs per period, converted to runs per year using available working days rather than calendar weeks. Number of people doing it, which is often more than one, because the same reconciliation frequently happens twice in two departments. Loaded hourly rate, not salary divided by 2,080.

Multiply, then apply an automation percentage and subtract the residual human minutes. That last subtraction is the step that separates a figure you can defend from a figure that gets picked apart.

Common mistakes

Annualising by 52 weeks. Covered above. Twelve per cent, every time, always in the flattering direction.

Using salary instead of a loaded rate. Employer National Insurance and pension contributions are real money, and leaving them out understates the cost of the hour by roughly 15%. It makes automation look worse than it is, which is the one error in this list that costs you the project rather than your credibility.

Estimating short tasks. A task genuinely reported as "a couple of minutes" is often four or five once the tab-switching and the login are counted. Frequency amplifies the error: at 232 runs a year, two minutes of underestimate is nearly eight hours.

Counting the task and not the interruption. A four-minute task that arrives unpredictably eleven times a day is not forty-four minutes of cost. The switching cost lands on the work either side of it, and this calculator does not attempt to measure that. It is a reason the figure it produces is conservative, not a reason to inflate it.

Frequently Asked Questions

How many working days are there in a UK year?

Around 232 for a full-time employee on the statutory minimum: 52 weeks of five days is 260, less the 28 days of statutory annual leave that a five-day worker is entitled to. Employers who give bank holidays on top of 25 days' leave land nearer 227. Use that figure rather than 260 when annualising anything daily.

Is the "40% of time is automatable" statistic real?

It circulates widely and every trail leads back to a vendor survey or an unsourced blog post, so this page does not repeat it. Your own number, measured on your own five tasks, is both more defensible and usually more persuasive.

What hourly rate should I use?

A fully loaded one: gross salary plus employer National Insurance plus employer pension contributions, divided by paid hours. For a £30,000 salary that comes out near £17.67 an hour rather than the £15.38 a straight salary division gives.

Should I include time saved on tasks nobody was doing properly anyway?

No. If the weekly report was skipped half the time, its real cost is half of what the frequency suggests. Automating it may well be worth doing for accuracy rather than for hours, and that is a different and honest argument to make.

Why does the total look smaller than I expected?

Usually because one task was measured and the rest were guessed, or because a task that felt constant turned out to run weekly. The number people find shocking is almost always the annual total across five or six small tasks, not any single one.

What to do with the result

Take the top two lines by annual hours and ask one question about each: could this go to zero human touches? If yes, that is your first automation. If no, the residual arithmetic above tells you what the ceiling on the saving really is, and it is often low enough to leave the task alone.

Where this tool stops is the honest bit: it costs a task, but it cannot tell you whether that task is automatable at a sensible price. Some twenty-minute jobs are two hours of work to automate and some are two weeks, and the difference is usually whether the systems involved have a decent API or whether somebody is going to have to drive a browser. Working out which one you are looking at, before money is committed, is the part I get asked to do most often.

That is what I build: n8n and Make.com workflows, custom FastAPI services when the connector does not exist, and the reporting that shows whether the hours actually came back. If you have a number from this page and want a second opinion on which line to attack first, send it over. I am on Upwork and Fiverr, or at iam.mbilalvirk@gmail.com. For context, what workflow automation actually is covers the ground plainly, and the piece on automation for coaches and consultants works through a smaller version of this exercise end to end.