Estimates suggest meetings and application switching can together consume a third or more of the workday. Meeting time is commonly put at 11 to 15 hours a week, and Harvard Business Review found workers toggle between apps about 1,200 times daily, costing around 9% of work time. Recovering focus after interruptions adds further, harder-to-see losses.
Open any manager’s calendar and it looks full. Open the same person’s list of finished work and it looks thin. The gap between the two is where the workday goes, and most of it disappears in two places that are easy to overlook: meetings and the constant hopping between applications.
Both costs are well documented, but they are usually reported separately and without context. This guide puts them side by side, explains what the research does and does not show, and gives you a practical way to measure the loss on your own team. If you want the wider view on measurement, see our guide to how to monitor productivity without making employees feel watched.
Key Takeaways
- Meetings and app switching can together take a third or more of the workday, but the figures overlap and should be treated as a range.
- Workers toggle between apps and websites nearly 1,200 times a day, a cost of about 9% of work time.
- Meeting load is estimated at 11 to 15 hours a week, and many meetings are unplanned and land in peak focus hours.
- The biggest loss is the least visible one: the time it takes to regain focus after each interruption.
- You cannot fix what you have not measured, so start with team-level data and share it openly.
The Short Answer: It Depends on How You Count
There is no single, universal number for time lost at work. Each study measures a different thing, in different companies, with different definitions. The ledger below shows the main sources and what each one really captures.
| Source of loss | Typical figure | What it measures | Caveat |
| Meetings | About 11 to 15 hours a week | Scheduled meeting time from calendar data | Varies by role and company size; leaders spend more |
| Application switching | Nearly 1,200 switches a day, about 9% of time | Toggling between apps and websites | Measured at three large companies; each switch is about two seconds |
| Interruption recovery | About 23 to 25 minutes per return to task | Time before resuming an interrupted task | Large variation; not every interruption costs this much |
Because a meeting is itself an app, and an interruption often involves a switch, these costs overlap. Adding them together would double count. A defensible reading is that direct meeting time plus switching can reach roughly a third of the day, with recovery time as an additional cost that is real but harder to pin down.
An illustrative eight-hour day
To make the ranges concrete, take a 480-minute day. At the low end of the meeting range (25%), meetings take about 120 minutes. Application switching at 9% adds roughly 43 minutes. Together, that is about 163 minutes, or 34% of the day. At the high end of the meeting range (37%), meetings take about 178 minutes, and the combined total rises to roughly 221 minutes, or 46%. Because of the overlap described above, the true figure for most people is likely somewhat lower, and the refocus penalty is on top. This is illustrative arithmetic from the published figures, not a measurement of any one team.
How Much Time Do Meetings Take?
Estimates of weekly meeting time range from about 11 to 15 hours, which is 25% to 37% of a 40-hour week. Leaders and enterprise employees sit toward the top of that range, and unplanned meetings make the total harder to see.
Microsoft’s 2025 Work Trend Index, summarized by HR Executive, found that 57% of meetings are ad hoc, and about half happen between 9 and 11 a.m. and 1 and 3 p.m., peak concentration windows. It also reported that meetings after 8 p.m. rose 16% year over year.
One caution on a widely quoted figure from the same research: the headline of an interruption every two minutes, about 275 a day, describes heavy users of collaboration tools, not the average employee. It shows how bad fragmentation can get, not what a typical day looks like.
The practical point is that calendar hours understate the problem. A meeting at 10 a.m. doesn’t just cost the meeting. It splits the morning into pieces too short for deep work.
How Much Time Does Application Switching Take?
A study published in Harvard Business Review observed 137 users across 20 teams at three Fortune 500 companies. Workers toggled between applications and websites nearly 1,200 times a day, and each switch cost a little over two seconds. Over a year, the authors calculated, that adds up to about five working weeks, or 9% of time at work.
The arithmetic is easy to check. Nearly 1,200 switches at a little over two seconds each is about 40 minutes a day, or roughly 8% of an eight-hour day. In one supply-chain example, a single transaction involved about 350 switches between 22 applications and websites.
The researchers called this the toggle tax. Its defining feature is that no single switch looks expensive, which is why teams rarely notice it until someone measures it.
The Hidden Cost: Getting Your Focus Back
Time on the clock is only part of the loss. Research by Gloria Mark at the University of California, Irvine suggests people often take roughly 23 to 25 minutes to return to an interrupted task, according to a review of her findings. Her team also found people spend an average of about 47 seconds on a screen before switching, and that people interrupt themselves about as often as others interrupt them.
Treat the 23-minute figure with care. It is an average with a wide spread, and in the gap people usually work on something else rather than stare at nothing. The reliable takeaway is directional: interruptions cost more than the seconds they take, and fragmented days leave little room for sustained thinking.
Why Remote and Hybrid Teams Feel It Most
In an office, many coordination needs are settled with a quick conversation at a desk. On a distributed team, the same need becomes a calendar invite, a video call, or a chat thread. Each of those adds a meeting or a notification, and each one asks someone to switch context.
Time zones compound the effect. Microsoft’s 2025 data shows roughly 30% of meetings now span multiple time zones, a 35% rise since 2021, which pushes calls into early mornings and evenings. Flexible schedules help people manage this, but only if the extra hours are a choice rather than an expectation. Without clear norms, meeting load becomes one more route to an overlong day.
How to Measure the Loss on Your Own Team
Industry averages are a starting point. Your team’s real numbers are what drive decisions. A simple four-week approach works well:
- Pick two or three roles: Choose roles with different work, such as engineering, support, and account management, so you can compare.
- Pull meeting hours from calendars: Count scheduled hours per person per week, and note how many fall in morning and early-afternoon peak windows.
- Add app and website usage by category: Look at time in communication tools versus core work tools, and how fragmented the day is.
- Count protected focus blocks: Define a focus block, for example, 60 to 90 minutes without a meeting, and count how many each person gets per week.
- Share and discuss the results: Review team-level patterns with employees and ask what is causing the fragmentation before changing anything.
Common measurement mistakes
- Comparing roles directly: A support agent and an engineer need very different amounts of collaboration, so compare each role against its own expectations.
- Treating all switching as waste: Some switching is part of the job, such as pulling data from one tool into another. Look for patterns that grow or cluster, not for zero.
- Counting only scheduled meetings: Ad hoc calls and chat threads are part of the real load.
- Acting without the team: Employees usually know exactly which meetings and tools cause the most friction. Ask them.
Practical Ways to Win Back Time
- Audit recurring meetings: Cancel those without a clear purpose or agenda, and shorten the rest.
- Protect peak hours: Set no-meeting blocks in the mid-morning and early-afternoon windows where focus is strongest.
- Default to asynchronous updates: Status updates and simple decisions rarely need a live call.
- Batch notifications: Check chat and email at set times instead of reacting to every ping.
- Set meeting defaults: Shorter default lengths, a stated purpose on every invite, and a clear owner for each recurring meeting prevent drift.
- Respect time zones: Rotate inconvenient meeting times fairly, and record sessions or share notes so people can opt out without losing context.
- Reduce tool sprawl: Where possible, consolidate overlapping applications and integrate the rest, since fewer tools mean fewer switches.
Reclaimed time also needs a destination. Our piece on where the hours AI saves employees actually go shows why freed hours can quietly refill with new work unless focus time is protected deliberately.
How REMOTLY Helps Teams See Where Time Goes
REMOTLY is an AI-powered workforce productivity and intelligence platform for remote, hybrid, and in-office teams. Its real-time productivity dashboards show engagement and inactivity, plus top app and website usage, and productivity classification lets organizations mark apps and websites as productive or unproductive for specific job roles. According to REMOTLY, related capabilities include:
- Time spent by app and website category, with historical data and daily summary reports
- Focus-time tools that identify blocks of deep work and alert teams when distraction spikes, described in REMOTLY’s Time Block Planner
- A productivity timeline that lets managers zoom in on bursts of work and slowdowns
- Employee self-access, so people can see the same patterns managers see
For a deeper look at using usage data to understand work patterns, see how app and website usage data reveals work patterns. REMOTLY reports digital activity, so pair it with calendar data to see the full meeting picture.
Want to see where your team’s hours actually go? Explore REMOTLY’s features or visit remotly.tech to book a demo.
The Bottom Line
Meetings and application switching can take a third or more of the workday, and the refocus penalty adds more on top. The numbers overlap and vary by role, so use them as a range and measure your own team. Start with a few weeks of team-level data, protect focus blocks, and share what you find. The hours are rarely lost in one place. They leak out in small pieces, and small pieces are exactly what measurement makes visible.
FAQs
How much of the workday is lost to meetings?
Research estimates suggest that meetings occupy approximately 11–15 hours per week, accounting for 25%–37% of a standard 40-hour workweek, with figures varying by data source and the employees included in the analysis. Leaders and enterprise employees tend to sit at the high end.
How much productivity is lost when employees frequently switch between applications?
A Harvard Business Review study of 137 users found they toggled between apps and websites nearly 1,200 times a day, at a little over two seconds per switch. Over a year, the researchers calculated this costs about 9% of time at work.
How long does it take to refocus after an interruption?
Research by Gloria Mark at UC Irvine suggests about 23 to 25 minutes on average before people return to the interrupted task. Since individual experiences vary considerably and employees may handle other responsibilities during these intervals, the figure should be viewed as a general estimate rather than a fixed standard.
Are meetings always a waste of time?
No. Meetings are valuable for decisions, sensitive conversations, and building trust. The problem is volume, timing, and unplanned meetings that land in peak focus hours. The goal is fewer, better-timed meetings, not zero.
What is the toggle tax?
The toggle tax is the cumulative time and mental effort lost when workers move between applications and websites throughout the day. Each switch is brief, but the frequency makes the total substantial.
How can managers reduce context switching without banning tools?
Protect uninterrupted focus blocks, move routine updates to asynchronous channels, batch notifications, and reduce overlapping tools where possible. Review the changes with the team and keep what measurably improves focus time.
How can I measure meeting and app-switching time on my team?
Combine calendar data for meeting hours with app and website usage reporting for switching and focus patterns. Track a few weeks of team-level trends, compare against role expectations, and review the results with employees.
