Google Calendar default notification: setting it once for every event

Setting a reminder on every single event is the kind of task that gets abandoned after a week. The Google Calendar default notification exists to remove it: pick a timing once, and every event created afterwards inherits it. The setting is easy to find. What it covers, and what it silently refuses to touch, is where the time goes.

Two facts explain nearly every complaint about it. The default belongs to one calendar rather than to the account, and it applies only to events that have not been given their own reminders. Everything below follows from those two.

Two different things share the word notification

Google Calendar uses one word for two mechanisms that behave differently, and the distinction decides which screen to open.

A reminder is an alarm that fires a set number of minutes before an event starts. It is the thing most people mean. Reminders can be delivered as a pop up or as an email, and they can be set for a whole calendar as a default or for a single event as an override.

A notification is a message about a change to an event rather than a countdown to it. Google's own list of notification types names five: a new event put on a calendar, a change to an event, a cancellation, an attendee responding to an invitation, and an agenda of the day's events sent out in the morning. These are delivered by email only. There is no pop up equivalent for any of the five.

Anyone trying to stop a stream of email about meetings being edited is looking for the second group, and no amount of adjusting the reminder timing will help. Anyone whose meetings arrive unannounced is looking for the first.

Both are stored as properties of a calendar in the account's own calendar list, which is the technical reason for the behaviour that surprises people most. Reminder and notification settings are private to each person and are not shared with anyone else who can see the same calendar. A shared team calendar can have five different sets of defaults, one per person, and none of them affects the others. Setting a default on a calendar shared with colleagues does not give the colleagues that default.

The default lives on one calendar, not on the account

Open Google Calendar in a browser, open Settings, and look at the left column. Under the heading that lists the account's own calendars there is one entry per calendar, and each entry has its own Event notifications section. That repetition is the whole story.

An account with a work calendar, a personal calendar, a project calendar and two subscribed calendars has five separate default settings. Changing the default on the primary calendar does nothing to the other four. A new calendar created next month starts with its own defaults rather than inheriting the one just configured.

This is also why the setting cannot be reached from the mobile apps in the same shape. The per calendar notification defaults are a browser side screen, and the mobile apps expose a smaller subset. The reliable route is a browser on a computer.

A second place is easy to mistake for this one. The general settings at the top of the same screen hold preferences that apply across the whole account, including how notifications are delivered and whether they are limited to events answered yes or maybe. What they do not hold is a timing. No entry under General sets how many minutes before an event a reminder fires, so time spent there hunting for it is time wasted. The timings are always inside a named calendar further down the list.

There is also a difference between hiding a calendar and silencing it. Unticking a calendar in the sidebar removes its events from view but leaves its reminders configured, so an alarm can fire for an event that is not currently on screen. Removing the notification entries for that calendar is the separate act that stops the alarms.

Inside each calendar there are two lists rather than one. Event notifications governs timed events. All day event notifications governs events with no start time, and it is a separate list with separate entries. A default set on the first has no effect on the second, which is the usual reason an all day deadline passes with no warning while ordinary meetings warn correctly.

Each list accepts more than one entry. Adding a notification twice, at different intervals, gives every new event two alarms. A common pairing is one the day before and one shortly before the start, and it is set here once rather than on each event.

What changing the default does not do

The default applies at the moment an event is created. It does not reach backwards.

An event that was created earlier already stores its own decision about reminders. If that event is using the calendar default, changing the default does change what it does, because the event holds a pointer rather than a copy. If the event was given its own reminder at any point, even one that happens to match the old default, it now holds an override and the default no longer applies to it.

This is the mechanism behind the most common report: the default was changed to thirty minutes, and half the existing meetings still warn at ten. The half that still warn at ten are the ones that were touched individually at some point, often without the person remembering. There is no bulk operation in the interface to release them back to the default. Each one has to be opened and set back to the calendar default individually, or deleted and recreated.

Invitations received from other people follow the same rule from the receiving side. Reminders are private to each copy of an event, so an invitation arriving from outside picks up the receiving account's default rather than whatever the organizer set. An organizer who sets a reminder for themselves is not setting one for the guests, and cannot.

One setting changes which events get reminders at all. Google exposes a preference for sending reminders only for events that have been answered yes or maybe. With it switched on, an unanswered invitation produces no alarm at all, however the default is configured. It defaults to off, and it is worth checking before concluding that the default is broken.

The limits worth knowing before choosing a timing

The numbers are published and they are wider than most people assume.

A reminder can be set from zero minutes before the start up to 40,320 minutes, which is four weeks. That upper bound makes the reminder mechanism usable for things it is not usually used for, such as an annual renewal that needs a month of warning. A value of zero fires at the start time itself.

Each event can carry at most five overriding reminders. That ceiling applies to reminders set on the individual event, not to the calendar default, and hitting it usually means the event is being asked to do the work of a task list.

Delivery is either a pop up or an email sent by the server, and both are available for defaults and for overrides. Pop ups appear on mobile and in web clients. The distinction matters for reliability: an email arrives regardless of which device is awake, while a pop up depends on a client being open and permitted to show it.

Behaviour	Reminders	Notifications
What it announces	Time before an event starts	A change to an event
Pop up available	Yes	No
Email available	Yes	Yes
Set as a default	Per calendar	Per calendar
Set per event	Yes, up to five	No
Visible to other people	No	No

The Mac adds a second set of defaults

On a Mac the browser is often not where events are read, and that introduces a layer that the Google settings do not control.

The Calendar application built into macOS keeps its own default alert times, set per account in its settings rather than fetched from Google. An account that reliably warned about meetings in the browser can arrive on the Mac silent, because the Mac side default has never been set. The reverse also happens: two alerts for the same meeting, one from the Google default delivered as an email and one from the Mac default delivered as a system notification.

macOS then decides separately whether a calendar application may show alerts at all, in System Settings under Notifications. An alert time that is set correctly and a notification permission that is switched off produce the same symptom, which is silence, so both need checking once before blaming the Google default.

The practical order is to set the Google default for each calendar first, because that is the one that follows the account to a phone and a browser, then set the Mac side default to match rather than to add. A native Mac calendar that reads the Google account can show which alert came from which source, and the per event alert options in a desktop calendar sit closer to hand than a browser settings page. The behaviour of alerts alongside travel time and departure warnings is covered in Features, and the initial setup order for an account is in the Guide.

Choosing a timing that survives a full week

The default is worth choosing deliberately once, because it is inherited by every event created afterwards.

Ten minutes is the interval most accounts arrive with, and it assumes the next thing is already open on screen. It is too short for anything that needs a room, a document, or a walk.

Thirty minutes suits a calendar where meetings need preparation, and it is long enough to leave a building. It is also long enough to arrive during the previous meeting, which is the trade off.

A pairing usually beats a single interval. One notification the day before for all day entries, and one shortly before the start for timed events, covers both shapes without producing noise. Remember that those two live in different lists, so the pairing is set in two places on the same screen.

For a calendar full of events that need travel, the reminder interval is the wrong tool on its own, because a fixed number of minutes cannot know how far away the next location is. That gap is what departure alerts based on a measured route address, and the mechanics are described under Travel time.

What to change first

Open Settings in a browser, work down the list of calendars one at a time, and set both Event notifications and All day event notifications on each, because neither inherits from the other or from the account. Then check the preference that limits reminders to accepted events, since it overrides everything else. If the Mac is where the calendar is actually read, set the alert defaults there to match rather than to duplicate, which is the point at which a desktop calendar such as Caltimate is doing the announcing rather than a browser tab.