Time-zone message checker

Made-up data

A made-up week of 7 tutoring sessions. The clocks went back in North America on the Sunday before. Pick a session to see its confirmation drafted in the student's own clock. Then break it, and watch which check fails and why.

Picking a session and breaking the draft need JavaScript. The first session's draft and its four checks read below without it.

Pick a session

MondayPia, Chemistry, New YorkMondayNia, Geometry, ChicagoInvitation written last weekMondayAna, Statistics, TokyoInvitation written last week; the clocks never change hereTuesdayHugo, Spanish, KolkataA half-hour offsetWednesdayWren, World history, LondonNo local time in the invitationFridayFinn, Algebra, SydneyA different day in UTCFridayEsme, Biology, Los Angeles

The draft

Stored: Monday, 23:00 UTC
The student's clock: Monday, 6:00 p.m.
New York time (UTC-5)
The invitation: Says Monday, 6:00 p.m.

Hi Pia,

Your tutoring session is booked.

Course: Chemistry

Day: Monday

Time: 6:00 p.m.

Time zone: New York time (UTC-5)

See you then.

Break it

The four checks

All four checks passed. The draft waits for a person to read it and send it.

1. The time matches the invitation
Passed. The message says Monday, 6:00 p.m. The invitation and the time worked out again from UTC agree.
2. It has a day, a time and a time zone
Passed. It gives Monday, 6:00 p.m. and the zone: New York.
3. Nothing can send it
Passed. There is no send button and no sending code. The draft waits for a person to read it and send it.
4. A zone on file is labelled and named
Passed. Not needed here: the invitation gave the local time, so no zone on file was used.