Do overlapping calendar events double-count your hours?
You block off Thursday afternoon, a client reschedules straight into a slot that already has a standup in it, and for thirty minutes two events sit on top of each other. By the time the week settles, three separate calls end up sharing the same hour. Add up every entry on the calendar and those thirty minutes get counted twice — and naively summing every overlapping pair overcounts the three-way pile-up even more. That is exactly the number Calendar Timesheet refuses to give you.
Overlapping pairs multiply faster than double-booked time does
Book three one-hour calls into the same slot and Calendar Timesheet finds 3 overlapping pairs — every call collides with the other two. Add up each pair's overlap and the damage looks like 180 minutes. The real figure is 120 minutes (2 hours), because all three calls occupy the very same hour rather than three separate overlapping hours. Calendar Timesheet merges the spans into one block and measures what is actually covered twice, instead of adding up every pair that happens to touch.
Calendar Timesheet reports the overlap; it does not shrink your total
Two two-hour blocks scheduled on top of each other still add up to 240 minutes (4 hours) across 2 events — the raw total is never reduced because of an overlap. Alongside it you get a flag: 120 minutes (2 hours) of that total is double-counted. Calendar Timesheet will not decide which of the two blocks you actually worked through; only you know that, so both events stay on the sheet and you are told exactly how much of the total to treat with suspicion.
Where one meeting ends, Calendar Timesheet draws a hard line
A nine o'clock call ending at ten, immediately followed by a ten o'clock call, produces zero overlapping pairs — the shared instant at exactly 10:00 belongs to neither call once its own end is reached. A formula that treats touching boundaries as overlap flags every ordinary back-to-back day as one long collision; Calendar Timesheet's end times are exclusive, so a full day of adjoining meetings reports no overlap at all.
A meeting swallowed by a longer one still overlaps — at its own length
A three-hour block from nine to noon with a thirty-minute call sitting inside it from ten to half past overlaps for exactly 30 minutes: the inner call's entire length, nothing more and nothing less. Calendar Timesheet takes the intersection of the two spans, so containment is simply an overlap where one side happens to start later and end earlier than the other.
All-day blocks sit outside the count entirely
Put an all-day event over a morning that already has a standup and a review on it, and overlap detection ignores the all-day block completely — it contributes 0 pairs, on either side. Its span is a date, not a stretch of clock time, so treating it like a timed meeting would flag every event that day as double-booked without telling you anything true.
See how Calendar Timesheet counts all-day eventsWhat this can't tell you
Calendar Timesheet will not tell you which side of a double-booking you actually worked, and it will not hand you a corrected total — it deliberately stops short of merging or deduplicating your calendar for you, rather than quietly flattening the numbers. What it gives you is the honest size of the problem: in the two-call example above, 120 minutes of overlap is a number you can act on; a total that has already decided for you is not. Overlap detection also only runs on timed events — an all-day block is never part of it, on either side.
Frequently asked questions
- Why doesn't Calendar Timesheet just add up every overlapping pair to find double-counted time?
- Because that overstates it. Three one-hour calls sharing the same hour make 3 overlapping pairs, and summing their overlaps would claim 180 minutes of double-booked time. The real figure, once the spans are merged instead of summed, is 120 minutes.
- Does Calendar Timesheet remove double-booked time from my hours?
- No. Two overlapping two-hour blocks still total 240 minutes across 2 events; Calendar Timesheet flags 120 minutes of that as double-counted and leaves the decision about which event to keep to you.
- Does back-to-back scheduling count as an overlap?
- No. A call ending at 10:00 immediately followed by one starting at 10:00 produces zero overlapping pairs — the shared boundary belongs to neither call once it has ended.
- What happens when a short meeting is scheduled entirely inside a longer one?
- It overlaps for its own full length. A 30-minute call inside a 3-hour block overlaps for 30 minutes — not some fraction of the longer event.
- Do all-day events get flagged as overlapping the meetings underneath them?
- No, never. Overlap detection only looks at timed events, so an all-day block placed over a full day of meetings contributes 0 pairs to the count.
See it on your own calendar
Calendar Timesheet reads an .ics export in your browser — nothing is uploaded, and nothing is connected to your Google account.