Before anyone updates a calendar, a meeting schedule template should show exactly which occurrence would change, what stays unchanged, and which conflicts still need a decision. This original example expands four weekly meetings and compares two alternatives for one date. Every entry is proposed or fictional; no room has been booked and no update has been sent.
Expand the recurrence into four identifiable rows
Series SER01 contains four Tuesdays: October 20, October 27, November 3 and November 10, 2026. Each meeting is planned for 10:00–10:30 in America/New_York, with Room A and Dana as the proposed room and lead.
| Occurrence ID | Original date | Original local time | Proposed room | Proposed lead |
|---|---|---|---|---|
| SER01-01 | October 20, 2026 | 10:00–10:30 | Room A | Dana |
| SER01-02 | October 27, 2026 | 10:00–10:30 | Room A | Dana |
| SER01-03 | November 3, 2026 | 10:00–10:30 | Room A | Dana |
| SER01-04 | November 10, 2026 | 10:00–10:30 | Room A | Dana |
All four rows use America/New_York. Keep the named zone with each date when transferring the ledger to another document. This example does not convert the times to UTC or another region; verify actual calendar settings and any required conversion separately.
Four meetings of 30 minutes total 120 planned minutes. That is schedule duration, not attendance time multiplied by the number of invitees. Moving one 30-minute occurrence preserves that total unless the approved change also alters duration or cancels a meeting.
Stable occurrence IDs let a reviewer trace an exception back to its original row. Preserve SER01-03 and its original date and time even while considering another time for it.
Name the scope of the proposed change
Microsoft's Outlook guidance distinguishes changing one occurrence from changing a recurring series; available scope choices differ between new and classic Outlook. It also distinguishes events the organizer created from meetings received by invitation. Check the actual organizer and calendar version before making a change. Change an appointment, meeting, or event in Outlook
For this packet, the scope is SER01-03 only. The other three dates remain at 10:00–10:30 in Room A. Consider these alternatives:
| Candidate | Target | Proposed local time on November 3 | Proposed room | Status |
|---|---|---|---|---|
| E01 | SER01-03 | 11:00–11:30 | Room B | Proposed; supplied conflict exists |
| E02 | SER01-03 | 11:45–12:15 | Room B | Alternative; confirmation needed |
Both retain Dana as lead and America/New_York as the zone. E01 and E02 are competing proposals for the same occurrence. They are not two additional meetings and do not create a fifth or sixth weekly occurrence.
Check the room and the person against the same interval
The supplied comparison meeting X01 is fictional: November 3, 2026, 11:15–11:45, America/New_York, Room B, led by Dana.
| Candidate versus X01 | Shared room | Shared lead | Time evidence | Finding |
|---|---|---|---|---|
| E01 | Room B | Dana | Later start: 11:15. Earlier end: 11:30. | 15-minute overlap for both resources |
| E02 | Room B | Dana | E02 starts at 11:45, when X01 ends. | No interval overlap with supplied X01; buffers unknown |
E01's overlap runs from 11:15 to 11:30. Record both the room conflict and Dana's conflict against that interval. The two flags describe two affected resources, not 30 minutes of overlapping schedule time.
E02 eliminates the overlap with this supplied meeting. It does not prove Room B is available or that Dana can move immediately into the next meeting. Setup, cleanup, travel, other bookings and attendee availability remain unconfirmed. Do not replace “no overlap with X01” with “approved” or “conflict-free.”
Keep a decision record beside the candidates
Use the ledger to review options, then record the actual decision in a separate change form. Leave these actual-action fields blank until there is evidence:
| Actual-action field | Entry |
|---|---|
| Decision and selected candidate, or decision to retain the baseline | |
| Authorized organizer and approval reference | |
| Room availability check and required buffers | |
| Attendee availability confirmation | |
| Effective date, time, zone and room in the native calendar | |
| Calendar change completed by / evidence reference | |
| Update sent to / sent time / evidence reference | |
| Acknowledgment or remaining follow-up |
Reviewing E02 does not fill any of those fields. If it is later approved and implemented, keep the original SER01-03 row, link the decision to E02, and record the effective details. If it is rejected, retain the proposal and reason without altering the baseline.
A useful communication draft can be prepared before sending:
Proposed change for SER01-03 only: November 3, 2026, from 10:00–10:30 in Room A to 11:45–12:15 in Room B, America/New_York. The October 20, October 27 and November 10 occurrences remain unchanged. Room, buffer and attendee confirmations are pending. This proposal is not a confirmed calendar update.
After an authorized decision, revise the wording to match the effective calendar record and actual communication status. Do not send a proposal that reads like a completed booking.
Copy this prompt for the schedule packet
Prepare an original meeting schedule packet in US English as readable tables and a change form. Do not generate calendar feeds or ICS files, book rooms, send invitations or claim synchronization.
Series SER01 has four weekly Tuesdays in 2026: October 20, October 27, November 3 and November 10. Assign occurrence IDs SER01-01 through SER01-04 in that order. Baseline for every occurrence: 10:00–10:30, America/New_York, proposed Room A, proposed lead Dana. Preserve original dates and times. Four 30-minute occurrences total 120 planned minutes.
For SER01-03 only, show alternative E01: November 3, 11:00–11:30, Room B; and E02: November 3, 11:45–12:15, Room B. Both retain Dana and America/New_York. Other occurrences remain unchanged. These are competing proposals, not approved additional events.
Supplied fictional meeting X01 is November 3, 11:15–11:45, America/New_York, Room B, lead Dana. Show E01's 15-minute overlap from 11:15 to 11:30 for both room and lead. E02 has no interval overlap with X01, but actual availability, setup/travel/cleanup buffers, attendee agreement and organizer approval are TO CONFIRM. Do not call E02 conflict-free or approved.
Include a baseline occurrence ledger, single-occurrence change form, candidate/conflict matrix and blank actual decision, native-calendar update, communication and acknowledgment fields. Include a clearly labeled unsent proposal message for E02 stating the three unchanged dates. Distinguish proposed, approved and implemented states. Do not invent approvals or completed actions, change the whole series, add a fifth occurrence or convert zones without verified inputs. Note that actual organizer authority and calendar version must be checked before any native calendar action.
Put the exception review in one place
An optional prepared HTML review in NOS can place the four baseline rows beside E01, E02 and the conflict evidence. NOS supports saving and rendering HTML. Keep the approved native calendar and decision records authoritative; selecting a review view does not book a room or send an update.
Explore NOS to present the prepared schedule review. The next useful action is a documented decision about SER01-03, with the other three occurrences still traceable.