The Cost of Late Meetings: How 2-Minute Delays Compound at Scale

I have seen leadership teams argue about who was late while nobody asks whether the meeting itself started late. Those are different problems.

If one person joins at 10:04 and the other six people have already started, there may be an attendance issue, but there are no direct waiting minutes for the group. If six people sit idle until a required seventh person arrives at 10:04, the meeting has consumed 24 person-minutes before the work begins. That is the number worth pricing.

Now scale that habit. A 2024 London School of Economics survey of 208 executives and employees reported an average of seven meetings a week, counting meetings with at least three people. For an illustrative company of 500 employees, if two minutes becomes the normal start delay and the affected employees are ready but unable to begin, the company commits 116.7 paid hours to waiting each week. Across 48 working weeks at an assumed loaded cost of $60 an hour, that is $336,000 a year: 500 × 7 × 2 ÷ 60 × 48 × $60. This is gross paid capacity, not money automatically returned to payroll. Use your own currency, loaded hourly rate, meeting frequency, and observed delay to calculate the company's actual figure.

This distinction keeps the calculation honest. It also moves the conversation away from blaming employees and toward fixing the scheduling system, meeting design, or operating rule that caused a group to wait.

The short answer: calculate waiting, not blame

Use this formula for the direct cost of a late start:

Late-meeting waiting cost = delayed start minutes ÷ 60 × combined loaded hourly cost of the people who were ready but unable to begin

Then annualize only with the number of times the delay actually occurred:

Annual delay cost = average cost per delayed occurrence × delayed occurrences per year

Three boundaries matter:

• Price the people who were waiting, not everyone on the invitation by default.
• Keep late-start cost separate from meeting overrun cost.
• Treat the result as paid capacity committed to waiting. It is not cash automatically returned to the company.

For the broader financial model, including total meeting investment, budgeting, and cost types, use the Meeting Cost Guide. This article stays with one narrower question: what does a delayed start cost, and how do you reduce it?

In Flowtrace's 2026 meeting statistics work, based on 1,240,880 scheduled meetings from 2025, the median average-late-time bucket among meetings with video-call timing data was 60 to 75 seconds. That timing subset covered roughly one quarter of meetings, so it is not a universal punctuality benchmark. It does show why the measurement needs scale. A small delay repeated across many meeting series can matter even when no single event looks dramatic.

What counts as a late meeting?

A late meeting is a meeting that cannot begin at its scheduled start time. That definition sounds obvious until different calendar events are mixed together.

The difference protects both the arithmetic and the people involved. A video-call join time can help establish when someone connected, but it does not by itself explain whether the meeting had started, whether that person was required, or whether useful work was already underway.

How to calculate the cost of a late meeting

Start with four inputs:

1. Scheduled start time.
2. Actual meeting start time.
3. People who were ready but unable to begin.
4. A consistent loaded hourly cost for those people.

Loaded hourly cost usually starts with salary and employer costs divided by workable annual hours. Many companies use role bands or team averages instead of exact individual salaries. That reduces unnecessary sensitivity while keeping the estimate useful. Our guide to calculating and budgeting total company meeting cost explains the full salary-loaded method.

A worked late-meeting cost example

A weekly operations review is scheduled for 10:00. Six people are ready, but the meeting cannot begin until the required owner arrives at 10:08.

The waiting group has a combined loaded cost of $360 per hour.

8 minutes ÷ 60 × $360 = $48

The direct delay cost for that occurrence is $48.

If the same delay happens 45 times in a working year:

$48 × 45 = $2,160

That $2,160 is the gross labor-cost equivalent of the waiting time. It does not prove the company can remove $2,160 from payroll. The practical opportunity is to release capacity and protect the work scheduled after the meeting.

If all seven attendees then remain eight minutes beyond the scheduled end, calculate that overrun separately using the hourly cost of the people who stayed. If the meeting still ends on time, do not invent an overrun. The risk may instead be a rushed decision, an unfinished agenda, or another follow-up meeting. Those effects need observable evidence before they receive a monetary value.

What not to force into the formula

Frustration, context switching, decision quality, preparation, and recovery can matter. They are not interchangeable with direct waiting minutes.

Research by Allen, Lehmann-Willenbrock, and Rogelberg found lower meeting satisfaction and effectiveness when meetings started late. In a randomized study of 48 groups, five- and ten-minute late-start conditions also differed from an on-time control on perceived outcomes and objective group performance. That is credible evidence that lateness can affect the meeting itself. It is not a license to add a universal productivity multiplier.

Track those wider effects as outcomes first. Repeated follow-up meetings, unresolved decisions, missed actions, or reported meeting quality are more defensible than a guessed percentage. The indirect costs of meetings need their own evidence and remedy.

Measure the pattern before changing behavior

One late start tells you what happened once. A useful baseline tells you whether the problem repeats, where it concentrates, and which cause is plausible.

For each meeting occurrence, record:

• Scheduled and actual start time.
• Actual end time when available.
• Attendees who joined and the people required to begin.
• Meeting series, organizer, team, time of day, and meeting type.
• Whether the previous calendar event overran.
• Direct waiting minutes and cost using the same assumptions.

Do not compare unlike work without context. A customer escalation, candidate interview, incident review, and weekly status meeting have different dependencies. Compare repeated occurrences of the same series or similar meeting families before deciding a team has a punctuality problem.

The image shows why event-level timing matters. A series can have the same scheduled slot every week while actual start, end, attendance, and duration vary. Meeting cost tracking becomes useful when those occurrences are aggregated without losing the meeting context behind them.

Find the cause of late meetings

Punctuality advice often starts and ends with telling people to be on time. That only works when the cause is personal choice. Company calendars create other causes every day.

If the same recurring series repeatedly starts late, use the recurring meeting review guide to decide whether to change its owner, time, format, or frequency.

Microsoft's Human Factors Lab compared four back-to-back video meetings with the same schedule separated by ten-minute meditation breaks. In that small study of 14 information workers, the breaks reduced accumulated beta-wave activity associated with stress and softened the transition spike between meetings. The sample is too small for a universal productivity claim, but the mechanism supports deliberate transition time.

For Outlook, Microsoft documents how to end meetings early or start them late. Another practical option is to use 25- or 50-minute calendar slots so the meeting and the transition both have time assigned. A buffer is not wasted space if it prevents the next group from waiting.

A 30-day plan to reduce late-meeting cost

Use a bounded test. Company-wide punctuality campaigns tend to create noise before anyone knows which meetings are causing the loss.

Week 1: define the measure

Agree when a meeting counts as started, who must be present, how grace periods work, and which loaded cost assumptions will be used. Decide whether a one-minute technical delay is recorded, ignored, or rounded consistently. Publish the definition so teams are not surprised later.

Weeks 2 and 3: build the baseline

Measure delayed starts across comparable meeting families. Rank meeting series by attendee-weighted waiting minutes and cost, then inspect the cause. Do not publish individual leaderboards. The useful question is why a recurring group is unable to start, not which person can be embarrassed by the dashboard.

Week 4: change one mechanism

Choose a small number of high-cost patterns and apply the relevant fix. Add a transition buffer, name a deputy, remove an unnecessary dependency, repair the room setup, or start with the available quorum. Keep a counter-metric such as overrun minutes, decision completion, cancellations, or follow-up meetings so the company does not create a new problem while fixing punctuality.

Measure again after the change. If waiting cost falls but overruns rise, the intervention has moved the problem. If both fall and the meeting still completes its job, keep the rule and test the next pattern.

How Flowtrace measures late-meeting cost

Flowtrace meeting analytics connects calendar and supported video-call metadata to show scheduled meeting investment, actual start and end patterns, attendance signals, delay time, and monetary delay-cost estimates. Leaders can review the pattern by meeting, team, or organizer and compare repeated occurrences.

Flowtrace does not need to record, transcribe, or interpret meeting conversations for this work. The measurement uses meeting metadata and configured cost assumptions. Coverage depends on the calendar and meeting systems connected, so estimates should retain their input and data-quality context.

That makes the product useful for a system-level question: where are groups repeatedly waiting, and which operating change would remove that delay? It should not be used to turn one late join into an employee performance judgment.

Flowtrace also provides meeting cost plugins for Google Calendar and Outlook that show cost and policy guidance while organizers create or edit meetings. Scheduling-time visibility helps prevent avoidable meeting cost. Organization-level analytics then verifies whether late starts, overruns, and other patterns changed.

Late meeting cost FAQ

What is a late meeting?

A late meeting is one that cannot begin at its scheduled start time. One attendee joining late is an attendance issue, but it creates meeting delay only when the group waits or necessary work cannot begin.

How do you calculate the cost of a late meeting?

Divide the delayed start minutes by 60, then multiply by the sum of loaded hourly cost for people who were ready but unable to begin. Multiply the per-event result by actual recurrence count for an annual estimate.

Who should be included in meeting delay cost?

Include people whose paid time was committed to waiting because the meeting could not start. Do not automatically include a late attendee before they join, optional attendees who did not block the meeting, or people who continued useful work.

Is a one-minute meeting delay worth measuring?

A single one-minute delay rarely deserves intervention. Measure it consistently because short delays can become material when they repeat across large recurring meeting portfolios. Act on patterns and causes, not isolated people.

Should a meeting wait for late participants?

Start when the meeting has the people and information needed to do the work. If a required decision maker is missing, use a named deputy, reschedule, or change the meeting design instead of making every attendee wait without a rule.

Start with one definition your company can defend

Late meetings become expensive when waiting is repeated, multiplied across attendees, and allowed to push the rest of the day. The arithmetic is simple once the company agrees what a delayed start means.

Measure the people who actually waited. Separate delay from overrun. Find the mechanism, change it, and inspect the next month of comparable meetings. If the same group is still waiting, another reminder will not fix it. The meeting needs a different rule.

If you want to see meeting delay cost alongside total meeting investment, attendance, recurrence, and team patterns, schedule a Flowtrace meeting analytics demo.