Do all-day Google Calendar events count as hours in Calendar Timesheet?

Not by default. Calendar Timesheet excludes an all-day event from your hourly total unless you turn on “Include all-day events,” and an excluded event appears in the exclusions list with the reason “All-day event” rather than being silently dropped.

How many hours does Calendar Timesheet credit for an all-day event?

8 hours per working day it covers, by default — a policy figure you can change, never twenty-four hours and never the literal gap between the event's start and end dates. A day off is not 8 billable hours any more than it is twenty-four; it is a number you decide.

Does a weekend inside an all-day event get counted?

No. Calendar Timesheet only credits Monday, Tuesday, Wednesday, Thursday, and Friday. A Friday-to-Monday offsite spans four calendar days but credits 2 of them — the Friday and the Monday — and a block that falls entirely on a weekend credits nothing at all.

Why doesn't a three-day event credit end minus start?

Because Google reports the day after an all-day event's last day, not the last day itself, and Calendar Timesheet credits one policy day at a time for each day actually covered rather than the raw gap between the two dates. At 7.5 hours a day, three working days credit 1350 minutes — 22.5 hours — not a single figure for the whole span.

Why does the same all-day event show a different start time in different timezones?

Because Calendar Timesheet anchors an all-day event's boundary to midnight in the timezone the report runs in, not to UTC midnight. The same event on 18 August 2026 starts at 2026-08-17T21:00:00Z for a report in Europe/Istanbul and at 2026-08-18T04:00:00Z for one in America/New_York — both midnight, in their own zone.

Can I change which days count as working days for all-day events?

Not yet. Calendar Timesheet currently credits all-day events against a fixed Monday-to-Friday week. If your weekend falls on different days, that default will not match your schedule, and there is no setting yet to change it.

Do all-day events get flagged as overlapping other meetings?

No. Calendar Timesheet never runs overlap detection against an all-day event, so a week logged as an offsite does not mark every meeting inside it as double-booked, and an all-day event is never itself flagged as overlapping anything else.

Do all-day calendar events count as hours worked?

Reconciling August, you scroll past a client call, a design review, and then a four-day block marked as “Offsite — Q3 Planning.” It has no start time and no end time, just a date range running from a Friday to a Monday. Is that meant to be thirty-two hours on your timesheet, or none at all? Calendar Timesheet has an answer, and it is neither.

By default, it counts for nothing — and says so

An all-day event with no start or end time is excluded from your hourly total the moment Calendar Timesheet reads it. It is not silently dropped: open the exclusions list and that block is right there, tagged with the reason “All-day event,” the same way a cancelled one is. Turning that block into hours is something you choose, not something Calendar Timesheet assumes.

Turn it on, and it credits a figure — not the clock

Switch on all-day events and Calendar Timesheet does not read the block as twenty-four hours, and it does not measure the literal gap between the event's start date and its end date either. It credits 8 hours for each day the event covers — a policy figure standing in for a working day, because a day off is not 8 billable hours any more than it is twenty-four. You can change that per-day figure to match your own rate; you cannot yet change which days it applies to.

Only the days you actually work, once each

The 8 hours land on Monday, Tuesday, Wednesday, Thursday, and Friday only — never a Saturday or a Sunday, and never twice for the same day. Take that Friday-to-Monday offsite: four calendar days on the invite, but only 2 of them — the Friday and the Monday — are working days, so Calendar Timesheet credits 2 days, not 4.

A block that never touches a working day counts for nothing

Mark a Saturday-to-Sunday block as an all-day event and Calendar Timesheet excludes it entirely, the same way it excludes a zero-length meeting — there is no working day inside the range for the policy figure to land on.

A three-day trip, at your own rate

Say you bill 7.5 hours for a day away rather than the 8-hour default. A three-day trip credits 3 policy days at that rate — 1350 minutes, or 22.5 hours — one day at a time, not one lump sum for the whole span.

Google reports the day after the last day, on purpose

Export a Tuesday-to-Thursday trip from Google Calendar and its end date is 21 August 2026, a day the event does not include. Calendar Timesheet walks the range up to but excluding that end date; counting through it, an easy mistake in a hand-rolled script, would credit a fourth day that never happened.

Calendar dates, stepped in UTC — even across a clock change

All-day events are calendar dates, not instants, so Calendar Timesheet steps through them one UTC day at a time rather than in your local zone — a spring-forward day is 23 hours long in local time, and stepping in that zone can land on the same date twice. A block from 25 to 31 March 2026 in Europe/London spans 6 calendar days, including the day the clocks change, and still credits exactly 4 working days.

Midnight in your own timezone, not UTC midnight

The all-day boundary is anchored to midnight in the timezone your report runs in, not to UTC midnight — which is why the same all-day event on 18 August 2026 starts at 2026-08-17T21:00:00Z for a report run in Europe/Istanbul and at 2026-08-18T04:00:00Z for one run in America/New_York. That is also the answer to the recurring complaint that all-day events show up as 24-hour blocks in the wrong timezone: the block is a date, and Calendar Timesheet resolves it against the zone you asked for.

A report clips to the days you actually asked for

Ask for a narrower date range than an all-day event covers, and Calendar Timesheet reports only the days that fall inside it, flagged as clipped so the total reads as partial rather than final. A Monday-to-Friday conference — 5 working days in full — reported for a two-day window credits 2 days, not 5.

See how a whole export gets clipped to a date range

All-day events are never flagged as overlapping anything

Two ordinary meetings on the same day can overlap and get flagged; an all-day event never does, on either side. Its date span is not a block of clock time to collide with, so a full week logged as an offsite never marks every meeting inside it as double-booked.

See how overlapping meetings are counted

What this can't tell you

8 hours is a policy you chose, not a measurement of what you actually did that day — Calendar Timesheet has no way to know. And the working week behind it is currently fixed to Monday through Friday: correct for a standard week, wrong for anyone whose weekend falls on different days, since that is not yet something you can change.

Frequently asked questions

Do all-day Google Calendar events count as hours in Calendar Timesheet?: Not by default. Calendar Timesheet excludes an all-day event from your hourly total unless you turn on “Include all-day events,” and an excluded event appears in the exclusions list with the reason “All-day event” rather than being silently dropped.
How many hours does Calendar Timesheet credit for an all-day event?: 8 hours per working day it covers, by default — a policy figure you can change, never twenty-four hours and never the literal gap between the event's start and end dates. A day off is not 8 billable hours any more than it is twenty-four; it is a number you decide.
Does a weekend inside an all-day event get counted?: No. Calendar Timesheet only credits Monday, Tuesday, Wednesday, Thursday, and Friday. A Friday-to-Monday offsite spans four calendar days but credits 2 of them — the Friday and the Monday — and a block that falls entirely on a weekend credits nothing at all.
Why doesn't a three-day event credit end minus start?: Because Google reports the day after an all-day event's last day, not the last day itself, and Calendar Timesheet credits one policy day at a time for each day actually covered rather than the raw gap between the two dates. At 7.5 hours a day, three working days credit 1350 minutes — 22.5 hours — not a single figure for the whole span.
Why does the same all-day event show a different start time in different timezones?: Because Calendar Timesheet anchors an all-day event's boundary to midnight in the timezone the report runs in, not to UTC midnight. The same event on 18 August 2026 starts at 2026-08-17T21:00:00Z for a report in Europe/Istanbul and at 2026-08-18T04:00:00Z for one in America/New_York — both midnight, in their own zone.
Can I change which days count as working days for all-day events?: Not yet. Calendar Timesheet currently credits all-day events against a fixed Monday-to-Friday week. If your weekend falls on different days, that default will not match your schedule, and there is no setting yet to change it.
Do all-day events get flagged as overlapping other meetings?: No. Calendar Timesheet never runs overlap detection against an all-day event, so a week logged as an offsite does not mark every meeting inside it as double-booked, and an all-day event is never itself flagged as overlapping anything else.

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.

Open Calendar Timesheet See how Calendar Timesheet works

Back to WorkAlio