Scheduler sandbox
Made-up dataA request comes in. The engine books a tutor and a time in the student's own clock, or sends it to a person with a plain reason. Today in the demo is Mon 5 Oct; bookings open for two weeks.
What the engine did
- Request in: Algebra 1, 2 preferred times, zone Halifax.
- Zone: Halifax, UTC-3 today. Every time is turned into UTC before it is compared.
- Tutors for Algebra 1, fewest bookings first: Kesi (4 booked), Delphine (5 booked), Galen (5 booked), Jory (5 booked).
- Time 1: Mon 12 Oct, 6:00 pm your time, stored as 2026-10-12T21:00Z.
- Kesi: not working then (2:30 am Tue in Kolkata).
- Delphine: not working then (10:00 pm Mon in Lisbon).
- Galen: already has a session then.
- Jory: not working then (3:00 pm Mon in Denver).
- Time 2: Tue 6 Oct, 10:00 am your time, stored as 2026-10-06T13:00Z.
- Kesi: not working then (6:30 pm Tue in Kolkata).
- Delphine: not working then (2:00 pm Tue in Lisbon).
- Galen: not working then (6:00 am Tue in Los Angeles).
- Jory is free. This is the booking.
- Invitation written twice: Tue 6 Oct, 10:00 am for you in Halifax, Tue 6 Oct, 7:00 am for Jory in Denver.
Times and tutors tried
Time 1 Mon 12 Oct, 6:00 pm, stored as 2026-10-12T21:00Z
Time 2 Tue 6 Oct, 10:00 am, stored as 2026-10-06T13:00Z
Choose a slot to see its reason.
Result
Booked, invitation sent
Algebra 1 with Jory, Room N1.
Your copy, Halifax
Tue 6 Oct, 10:00 am
UTC-3
Jory's copy, Denver
Tue 6 Oct, 7:00 am
UTC-6
Stored once as 2026-10-06T13:00Z. Each reader sees it in their own clock.