How to Reduce Overtime: Find the Cause in Your Timesheets Before You Cut Hours

Most teams try to reduce overtime the same way: a manager sends a note asking people to log off on time, overtime drops for two weeks, and then it creeps back. It comes back because the note treats the symptom. Overtime is what happens when the work assigned to a week is bigger than the hours in it, and the reason for that gap is different on every team.

This guide shows how to reduce overtime by finding that reason in your own time data and fixing it. It covers the causes that show up most often in project and office work, a five step overtime reduction action plan with a worked cost example, what US law lets you do about overtime nobody approved, and how to keep the numbers down once they fall.

How to reduce overtime: the short answer

To reduce overtime for good, measure where it happens, find out why it happens there, and fix that cause instead of asking people to work faster. Then put a simple approval rule in place so new overtime is a decision rather than a habit.

Each step gets a full section in the action plan below.

What overtime really costs

Under the FLSA, non exempt employees must be paid “not less than time and one-half their regular rates of pay” for hours over 40 in a workweek, according to the US Department of Labor. So every overtime hour costs at least 50% more than a regular one. That premium is the part everyone sees on payroll. The rest of the bill is less obvious.

Output per hour drops

Long hours do not produce proportionally more work. Economist John Pencavel studied output data for munitions workers and found the relationship is nonlinear: below a threshold, output grows in line with hours, and above it, output “rises at a decreasing rate as hours increase” (IZA Discussion Paper 8129, 2014). In practice, the tenth hour of a long day costs one and a half times as much as the first and delivers less.

Errors, injuries, and health risks rise

The National Institute for Occupational Safety and Health says research links shift work and long work hours with “a somewhat higher risk for illnesses, errors, injuries, and certain symptoms” (NIOSH). At the extreme end, a joint study by the World Health Organization and the International Labour Organization estimated that working 55 or more hours a week led to 745,000 deaths from stroke and heart disease worldwide in 2016. The same study found a 35% higher risk of stroke and a 17% higher risk of dying from ischemic heart disease, compared with a 35 to 40 hour week (WHO and ILO, 2021).

Overtime hides the real problem

The least obvious cost is that overtime makes a broken plan look like it works. A project that needs 20% more hours than it was sold for still ships on time if the team stays late, so nobody fixes the estimate, and the next project is sold the same way. Overtime turns a pricing or planning error into a recurring payroll line.

For a sense of scale, the Bureau of Labor Statistics reports that production and nonsupervisory employees in US manufacturing averaged 4.0 overtime hours a week in September 2026 (seasonally adjusted). Office and project teams are not in that survey, which is one reason their overtime tends to go unmeasured.

Why overtime keeps coming back

Most overtime in project and office work traces back to one of five causes. Each one leaves a different pattern in timesheet data, and each needs a different fix. Treating all of them with a general rule like “no work after 6 pm” moves the hours around without removing them.

One team can have more than one cause. A design agency might have scope creep on its two largest clients and a single senior designer who reviews everything. That is two fixes, and running only one of them leaves half the overtime in place.

A five step overtime reduction action plan

Reducing overtime this way works for a team of five or a company of five hundred. The only requirement is that hours are recorded against the work they were spent on, not just as a daily total.

Step 1. Measure your overtime baseline

Pull 8 to 12 weeks of time records. One week is too noisy, and a year hides recent changes. For each person, note total hours, scheduled hours, and the difference. Then split the overtime by project and by task. You want answers to four questions:

• What share of all hours is overtime?
• Which people account for most of it?
• Which projects or clients account for most of it?
• Is it spread evenly across weeks, or does it spike before deadlines?

Also add up what the overtime cost: overtime hours multiplied by each person’s overtime rate. This figure is your baseline, and it is the number leadership will ask about later.

Step 2. Find the cause on each project

Take the two or three projects with the most overtime and compare actual hours with estimates, task by task. Use the table above as a checklist. If the overrun sits on tasks that were in the original plan, the estimates were wrong. If it sits on tasks added later, the cause is scope. If the project was estimated well but one person logged 50 hours a week on it, the problem is how work is assigned.

Talk to the people with the most overtime before deciding. They usually know exactly why they stay late, and their answer is often more specific than anything in a report.

Step 3. Apply the fix that matches the cause

• If estimates are wrong, take the actual hours from the last few similar tasks and use them as the new estimate. If a “two day” report has taken three days on each of the last five projects, it is a three day task.
• If scope keeps growing, agree on a rule with clients and internal requesters that every addition comes with more hours, a later date, or something removed. Our guide to scope creep covers how to set this up.
• If a few people carry the load, move tasks from the people with overtime to those under schedule, and cross train at least one backup for every bottleneck role, such as a sole reviewer or the only person who knows a client’s system.
• If the whole team is short of hours, compare the overtime cost from Step 1 with the cost of a new hire or contractor. Once steady overtime across a team adds up to more than one full time salary, adding people is usually cheaper.
• If it is habit, look at what managers reward. If late replies get praise, people send late replies. Stop scheduling meetings that push real work into the evening, and protect focus time during the day.

Step 4. Put an overtime policy in writing

A good overtime policy is short. It states who can approve overtime, how far in advance it must be requested, how it is recorded, and what happens if someone works extra hours without approval. It should also say plainly that every hour worked is recorded and paid, approved or not, because the law requires it (see the legal section below).

Pre approval does two things. It makes a manager decide whether the work is worth 1.5 times the cost, and it creates a record that separates planned overtime, such as a launch weekend, from unplanned overtime that points to one of the causes above.

Step 5. Review the numbers every month

Compare monthly overtime hours and cost against your baseline. If the numbers fell and stayed down, the fix worked. If they fell on one project and rose on another, the cause moved, which often happens when an overloaded person is reassigned without their workload changing. Repeat Step 2 on the new hotspot.

See overtime by person, project, and task, compare it with estimates, and track what it costs with actiTIME

Try Free

Worked example: what one team’s overtime costs

The figures below are illustrative. A marketing team of six non exempt specialists earns $30 an hour each. Over the last 10 weeks, each person averaged 5 hours of overtime a week.

The time data shows that 60% of the overtime sits on two client accounts, and on both of them content tasks run about 40% over estimate. The other 40% is spread thinly across the team with no pattern.

So the first move is easy to pick.Fixing estimates and scope on the two accounts addresses 60% of the cost, or $42,120 a year at the current rate ($70,200 x 0.6). Repricing those accounts so the extra hours are billed would recover part of the rest. Asking the whole team to “work smarter” would have spread the effort across the 40% that has no single cause.

Can you stop employees from working overtime?

You can set rules, but you cannot refuse to pay for hours that were already worked. Three points from federal law matter most:

• The FLSA sets no limit on hours. “There is no limit in the Act on the number of hours employees aged 16 and older may work in any workweek,” per the Department of Labor. Employers can require overtime, and they can also forbid it.
• Unapproved overtime is still paid. Federal rules on hours worked say that if management does not want work done, it must “exercise its control and see that the work is not performed,” and that “the mere promulgation of a rule against such work is not enough” (29 CFR 785.13). Work done at home, such as answering email in the evening, follows the same rule (29 CFR 785.12).
• The policy is enforced through discipline, not pay. An employer can warn or discipline someone who breaks an overtime approval rule. It cannot deduct the hours or leave them off the timesheet.

Local rules add more. California adds daily overtime after 8 hours (see our guide to California overtime laws). Oregon requires covered large employers to give workers their schedules in writing at least 14 days in advance, with extra pay for some late changes (Oregon Bureau of Labor and Industries). In the European Union, the Working Time Directive caps average working time at 48 hours per seven day period, overtime included (European Commission).

Five mistakes that bring overtime back

1. Cutting hours without cutting work.

   A hard stop at 6 pm with the same deadlines moves the overtime into weekends or off the record, which creates legal risk on top of the cost.

2. Looking only at daily totals.

   Knowing that someone worked 48 hours does not say why. Without hours by project and task, there is nothing to diagnose.

3. Fixing the person instead of the plan.

   Sending a high overtime employee to a time management course rarely helps when their tasks were underestimated by 40%.

4. Banning overtime and paying for it in comp time.

   Private employers covered by the FLSA cannot replace overtime pay with time off in a later week. Our article on banked hours vs overtime pay explains where the line is.

5. Measuring once.

   Overtime moves as projects change. A team that reviews it monthly catches a new hotspot in weeks rather than at year end.

How to manage overtime in actiTIME

The action plan depends on two kinds of data: hours recorded against tasks, and estimates to compare them with. actiTIME keeps both in one place, so Steps 1, 2, and 5 become reports instead of spreadsheet work.

• Overtime Registration calculates overtime for each user automatically against their schedule, or lets them enter it manually, depending on the mode you choose.
• The Time Balance and Overtime Report shows worked time against scheduled hours for every user, which gives you the baseline for Step 1.
• Task estimates and the Estimated vs. Actual Time Report show which tasks run over and by how much, which is the diagnosis in Step 2.
• With an overtime rate in each user’s profile, the Cost of Work Report shows overtime costs by project and customer.
• Time budgets on projects or tasks turn red when exceeded, so an overrun shows up before it becomes a month of late evenings.
• Timesheet approval and locking give managers a weekly checkpoint and keep approved hours from being changed afterward.

For a step by step setup of overtime calculation and reports, see how to manage overtime the simple way with actiTIME.

FAQ

How do you reduce overtime without hurting productivity?

Remove the reason the extra hours were needed instead of removing the hours. If tasks are underestimated, fix the estimates and deadlines. If one person is overloaded, move work to someone with spare capacity. Productivity per hour usually improves when overtime falls, because output grows more slowly than hours once days get long.

How do you manage overtime effectively?

Record every hour against the work it was spent on, require approval before planned overtime, and review overtime hours and cost every month. Keep overtime for real peaks, such as a launch or a seasonal rush, rather than using it to cover a plan that was short of hours from the start.

Is overtime really worth it?

For short peaks, often yes: paying a trained employee 1.5 times their rate for a few weeks can be cheaper than hiring. As a permanent arrangement, rarely. The premium adds up quickly, output per hour falls on long days, and NIOSH links long hours with more errors and injuries.

Can I reduce the hours of an employee?

Under federal law, yes. The FLSA regulates pay for hours worked, not how many hours you schedule. State and city laws can add notice and pay rules for schedule changes, as Oregon does, and employment contracts or union agreements may set minimum hours. Check those before cutting an employee’s schedule.

What is OT pay for $20 an hour?

$30 an hour at time and a half ($20 x 1.5). Five overtime hours in a week would add $150 to that week’s pay. Use our overtime calculator for other rates and hours.

How do you shorten overtime on a single project?

Compare the remaining work with the remaining hours and deadline. Then cut or postpone lower priority tasks, move tasks to people with spare capacity, or agree on a new date with the client. Adding more evening hours to a late project usually costs more and delivers less than changing its scope.

Treat overtime as a signal

Overtime is rarely the problem itself. It is the bill for a plan that was short of hours. Teams that figure out how to reduce overtime for good trace the hours back to that plan and fix it. Then they check again next month, because the cause often moves.

To see where your team’s overtime comes from, start a free trial of actiTIME. It runs for 30 days with every feature included, and afterward you can keep the permanent free version for teams of up to 3 users.