CALENDAR REMINDER ANCHOR - WORKED REFERENCE Original fictional event: 15 January 2027, 09:00Z to 10:00Z. Revised: 10:00Z to 12:00Z. All five alternatives describe alarm COMPONENTS, not standalone calendar import files. Each VALARM belongs inside its associated VEVENT. These examples are not added to a live calendar. 30 minutes before start Original: 08:30Z; Revised: 09:30Z The default anchor is DTSTART; the alarm follows the changed start. BEGIN:VALARM TRIGGER:-PT30M ACTION:DISPLAY DESCRIPTION:Fictional before-start reminder END:VALARM 30 minutes before end Original: 09:30Z; Revised: 11:30Z The alarm follows the changed end, not a fixed gap before the start. BEGIN:VALARM TRIGGER;RELATED=END:-PT30M ACTION:DISPLAY DESCRIPTION:Fictional before-end reminder END:VALARM 5 minutes after end Original: 10:05Z; Revised: 12:05Z A positive duration follows the anchor rather than preceding it. BEGIN:VALARM TRIGGER;RELATED=END:PT5M ACTION:DISPLAY DESCRIPTION:Fictional after-end reminder END:VALARM One fixed UTC time Original: 08:30Z; Revised: 08:30Z The trigger stores one instant; moving the event does not recalculate it. BEGIN:VALARM TRIGGER;VALUE=DATE-TIME:20270115T083000Z ACTION:DISPLAY DESCRIPTION:Fictional absolute reminder END:VALARM Before start, then two extra reminders Original: 08:30Z, 08:35Z, 08:40Z; Revised: 09:30Z, 09:35Z, 09:40Z REPEAT counts two additional triggers, with five minutes between them. BEGIN:VALARM TRIGGER:-PT30M ACTION:DISPLAY DESCRIPTION:Fictional repeat reminder REPEAT:2 DURATION:PT5M END:VALARM OWN CHECK RECORD Event and date: ____ DTSTART and time representation: ____ DTEND, or event DURATION with DTSTART: ____ TRIGGER value type, RELATED/default and signed duration: ____ Predicted initial trigger: ____ Additional REPEAT count and alarm DURATION: ____ Actual app/version, preserved fields and observed notification: ____ Unresolved difference: ____