Daily reminder in Google Calendar for the things you keep forgetting

The thing that needs remembering every morning is usually small. Take the tablet. Log yesterday's hours. Water the plants. Check whether the overnight build passed. It is the kind of item that never justifies a project management tool, and that is exactly why it keeps getting forgotten.

Google Calendar can carry it, but the word reminder now maps onto at least four different mechanisms inside the product, and they behave differently at nine in the morning. Picking the wrong one is why a daily reminder was set up months ago, appeared for a while, and then quietly stopped mattering.

Four mechanisms, and only one of them survives being ignored

Before changing any settings, it helps to see the options side by side, because the differences are behavioural rather than cosmetic.

Mechanism	Where the nudge appears	Repeats	What happens if it gets ignored
Repeating event with a notification	Pop-up or email, a set time before the start	Yes, up to 730 occurrences	It slides into the past and vanishes
Task with a date and time	Notification at that date and time	Yes	It stays pending and rolls forward
Task with a deadline only	Notification at 9 AM local time on the deadline day	Yes	It stays pending and rolls forward
Agenda notification	One email at the start of the day, listing events	Daily by definition	Nothing, it is a digest and not an alarm

The fourth row is the one people mean when they say the calendar already emails them every morning, and it is also the one that cannot carry a task. The first two rows are the real choice, and the deciding factor is the last column.

An event is an answer to the question of when something happens. Once that time has passed, the event has done its job and the calendar moves on. A task is an answer to the question of whether something is done. An uncompleted task does not go away, and Google Calendar surfaces every uncompleted task from the last 365 days in a Pending tasks list at the top of the day being viewed. For a morning habit that genuinely has to happen, that difference is the whole decision.

The repeating event, and the two reasons it goes quiet

Setting up a daily event is the obvious first attempt. Create an event, click the dropdown next to "Does not repeat", choose Daily, and decide when the repeat ends. Two details then decide whether it keeps working.

The first is the occurrence limit. Repeating events in Google Calendar have a limit of 730 occurrences, which for a daily event works out to roughly two years. A reminder created without an end date does not run forever; it runs until that ceiling and then stops, on an ordinary Tuesday, with no announcement. Anyone whose daily reminder disappeared without explanation after a long stretch should check the last date in the series before assuming a bug.

The second is all-day events. It is natural to make a daily reminder an all-day event, since nine in the morning is not really a meeting. But all-day events have their own notification settings, separate from timed ones, in the calendar's settings panel. A calendar can be configured to give timed events a pop-up ten minutes before and to give all-day events nothing at all, and that combination produces exactly the symptom of a reminder that exists on the grid but never speaks. The fix is to open the calendar itself from the list of owned calendars in Settings, then look at the "All-day event notifications" block rather than at the event.

There is a third, quieter failure. Calendar-level settings determine notifications for new events unless a specific event overrides them, so a reminder created before those defaults were changed keeps the older behaviour. Editing the series and adding the notification explicitly is more reliable than adjusting the default and hoping it propagates.

The task route, and what it actually does at 9 AM

Tasks live in the same Create menu as events, under Task, and the settings are deliberately different from an event's. A task takes a start date and time, an optional deadline, a task list, and a set of advanced options covering colour, whether the time counts as Free or Busy, and its visibility to people the calendar is shared with. Work and school accounts additionally get Do not disturb and Automatically decline meetings.

The notification behaviour is worth learning precisely, because it explains most complaints about tasks being silent.

A task with a date and a time notifies at that date and time. A task with a date but no time notifies at 9 AM. A task carrying a deadline produces a notification to complete it on the day of the deadline, at 9 AM in the local time zone. So the morning nudge that people are usually trying to build already exists as a default: a dated task with no specific time arrives at 9 AM without any configuration at all.

To make it recur, pick the date and time and then choose Repeat. Two constraints apply. A task with subtasks cannot repeat, which rules out using one parent task as a morning checklist with items underneath. And a recurring task cannot be given an end time, so it occupies a point rather than a block. In Calendar, a certain number of upcoming instances of a repeating task appear on the grid, and further ones are added as time passes, which is a different model from the fixed series an event produces.

One more property makes tasks the stronger choice for habits: a task only leaves the list when it is marked complete. The Pending tasks control gathers every uncompleted task from the last year into one place, so a morning item that was skipped on three days is visible as three skipped days rather than three empty slots in the past.

The daily agenda is an email, and it only knows about events

A separate feature is often mistaken for a reminder system. Google Calendar can send a summary of the day at the start of the day, and Google's own developer documentation lists it as one of the notification types alongside event creation and cancellation.

Agenda: A list of all the events on the user's calendar, sent at the start of the day. Source: developers.google.com

Two limits come with it. The delivery table in the same documentation shows that the agenda notification is available by email only, with no pop-up option, unlike reminders on individual events which support both. And it lists events, not tasks, so a task-based morning habit will not appear in it.

The setting sits under the calendar's Other notifications section, where each category, such as changed events or event responses, can be set to Email or None. For someone who wants one message in the morning rather than a stream of alerts through the day, this is the right control to reach for. It works as a briefing, not as an alarm.

Where the notification gets lost

Delivery, not configuration, is where most daily reminders actually fail, and four facts narrow the search quickly.

Notification settings are personal to one account. Nobody who shares the calendar, and nobody with permission to change its events, can alter them, and changing them does not affect what anyone else receives. So a reminder that works for a colleague and not on this account is a settings problem on this account.

Desktop notifications require Google Calendar to be open in the browser. If the tab gets closed at the end of the day, a nine in the morning pop-up has nothing to appear from. On a Mac this is the single most common cause, and it is also the reason email or a native application is a steadier channel for a habit than a browser pop-up.

The browser itself has to allow it. Notifications for calendar.google.com need to be permitted in the browser's site settings, and in Chrome that means adding the site under the list allowed to send notifications. Snoozed notifications are a Chrome-only feature, which is worth knowing before building a routine around snoozing.

Finally, there is a setting that suppresses notifications for events that have not been accepted. A checkbox in the notification settings restricts alerts to events that were answered Yes or Maybe, and while it is on, an event created by someone else and left unanswered stays silent. That rarely affects a self-created daily reminder, but it explains a great deal of missing noise around recurring team events.

When the same reminder has to reach more than one person

A daily reminder that only one person needs is a settings question. A daily reminder that a team needs is a different problem, and the mechanisms diverge sharply.

Because notification settings belong to the account rather than to the calendar, a shared calendar carrying a daily item gives everyone the item and nobody a guaranteed alert. Each person decides, on their own account, whether that calendar notifies them and how. There is no way to push a notification preference onto a colleague, and that is deliberate.

An event with guests behaves better, since each guest gets the event on their own calendar and their own default notifications apply to it. The cost is that every change to the series generates traffic for everyone invited, so a daily event with six guests is a daily line in six inboxes if any of them have email notifications for changed events switched on.

Tasks are the weakest option here, because a task in Google Tasks belongs to one account's list. Assignment exists, but only inside specific surfaces: group tasks in a Chat space, and tasks assigned in a Google Doc for eligible Workspace accounts. Neither is reachable from the calendar grid. For a recurring team obligation, the durable pattern is a repeating event that blocks the slot, plus a task on each person's own list for the part that has to be marked done.

Picking between an event and a task, in one question

Ask whether the item has a duration or a state.

Something that occupies time, needs to stop other people booking over it, or belongs in a place is an event. A stand-up, a medication that has to be taken at a specific hour alongside a meal, a daily call. Give it a timed repeat, check the notification on the series itself, and note the end date so the 730-occurrence ceiling is a decision rather than a surprise.

Something that is either done or not done is a task. Logging hours, filing receipts, replying to yesterday's messages. Create it with a date, let it notify at 9 AM, set Repeat, and let the Pending tasks list do the accounting. If it also needs to defend a slot in the day, a task can be marked Busy in its advanced settings, which gives it the blocking behaviour of an event without giving up the completion state.

Where a desktop calendar helps is the step before either of those: writing the thing down at the moment it comes to mind, without opening a form. The Entering events walkthrough covers reading an ordinary sentence, repeat wording included, straight into a dated item. Which mechanisms a given calendar surfaces on the Mac side is listed under Features.

What to change first

Open the calendar's own settings and look at "All-day event notifications" before touching anything else, because a silent all-day reminder is the single most common version of this problem. Then move any item that has to survive being skipped from an event to a dated task, and let its 9 AM default do the work.

If the friction is in writing the item down rather than in the alert, Caltimate takes a spoken or typed sentence on a Mac and files it with its repeat and its alert already set.