SalesBooking behaviour

Only 14% of meetings are booked for today or tomorrow

Name: Only 14% of meetings are booked for today or tomorrow
Creator: meetergo GmbH
License: https://creativecommons.org/licenses/by/4.0/

The industry runs on a 2007 study about lead response time and a widely repeated instruction to call within five minutes. Booked meetings do not behave that way: 14.3% happen within a day of being booked, 43.2% are more than a week out, and the single largest bucket is more than two weeks.

Completed, non-cancelled meetings over 180 days, measured as the gap between the booking timestamp and the meeting's start. n = 841,480.

meetergo DataPublished August 20, 2026Data as of August 20, 2026n = 841,480

How far ahead meetings are actually booked

Completed, non-cancelled meetings over 180 days, by the gap between booking and start. n = 841,480.

Booked for today or tomorrow

14.3%

120,701 meetings. The speed-to-lead orthodoxy describes this slice and no other.

Booked more than two weeks out

24.3%

204,147 meetings: the largest single bucket in the distribution.

Completed meetings

841,480

180 days, cancellations excluded, start time already in the past.

Same or next day
14.3%
120,701 meetings · 14.3% cumulative
1 to 3 days
18.9%
159,198 meetings · 33.3% cumulative
3 to 7 days
23.5%
197,705 meetings · 56.8% cumulative
7 to 14 days
19.0%
159,729 meetings · 75.7% cumulative
More than 14 days
24.3%
204,147 meetings · 100.0% cumulative

The whole distribution, end to end

14.3%

18.9%

23.5%

19.0%

24.3%

Same or next day
1 to 3 days
3 to 7 days
7 to 14 days
More than 14 days

One measure, one scale. The bars are each bucket's share; the strip below is the same five shares laid end to end, so the cumulative figure can be read off directly.

meetergo.com/datameetergo GmbH

Booking lead time distribution
Lead time	Meetings	Share of day	Cumulative
Same or next day	120,701	14.34%	14.34%
1 to 3 days	159,198	18.92%	33.26%
3 to 7 days	197,705	23.49%	56.75%
7 to 14 days	159,729	18.98%	75.74%
More than 14 days	204,147	24.26%	100.00%

Cumulative is the share of meetings booked at or below that lead time. Meetings still in the future are excluded, so a long-lead booking made yesterday is not counted yet.

Bookings collapse at the weekend, and they do not stop

Bookings created per day, 19 July to 19 August 2026. 23 weekdays against 9 weekend days, 229,324 bookings across 32 whole days.

Weekday averageavg 8,892.4/day
Weekend averageavg 2,755.3/day

−69.0% fewer bookings created per weekend day, across 229,324 bookings in 32 whole days.

The dashed lines are the two averages; the gap between them is the drop the headline claims. A 33rd day, 20 August, stood at 1,503 bookings when the query ran and is left out. A day still in progress does not belong in a comparison of 32 whole ones.

meetergo.com/datameetergo GmbH

Bookings created per day, 19 July to 19 August 2026
Date	Day type	Bookings
Sun, 07/19	Weekend average	2,615
Mon, 07/20	Weekday average	9,228
Tue, 07/21	Weekday average	8,557
Wed, 07/22	Weekday average	8,647
Thu, 07/23	Weekday average	7,114
Fri, 07/24	Weekday average	5,992
Sat, 07/25	Weekend average	2,114
Sun, 07/26	Weekend average	3,106
Mon, 07/27	Weekday average	9,719
Tue, 07/28	Weekday average	9,118
Wed, 07/29	Weekday average	7,545
Thu, 07/30	Weekday average	7,615
Fri, 07/31	Weekday average	5,922
Sat, 08/01	Weekend average	2,405
Sun, 08/02	Weekend average	3,066
Mon, 08/03	Weekday average	9,679
Tue, 08/04	Weekday average	10,120
Wed, 08/05	Weekday average	8,968
Thu, 08/06	Weekday average	9,379
Fri, 08/07	Weekday average	7,395
Sat, 08/08	Weekend average	2,555
Sun, 08/09	Weekend average	3,196
Mon, 08/10	Weekday average	10,411
Tue, 08/11	Weekday average	10,020
Wed, 08/12	Weekday average	8,757
Thu, 08/13	Weekday average	9,719
Fri, 08/14	Weekday average	7,505
Sat, 08/15	Weekend average	2,505
Sun, 08/16	Weekend average	3,236
Mon, 08/17	Weekday average	11,513
Tue, 08/18	Weekday average	11,062
Wed, 08/19	Weekday average	10,541

Non-cancelled bookings by creation date. Weekend days are emphasised. The nine weekend days total 24,798 bookings and the 23 weekdays total 204,526, which is where the two averages in the chart come from.

What this means for you

Lead time decides whether your follow-up cadence and your reminder timing are aimed at the right meeting at all.

How to act on it

A reminder built for same-day bookings misses six meetings out of seven. The 14+ day bucket alone is a quarter of your meetings, and the one most exposed to cancellation and reschedule.
If your sales process measures speed-to-lead and nothing else, it is optimising 14.3% of your meetings and ignoring where the volume actually sits.
Weekend bookings do not disappear. 2,755 a day is still nearly a third of the weekday rate, arriving when nobody is watching the inbox: routing rules matter more than staffing there.

What this chart cannot tell you

The limits are published with the finding, because the first reply to any chart is an attempt to find them.

Lead time is measured to the meeting's scheduled start, not to when it happened. Reschedules move the start, and this cut does not follow them.
Only meetings whose start time has already passed are counted, which slightly under-weights the longest bucket: a meeting booked yesterday for three months out is not in here yet.
The weekend panel covers a single month in high summer. Treat the −69% as an order of magnitude, not a constant.

›The query behind this report

Run against PostgreSQL. Multi-host meetings duplicate rows across the host join, so the counts use COUNT(DISTINCT).

SELECT
  CASE
    WHEN EXTRACT(EPOCH FROM (a."start"::timestamptz - a."createdAt")) / 3600  < 24 THEN '0-1 days'
    WHEN EXTRACT(EPOCH FROM (a."start"::timestamptz - a."createdAt")) / 86400 < 3  THEN '1-3 days'
    WHEN EXTRACT(EPOCH FROM (a."start"::timestamptz - a."createdAt")) / 86400 < 7  THEN '3-7 days'
    WHEN EXTRACT(EPOCH FROM (a."start"::timestamptz - a."createdAt")) / 86400 < 14 THEN '7-14 days'
    ELSE '14+ days'
  END AS lead_time,
  COUNT(*) AS meetings
FROM "appointment" a
JOIN "attendee" at ON at."appointmentId" = a."id"
WHERE a."isCancelled" = false
  AND a."start"::timestamptz < now()
  AND a."createdAt" >= now() - interval '180 days'
GROUP BY lead_time
ORDER BY MIN(EXTRACT(EPOCH FROM (a."start"::timestamptz - a."createdAt")));

How to cite this

Free to reuse with attribution. Copy the line below or link the chart directly: either way the sample size travels with it.

Across 841,480 completed meetings booked through meetergo over 180 days, only 14.3% were booked for the same or next day, while 24.3% were booked more than two weeks ahead: the largest single bucket in the distribution.

Source: https://meetergo.com/en/data/booking-lead-time

How we collect this data

meetergo is scheduling software used across Europe. The reports here are a by-product of running it: aggregate patterns in when meetings get booked and when they start.

Production data, not a survey

Every figure is a query against the live appointment, attendee and host tables. Nobody was asked what time they prefer to meet: these are the meetings that actually happened.

The method travels with the number

Sample size, window and filter sit in the subhead of every chart, and the SQL sits at the bottom of every report. Run it against your own book if you have one.

Re-run each quarter

Working hours are seasonal: summer hours, the December collapse, the January surge. The meeting clock is re-queried rather than republished unchanged.

Aggregated and non-identifiable

meetergo sells GDPR compliance, so no cut is fine enough to trace back to one customer's booking volume. Every market shown clears a minimum sample of 3,000 meetings.