Skip to content
Interface language: English
Design / Signal

Every other Tuesday, but by which clock? Designing recurring dates

Design recurring appointments with a clear rule, time zone, exceptions and edit scope. Check the actual dates before changing one event or a series.

Article language: English

A baker divides warm bread in a kitchen at night, with navy cupboards and a stone hearth.
In this article

“Every other Tuesday” sounds precise enough until one person writes down the second Tuesday of each month and another schedules meetings two weeks apart. For a while, both rules can point to the same day. The first date matches. Only later does it become clear that the participants are working from two different versions of November.

Designing recurring dates begins with the meaning of the repetition. One correct date does not prove that the series matches the intention. It needs a starting point, a rhythm, an end and rules for exceptions. Then there is the clock by which the meeting time is preserved. Otherwise it is easy to design a button that consistently repeats a misunderstanding.

Imagine a fictional screen-printing studio holding eight online consultations. The first is on Tuesday, 3 November 2026, at 9:00 in Warsaw. The consultations continue every two weeks. One will be moved because the studio is taking a break, and some participants join from Korea. The December adjustment must leave the other consultations intact, while a participant in Seoul needs to recognise their own time for every meeting.

First show the dates implied by the sentence

Instead of “Repeat: every other Tuesday”, use clear parts: every two weeks, on Tuesday, starting on the specified date. The user should understand that the start establishes the rhythm. Moving the first Tuesday by one week can shift every subsequent meeting, even though the fields “every two weeks” and “Tuesday” stay the same.

The preview of our example shows 3 and 17 November, 1, 15 and 29 December, then 12 and 26 January and 9 February 2027. That is eight occurrences including the first. Showing actual dates reveals the December meeting before anything is saved. A description of the rule alone does not show which holidays or breaks it may meet.

There is no need to display a huge calendar immediately. For eight consultations, a short list may be enough. For a long series, show the nearest occurrences and a way to inspect later ones, with a clear indication of what the preview covers. Three visible dates should not imply that the series ends at the third.

Google Calendar's recurring-event instructions guide people through choosing a frequency and an end to repetition. When an event is edited later, they must select which events in the series the change applies to. The rule and the scope of an edit are separate decisions.

In our product, the label “Eight meetings” should explain at once whether it includes the first one being entered. “Repeat eight times” might suggest nine dates: the initial one and eight more. A summary with a counted list removes that uncertainty better than an additional technical abbreviation.

An end set by date needs similar care. If we choose “through 9 February inclusive”, the final meeting should be recognisable in the preview. Do not show only the boundary date without explaining whether that day belongs to the series. When the start or frequency changes, recalculate the result before the user saves the setting.

The choice of control itself is discussed in designing a date field and calendar (in Polish). Here we add the meaning of the entire series to a correctly entered date. A convenient Tuesday picker does not answer whether consultations end after eight meetings or after eight weeks.

The organiser's time and the participant's time serve different purposes

For the studio, we choose a fixed local time in Warsaw. The organiser wants to start at 9:00. A participant in Seoul should see the corresponding moment in their own time zone, but their display setting should not independently move the whole series. Separate the rule's time zone from the zone in which someone views the dates.

Google Calendar's documentation on calendars and events says a recurring event needs one time zone in which its occurrences are expanded. It separately describes converting displayed results to a selected zone.

A clear description such as “9:00 Warsaw time” is enough on screen. When the zone is selected, the implementer needs an unambiguous representation. Do not permanently replace it with an offset of “plus one hour” if the rule must preserve local time after a clock change. The city name should correspond to the actual zone in use, not decorate a technically different setting.

Compare two test occurrences on either side of the autumn 2026 clock change. On Tuesday, 20 October, 9:00 in Warsaw corresponds to 16:00 in Seoul; on Tuesday, 3 November, 9:00 in Warsaw corresponds to 17:00 in Seoul. This is a conversion check for those two dates and zones. A fixed time for the organiser does not mean a fixed time for every participant.

If a user travels, show whether they changed only the view or the meeting rule. Switching to a phone in another zone can change how dates are displayed, but it should not silently change the studio's agreement. On returning to the settings, the zone used to generate the series must remain identifiable.

For working between Poland and Asia (in Polish), this has practical consequences for working hours. A participant should be able to view future dates in their own zone. It is not enough to convert the first and say the others will be the same. The most useful preview also covers the point where the difference between regions changes.

A December exception need not rewrite January

The studio wants to move the Tuesday, 29 December consultation to Wednesday, 30 December, while keeping 9:00 in Warsaw. The next should still fall on 12 January. The editing screen must name what is changing: this one meeting, not a new starting point for the two-week rhythm.

Aeneia conceptual photography

Google Calendar API's guide to recurring instances describes an exception as a change to an individual occurrence. Its original start field identifies it in the series even after it has been moved to another time. The meeting does not lose its identity simply because it was moved.

Our preview could show “30 December instead of 29 December”. That lets the participant recognise a move rather than mistake Wednesday for an extra meeting. The number of consultations remains eight. If the product allows a ninth to be added, that is a different action and needs a different message. An exception, an addition and a cancellation should not all share the label “Change date”.

When one meeting is cancelled, decide whether the number of planned consultations falls or the studio proposes a replacement. The calendar mechanism alone does not decide the terms of the service. In our example the organiser may specify another day, but the screen should not create one automatically without an agreed rule.

Similarly, a change “from this meeting onward” needs a clear boundary. If the time changes to 10:00 from 12 January, the November and December meetings should keep their descriptions. Before saving, show the date of the first meeting being changed and the new time. The word “future” depends on when it is read and does not sufficiently identify the scope.

If the time is adjusted without leaving the calendar, inline editing (in Polish) must include the choice of scope. Leaving a small field should not automatically change every meeting before the user specifies what the edit applies to. First show the proposed change and its scope; only then confirm the save. A small editor's speed does not justify hiding the effect.

A change to the whole series must account for existing exceptions. Does the December Wednesday remain, receive a new time or return to Tuesday? This is a decision to agree with the implementer before drawing the confirmation. Show the user the effect of the chosen option. A “Save all” button does not honestly resolve three different interpretations.

The same boundary applies when deleting: one occurrence, a specified later portion or the entire series. Cancelling the December consultation should not delete those in January. If the product offers undo, restoring it must restore the correct meeting and its identifiable link to the series. Creating a new event alongside it with a similar name may not restore the previous participants or their arrangements. That result needs a separate test.

A month is not a box with a fixed number of days

A second service variant has a consultation on the thirty-first day of each month. That is not the same as the last day of the month. When February is absent from the preview, the design should not choose on its own between the last day of February, the beginning of March and skipping the meeting. First the service needs a rule and a way of calculating dates that follows it.

RFC 5545 on recurrence rules states that generated invalid dates are ignored and are not counted as part of the set of occurrences. It also gives an example of skipping 30 February. This is behaviour of the iCalendar format, not an automatic policy for every service.

If the product offers “last day of the month”, show the actual ends of different months in the preview. If it offers “31st day”, name the consequence in months without one. Do not promise a meeting every month based on a rule that generates nothing in some months. The person is buying or planning specific dates, not an exercise in the length of months.

“Last working day” also needs a definition. Monday through Friday alone does not account for all studio breaks or local holidays. If the service calendar has its own exclusions, these should be visible in the result. A designer need not build that logic in a mock-up, but does need to know where dates shown as available come from.

Repeating a date does not reserve a resource

A sound rule can generate dates that conflict with the room or the organiser's availability. This is separate from understanding the recurrence. If saving requires every date to be checked, show the result even when only one of eight meetings is occupied. Do not call the entire series booked based on the first available Tuesday.

Evaluating AI calendar scheduling (in Polish) explores checking constraints and distinguishing a proposal from a reservation. Here the user chooses the rule. The preview should show its meaning, while the saved status should say which dates were actually accepted. A saved draft of a cycle may still require availability to be confirmed.

When the save result is unconfirmed, preserve a clear comparison of the existing meeting and proposed edit. For a partial operation, distinguish confirmed, rejected and unknown outcomes. A lost response after a connection failure does not prove that the save did not happen. Check the operation state and result against a reliable source. If it cannot be confirmed, show the uncertainty and a way to investigate instead of starting a new operation that creates another set of meetings. Where the system safely supports retrying the same operation, preserve its identity and conditions according to its documentation; do not assume every service provides that guarantee. Stripe’s documentation on network errors and retries illustrates one specific mechanism, not a rule for every calendar.

After returning to the page, read the saved result again. Test one distinctive exception and its two neighbouring meetings. The moved Wednesday should remain Wednesday, while the following Tuesdays keep their rhythm. This quickly reveals whether only the preview or the actual series changed, and whether the edit included unintended dates.

Also explain what happens to earlier information after the change. Will participants receive a notification about one move or a new complete set of dates? In notification settings (in Polish), distinguish minor updates from information needed to take part. One edit should not look like eight separate invitations to a new service.

At Aeneia Design, the choice can be designed together with exceptions, confirmation and a description of the behaviour for the implementer. Bring one real rule and a case where it must be overridden. Comparing the date list before and after the edit will explain the most. The December Wednesday should remain a recognisable exception rather than silently moving the whole of January onto a new schedule.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear