Using Calendar for recurring events and reminders
Creating recurring events and reminders in elementary OS's Calendar gives a weekly school run, shift roster, training session or monthly commitment one reliable entry. The app keeps the pattern visible in its agenda while allowing a single meeting to be adjusted when plans change. Its usefulness comes from treating the event, its repetition rule and its alert as related but separate pieces of information.
A recurring event answers “when does this happen regularly?”, while a reminder answers “when do I need to notice it?”. Separating those functions makes it easier to choose useful alert times without moving the appointment itself. It also prevents one busy calendar from filling the agenda with duplicate copies of the same commitment.
For Australian users, the details matter because schedules often combine school, work, sport, shopping and appointments across different suburbs. Sydney, Melbourne, Brisbane, Perth, Adelaide and Canberra each have their own transport rhythms, while state public holidays and school terms can interrupt an otherwise regular routine. Calendar can absorb those variations, provided each event has the right date, time zone, recurrence and alert.
Choose where each event belongs
Before creating anything, decide which calendar should receive the event. Calendar can keep entries on the computer and connect to compatible online accounts for synchronisation. A local calendar is useful for private reminders, although it will not automatically appear on a phone. A synchronised calendar is better when an event needs to travel between the desktop and another device, but the account must grant permission to add or change events.
Google Calendar is familiar to many Australian households, Microsoft 365 calendars are common in workplaces, and Nextcloud provides a self-hosted option for organisations that want greater control. Compatibility depends on the elementary OS release, the account provider and the authentication method available. Check the calendar list after connecting, because an imported calendar may be read-only. Events cannot be saved reliably to a source that only permits viewing.
Use separate calendars for work, family, community activities and personal commitments. This makes shared views cleaner and reduces accidental invitations, particularly for households that coordinate school pickups, medical appointments or a tradie's visit. Colour and calendar membership can also help distinguish a Coles or Woolworths shift from football training without putting every detail in the event title.
Calendar providers may store information outside Australia. For an Australian small business or community organisation handling client or member information, the Privacy Act 1988 and Australian Privacy Principles may apply to the provider or organisation involved. Sensitive notes are better kept out of synchronised event descriptions. If privacy is important, compare the provider's Australian data-handling information with any self-hosted service before importing a large calendar.
Create a recurrence that matches the real pattern
Open Calendar and start a new event with the add button. Give it a name that will be recognisable in a notification, such as “Swim training” or “Pay electricity bill”, then select its calendar. Set the start and end times, add a location if it helps, and use the all-day option for activities whose exact duration does not matter. An all-day event occupies the date without being tied to a particular hour.
The repeat control defines the pattern. Common choices include daily, weekly, monthly and yearly recurrence. A weekly event can follow the selected weekday, while a monthly event follows a date or a named day such as the second Tuesday. Where the installed version exposes more detailed interval settings, those can cover patterns such as every second week. If an unusual rule cannot be expressed in the editor, importing an iCalendar file from another calendar service may preserve it better than copying the same series by hand.
Choose an end condition deliberately. “Never” is appropriate for a school term that is reviewed each year, while a fixed number of occurrences or an end date suits a temporary arrangement. Public holidays are not automatically excluded from weekly or monthly patterns. A council meeting, community committee session or regular club night may therefore need a one-off exception when the relevant Australian state or territory observes a public holiday.
Preview the series after saving it. Scroll through the agenda or month view and check that the next few entries land on the intended dates. Monthly recurrence deserves particular attention: an event set for the 31st may be skipped in shorter months, depending on how the calendar service handles that rule. A date early in the month often behaves more consistently across months.
Add reminders that fit the day
Open the event and look for the reminder or alert control. Choose how far ahead the notification should appear. A short warning works for a train connection or a meeting in another part of Melbourne, while a longer warning gives useful time to collect a school bag, prepare work clothes or cancel a shift. The available lead times depend on the version of elementary OS and the connected calendar provider, but the event itself should remain at its correct time even if the alert is changed.
Keep the wording specific. “Leave for football” communicates more than “Football”, especially when several family members receive the same reminder. For an appointment involving travel across a busy Sydney road corridor, a second preparation event may be more useful than adding every stage of the journey to the appointment itself. It also keeps the recurring travel rule separate from a reminder that might only be needed on certain dates.
Alerts are delivered through elementary OS's notification system, so the operating system's notification and sound settings must allow them through. Check that Calendar is enabled, the alert volume is suitable and any quiet mode or notification suppression is switched off at the expected time. A muted desktop is particularly easy to overlook when most other household activity happens on a phone.
A synchronised account can carry the alert to a mobile device, but each device handles notifications independently. Google Calendar or Outlook notifications on an Android phone or iPhone need their own account, sync and permission settings. Do not assume a desktop alert proves that a phone is ready to warn you. Test the complete path before relying on it for a shift, medical appointment or school collection.
Change one occurrence without breaking the series
Recurring events need a clear editing choice. When an occurrence is opened, elementary OS may offer to change “this event”, “all events” or “this and future events”, although the wording varies by release and provider. Choose deliberately. Changing every event to move one football session would be surprising; changing only the current occurrence preserves the rest of the series.
Deleting a single occurrence is useful when one meeting is cancelled but the regular commitment continues. Deleting the entire series removes every remaining instance, so pause and read the confirmation before confirming. Some services create an exception for the altered occurrence and then synchronise that exception to other devices. A local copy and an account-based copy may behave differently, making it important to know which calendar actually owns the series.
Time zones deserve care when travelling between Australian cities. New South Wales, Victoria, South Australia and Tasmania change their clocks during daylight saving, while Queensland, Western Australia and the Northern Territory do not; Canberra follows the eastern states' pattern. A recurring meeting set in Sydney time may therefore occur at a different clock time after travel to Brisbane or Perth. Calendar may retain the original time zone, convert it to the current one or ask how to handle the change, depending on the account and event settings.
For all-day events, focus on the date rather than the displayed clock time. This matters for interstate travel, international appointments and events beginning late at night. For timed events, decide whether the meeting should remain tied to its original time zone or follow the traveller's current location. The first is usually appropriate for a recurring online meeting; the second can be useful for a temporary appointment involving someone in another state.
Keep events and alerts working across devices
Reliable syncing starts with a writable account and an intentional choice of calendars. After connecting Google Calendar, Outlook or a compatible CalDAV service such as Nextcloud, select the calendars that should appear and confirm that changes can be written. Avoid subscribing twice to the same account, since duplicate sources can produce two copies of every recurring event and two sets of alerts.
If an event is missing, check the calendar list first, then refresh or reopen Calendar and confirm that the device is online. Regional and rural connections can make synchronisation slower, but a reminder already stored on the device should still be able to fire. If it does not, verify the system date, time and time zone before changing the event itself. Automatic time settings normally handle clock changes, yet manual overrides can leave Calendar calculating alerts against the wrong time.
Notification problems and synchronisation problems are not always the same. A synced event may be present while the desktop notification is blocked by system settings. Conversely, a local event may display correctly while failing to reach a phone because the account is disconnected. Testing each layer separately makes troubleshooting faster: first the event, then the account, then the desktop alert, and finally the mobile notification.
Imported iCalendar files and manually recreated entries can overlap. When one comes from a colleague, club administrator or community group, compare it with existing calendars before adding it. A brief look at the recurrence and alert settings prevents duplicate school events, overlapping work shifts or repeated club reminders. These small checks preserve trust in the agenda and keep attention focused on the commitments that genuinely need action.
A dependable Calendar setup is built around a few clear choices. Each recurring event should live in the correct calendar, follow a rule that reflects reality, and carry an alert with enough warning for the day it describes. Individual exceptions should alter only the occurrence that needs them, while synchronisation should keep the desktop and mobile views consistent.
The essential habit is to treat recurrence, reminders and time zones as distinct controls. When those pieces agree, Calendar becomes a calm record of regular commitments rather than a source of duplicated alerts, missed appointments or accidental changes to an entire series.
