How Much Time Do Employees Spend Preparing for Meetings? The Real Shadow-Work Benchmark

How much time do employees spend preparing for meetings? If you only count what shows on the calendar, you are measuring the tip of the iceberg. Here is the scenario most teams know too well: a thirty-minute sync that someone starts prepping for the night before, that someone else opens with a deck edited during the walk to the conference room, and that generates an hour of follow-up notes, decisions, and action-chasing after everyone leaves. The meeting itself was the smallest part.

The research agrees. A 2025 survey of 1,000 U.S. technology and business leaders found employees spend nearly 25 hours per week on meeting work — but less than 10 of those hours are actually in meetings. The rest is shadow work: the preparation and follow-up that never appears on anyone's calendar. This post breaks down what the benchmark really says, why preparation keeps collapsing into the final ten minutes, and what it takes to make the shadow work shrink.

The real benchmark: a 25-hour week behind a 10-hour calendar

The clearest recent number comes from a joint Deloitte and Zoom study of 1,000 U.S. technology and business leaders, reported in late 2025. Respondents said they spent nearly 25 hours per week preparing for, participating in, or following up on meetings. In-meeting time? Less than 10 hours. Preparation and follow-up took nearly 15.

Read that ratio again: for every hour your team spends inside the room, roughly an hour and a half is spent outside it. The calendar — the artifact most leaders use to reason about meeting load — understates meeting work by more than half. When an executive says "my team only has 10 hours of meetings a week," the honest translation is "my team has 25 hours of meeting work a week and 15 of it is invisible."

The meeting calendar is a receipt for the cheapest part of the meeting. The expensive part — agendas, pre-reads, decks, minutes, action-chasing — never prints on it.

The same study measured where the invisible hours leak. Employees reported losing an average of 1.6 hours per week in the preparation stage alone — setting agendas, scheduling, assembling the pre-read — plus another 10 minutes per meeting to garbled audio, failed screen shares, and hardware glitches. That is time burned on the logistics of meeting, not the substance of it.

A caveat worth stating honestly: this is a self-reported, vendor-commissioned survey, not instrumented time records. People round. People forget. But the direction is consistent with everything else we know about meeting economics — including our own analysis of how much time employees spend in meetings, which found the in-room number alone has been climbing for years. The before-and-after layer compounds an already-growing base.

The 122% problem: preparation that happens in the last ten minutes

Here is the detail that turns "employees don't prepare enough" from an opinion into a telemetry fact. Microsoft's 2025 Work Trend Index measured document behavior across Microsoft 365 and found that PowerPoint edits spike 122% in the final 10 minutes before a meeting. Microsoft's own description is the digital equivalent of cramming before an exam.

Cramming is not preparation. It is re-assembly. Nobody frantically edits a deck ten minutes before a meeting because the content was impossible to write earlier — they do it because the content of that deck is status, and status keeps changing until the moment the call starts. The numbers live in a spreadsheet, the blockers live in a Slack thread, the decisions live in three different channels, and one person is paid to reconcile all of it into slides while walking to the room.

Microsoft's telemetry makes the timing worse. About half of all meetings land in the 9–11 a.m. and 1–3 p.m. windows — the hours most employees identify as their productivity peaks. So the cramming isn't just last-minute; it's last-minute during the hours people should be doing their deepest work. The preparation tax is paid in the most expensive cognitive hours of the day, and then the meeting itself consumes the recovery time. We covered the interruption arithmetic in the benchmark on daily interruptions; the pre-meeting edit spike is what those interruptions look like when they're wearing a tie.

The uncomfortable implication: if your pre-reads are still being assembled in the final minutes, your meeting culture has institutionalized context loss. The information existed. It was just scattered across platforms, so someone had to be paid in overtime to gather it.

The preparation gap and the multiplier nobody budgets for

Preparation time is also distributed unfairly, and the people with the least of it carry the most responsibility. A Lucid Meetings state-of-meetings survey found only 41% of respondents said they had enough time to prepare for the meetings they attend. Twenty-three percent said they rarely or never did. Nearly a quarter of participants are walking in cold, every week, by design.

Then there is the multiplier. In a classic Harvard Business Review investigation, Michael Mankins traced one weekly executive committee meeting at a large company and found it consumed 300,000 person-hours a year once you counted the preparation layers it generated underneath: every business unit that mirrored the meeting, every deck built to feed it, every briefing call convened to align on the briefing pack. The calendar showed 52 meetings. The organization paid for thousands.

The follow-up side of the ledger is its own tax. A 2026 compilation of the meeting-prep research aggregates Microsoft's survey of 31,000 workers across 31 countries: 55% said next steps were unclear after meetings, 56% found it hard to summarize them, and 57% found it hard to catch up after joining late. Every one of those percentages is an invoice for follow-up work — someone rewriting minutes, someone re-explaining decisions, someone chasing owners. It's the same waiting-and-hunting tax we quantified in our breakdown of coordination time, just wearing a meeting's clothing.

What the whole lifecycle actually costs, stage by stage:

What good looks like: meetings that start with the context already assembled

Compare the cramming culture with a team that treats preparation as an engineering problem instead of a personal virtue. On the better team, the pre-read assembles itself: updates arrive in the channels where work already happens, get captured as they post, and land in a shared project picture before the meeting opens. The deck isn't edited 122% in the final ten minutes because it was never the container for live status in the first place. The meeting starts at the decision, not at the recap.

The contrast is practical, not philosophical. Preparation collapses when the status work is done once, asynchronously, where it already happens — instead of re-collected by hand before every sync. Follow-up collapses when decisions and owners are captured in the flow of conversation instead of reconstructed from memory an hour later. The 25-hour week doesn't shrink because people try harder. It shrinks because the collection, assembly, and distribution work gets taken out of human hands.

This is precisely the job Project Intelligence does at Asa.Team: it surfaces project updates from Slack, Teams, Telegram, and WhatsApp and assembles them into a live project picture, so the pre-read, the status recap, and the "where does this stand?" chase are already answered before anyone books the room. Teams using it aren't preparing less — they're preparing nothing, because the preparation was done by the work itself. The thirty-minute sync still happens. It just starts with everyone having read the same page, literally.

Frequently Asked Questions

Do preparation hours count as meeting time?

Not in most calendar-based metrics — which is the point. The Deloitte and Zoom study separates them deliberately: less than 10 hours in meetings, nearly 15 preparing and following up. Any "meeting hours" number that comes from calendar exports is missing roughly 60% of the workload.

Why do employees prepare at the last minute?

Because most meeting content is status, and status stays fluid until the meeting starts. Microsoft's telemetry shows PowerPoint edits spiking 122% in the ten minutes before meetings — people are reconciling scattered information at the last possible moment, which is rational behavior when the underlying updates live across chat tools, spreadsheets, and other people's heads.

How many hours of meeting preparation is too many?

The benchmark offers a floor, not a quota. If prep-plus-follow-up time per week exceeds in-meeting time by more than 1.5x — the current U.S. average — the preparation layer, not the meetings, is where your budget should go. Audit the four-week ledger: who drafts the agenda, who assembles the pre-read, who writes the minutes, and who chases the actions.

Does AI note-taking fix the follow-up problem?

It fixes half of it. Notes capture what was said; they don't capture what happened in the channels between meetings, and they don't chase action owners. Follow-up time shrinks when decisions, owners, and status are captured continuously in the tools where work happens — not only when the meeting itself is transcribed.

Stop budgeting for the meeting and start budgeting for the work around it

The next time a meeting on your calendar takes thirty minutes, ask what it actually cost. Someone spent an evening assembling the pre-read. Someone else spent the walk to the room editing slides — joining the 122% cramming cohort. Someone will spend the morning after writing notes nobody requested and chasing owners nobody named. The twenty-five-hour week is real; the ten-hour calendar is the fiction.

So the question worth answering isn't "how do we prepare better." It's "why does preparing require assembly work at all?" The status your teams reconstruct before every meeting already exists somewhere in the tools you pay for. The only real question is whether you keep paying people to hunt it down — or let it surface itself. Start a four-week ledger this Monday. When you see how much of it is re-collection, you won't need another meeting to decide.