Practical guide
Calendar Reminders: Start, End or a Fixed Time?
Choose the alarm anchor, compare five worked results after an event changes, and separate an all-day midnight reminder from additional alarm repetitions.
On this page
Choose what the reminder should follow
A reminder “30 minutes before” needs an anchor. Before the start, before the end and at one fixed time are different instructions. If a workshop moves or grows longer, those instructions can stop producing the same reminder time. Read the event fields and the alarm’s TRIGGER together before changing the offset.
RFC 5545 gives TRIGGER a default DURATION value relative to the associated event’s start. RELATED=END changes the relative anchor to its end. A DATE-TIME trigger instead records an absolute UTC date and time. [1]
Read value type, anchor and sign as separate choices
TRIGGER:-PT30M means thirty minutes before the start. The omitted RELATED parameter defaults to START; omitting it does not make the trigger absolute. TRIGGER;RELATED=END:-PT30M means thirty minutes before the end. TRIGGER;RELATED=END:PT5M means five minutes after the end: the positive sign is implicit. [1]
For an end-relative alarm in a VEVENT, the associated event must supply DTEND, or both DTSTART and an event DURATION. A start-relative alarm needs DTSTART. Do not invent an end from the title or silently treat a missing end as the start. [2]
TRIGGER;VALUE=DATE-TIME:20270115T083000Z stores 15 January 2027 at 08:30 UTC. Its value must use UTC, and RELATED is not valid with this value type. A changed event start does not turn that stored time into a new “30 minutes before” calculation. For a recurring event, an absolute trigger still applies only at that specified instant, plus any explicitly defined alarm repetitions. [1]
Compare the same activity before and after a change
The original fictional workshop starts at 09:00Z and ends at 10:00Z on 15 January 2027. The revised workshop starts at 10:00Z and ends at 12:00Z on the same date. Using UTC keeps this comparison about the alarm anchor; it introduces no daylight-saving transition.
| Choice | Alarm properties | Original trigger time | After the event changes | What moved |
|---|---|---|---|---|
| 30 minutes before start | TRIGGER:-PT30M | 08:30Z | 09:30Z | The default anchor is DTSTART; the alarm follows the changed start. |
| 30 minutes before end | TRIGGER;RELATED=END:-PT30M | 09:30Z | 11:30Z | The alarm follows the changed end, not a fixed gap before the start. |
| 5 minutes after end | TRIGGER;RELATED=END:PT5M | 10:05Z | 12:05Z | A positive duration follows the anchor rather than preceding it. |
| One fixed UTC time | TRIGGER;VALUE=DATE-TIME:20270115T083000Z | 08:30Z | 08:30Z | The trigger stores one instant; moving the event does not recalculate it. |
| Before start, then two extra reminders | TRIGGER:-PT30M
REPEAT:2
DURATION:PT5M | 08:30Z, 08:35Z, 08:40Z | 09:30Z, 09:35Z, 09:40Z | REPEAT counts two additional triggers, with five minutes between them. |
Subtract thirty minutes from the original start to get 08:30Z. Subtract thirty minutes from the original end to get 09:30Z. After the change, repeat those two calculations using 10:00Z and 12:00Z: the results become 09:30Z and 11:30Z. The fixed 08:30Z trigger never asks for either new endpoint.
When an event end is represented by DURATION instead of DTEND, locate it on the event before calculating an END trigger. The DURATION inside VALARM has a different job: it is the interval between additional alarm triggers. [3]
Inspect five complete alarm components
Each block is a complete fictional DISPLAY VALARM component for the comparison above. It belongs inside its associated VEVENT; it is not a standalone calendar import file. DISPLAY requires a DESCRIPTION as well as ACTION and TRIGGER. The repeat example also includes both REPEAT and DURATION. [2]
30 minutes before start
BEGIN:VALARM
TRIGGER:-PT30M
ACTION:DISPLAY
DESCRIPTION:Fictional before-start reminder
END:VALARM
30 minutes before end
BEGIN:VALARM
TRIGGER;RELATED=END:-PT30M
ACTION:DISPLAY
DESCRIPTION:Fictional before-end reminder
END:VALARM
5 minutes after end
BEGIN:VALARM
TRIGGER;RELATED=END:PT5M
ACTION:DISPLAY
DESCRIPTION:Fictional after-end reminder
END:VALARM
One fixed UTC time
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:20270115T083000Z
ACTION:DISPLAY
DESCRIPTION:Fictional absolute reminder
END:VALARM
Before start, then two extra reminders
BEGIN:VALARM
TRIGGER:-PT30M
ACTION:DISPLAY
DESCRIPTION:Fictional repeat reminder
REPEAT:2
DURATION:PT5M
END:VALARM
Use the first block for a reminder following the start, the second for one following the end, and the fourth for one intentional fixed instant. Compare the third when the reminder should follow completion rather than precede it. These alternatives explain the format; no calendar-account import or actual notification delivery is claimed.
Separate an all-day anchor from repeated notifications
For a DATE-valued event, RFC 5545 places a relative trigger’s anchor at 00:00:00 on the specified date in the user’s configured time zone. If no configured zone can be found, the rule uses 00:00:00 UTC. An all-day start on 15 January with TRIGGER:-PT30M can therefore produce a reminder at 23:30 on 14 January in that configured zone. The earlier notification date does not itself mean the all-day event moved. [1]
Read REPEAT:2 as two additional triggers after the initial one. With DURATION:PT5M and an initial 08:30Z trigger, the original sequence is 08:30Z, 08:35Z and 08:40Z. There are three trigger times for the one alarm, not three workshop events. Both REPEAT and DURATION must be present when defining the repetition; REPEAT without its interval is not a complete repeating-alarm definition. [4] [2]
An alarm interval such as PT5M is five elapsed minutes. The standard separately distinguishes nominal days or weeks from hours, minutes and seconds; do not replace a day-based rule with twenty-four hours merely because an ordinary day happens to match. Use the existing event-duration guide when a real case crosses a clock change. [5]
Record the expected time before checking the calendar app
Keep a retained export or a copy of the relevant non-sensitive fields. Record DTSTART, the explicit end or event duration, and the entire TRIGGER property with its parameters. Calculate the first trigger, then list any additional repetitions. Name the time zone used for a DATE-valued event. This record lets you distinguish a field difference from an app setting.
In your actual calendar, inspect the event’s supported reminder setting and compare the imported or re-exported fields when available. Record the application and version, the intended trigger time and the observed result. A correct representation is not evidence that a particular app imported it unchanged or delivered a notification. RFC 5545 explicitly leaves alarm delivery to the calendar user agent and notes that implementations may ignore or seek confirmation for imported alarms that users did not set themselves. [2]
Download the worked comparison and blank check record (TXT)
The text record contains the five component excerpts and their filled time results. Use the import guide if the unresolved problem is a copied file, a subscription or an apparent duplicate; changing a reminder offset does not resolve those different questions.
Try three complete reminder decisions
These original fictional checks use the guide’s stated dates, fields and assumptions.
Case 1
A workshop is moved from 09:00Z–10:00Z to 10:00Z–12:00Z. Its trigger is TRIGGER;VALUE=DATE-TIME:20270115T083000Z. Should the reminder automatically become 09:30Z?
Show answer and explanation for case 1
No. The absolute trigger remains 08:30Z on 15 January 2027.
The trigger stores one UTC instant rather than a duration relative to DTSTART. A genuine thirty-minutes-before-start instruction would use TRIGGER:-PT30M and would move from 08:30Z to 09:30Z. Choose the intended anchor before changing fields.
Case 2
An all-day DATE start is 15 January 2027. A negative thirty-minute START trigger produces 23:30 on 14 January in the configured zone. Does this alone prove the event shifted one date?
Show answer and explanation for case 2
No. That notification follows the midnight anchor for the DATE-valued start.
RFC 5545 places the relative DATE trigger at 00:00 in the user’s configured zone, or UTC if no configured zone is found. Subtracting thirty minutes reaches the preceding evening. Check the actual event date separately before altering DTSTART.
Case 3
The first alarm is 08:30Z and its properties include REPEAT:2 and DURATION:PT5M. Are there two notifications total, or three separate workshop events?
Show answer and explanation for case 3
The defined alarm has three trigger times: 08:30Z, 08:35Z and 08:40Z.
REPEAT counts additional triggers after the first. DURATION is the five-minute gap inside VALARM, not the workshop length. The repetition describes one alarm associated with one event; notification delivery still needs checking in the actual app.
Sources and further reading
- RFC 5545 §3.8.6.3 — TriggerRelative and absolute triggers, sign, default START, end requirements, DATE midnight and fixed alarms in recurring events.
- RFC 5545 §3.6.6 — Alarm componentRequired DISPLAY properties, event association, repetition, delivery and treatment of imported alarms.
- RFC 5545 §3.8.2.5 — Duration propertyEvent duration and alarm repetition interval have different roles.
- RFC 5545 §3.8.6.2 — Repeat countThe repetition count excludes the initial alarm trigger.
- RFC 5545 §3.3.6 — Duration valueNominal days/weeks versus elapsed hours/minutes/seconds and signed durations.