WEEKLY INVITATION CHECK — a blank planning note, not an imported calendar 1. PURPOSE What must stay fixed: a regional local clock time OR elapsed hours? Choice: Reason: 2. REGION AND FIRST START Regional timezone name (not just an abbreviation or country): First local date and time: Corresponding UTC start and explicit offset, confirmed by organiser: 3. TRANSITION-WEEK CHECK Local and UTC start immediately before a clock change: Local and UTC start immediately after it: If the requested local time is missing, skip it or agree a separate replacement? If it repeats, which occurrence is intended? Record its UTC start: Who confirmed this choice, and when? 4. END AND EXCEPTIONS Duration/end condition (a separate question from spacing between starts): End date or occurrence count: Agreed exclusions or replacement dates: Recheck date if regional rules change: BEFORE SENDING Verify both transition-week occurrences in the actual calendar service. Do not infer a provider's behavior from FortuneLeaf's generated examples. Resolve starts before checking overlaps and the time left in the day. Keep this note locally. It is not an ICS file and this download sends no calendar. Method: https://fortuneleaf.app/blog/wall-clock-elapsed-time.html#weekly-starts