Check The Date As Well As The Time
A schedule can look right while landing on the wrong day or lasting longer than expected. For each confirmed time, record the calendar date, named time zone and UTC offset. If the source gives two possible instants, leave the time unconfirmed rather than picking the more convenient one.
This fictional exercise uses supplied offsets for specific dates, not a live calendar or a captured AI run. Use a text-only conversation with no calendar connection. Do not send invites or change events for this exercise.
Get The Pack
Give the AI only the test input. Keep the review key separate, and retain the first response before asking for a correction.
Download comparison worksheet (.txt)
Review Three Scheduling Traps
| Case | Draft error | What the evidence supports |
|---|---|---|
| SCH-01 | Friday at 09:00 in Seoul | Friday 17:00 in Los Angeles on November 6 is Saturday, November 7 at 10:00 in Seoul. |
| SCH-02 | One confirmed New York time at 01:30 | November 1 at 01:30 can be 05:30 or 06:30 UTC. Ask which occurrence was intended. |
| SCH-03 | A one-hour New York handoff | 00:30 at UTC-04:00 to 01:30 at UTC-05:00 on November 1 spans two hours. |
In SCH-03, compare the corresponding UTC times, 04:30 and 06:30. Subtracting the local clock readings would miss the repeated hour. In SCH-02, neither candidate is confirmed, so calculating both does not resolve the ambiguity.
Compare Your Next Run
When the tool or prompt changes, repeat the same input and check each outcome separately. Keep the output and worksheet in an approved location. If you have no comparable previous run, record a baseline.
Return to the schedule practice pack or choose your next check.
For real appointments, verify time-zone conversions for the actual date using an up-to-date calendar, confirm ambiguous times with the organizer, and check recurrence and invite recipients before sending. Do not reuse the offsets from this example for other dates.