Before choosing how your booking app stores dates, agree what the booking means. Is it one shared moment, a class that starts at the venue’s local time, or an appointment arranged in the customer’s chosen time zone? That decision tells your team what must stay fixed when clocks change or someone travels.
For example, a weekly class advertised for 09:00 at its venue usually needs to keep that local start time. Someone joining from another country may see a different hour as the countries change their clocks on different dates. Write down the rule, show the zone clearly, and test the booking in both the customer’s and operator’s views.
Which time should stay the same?
Start with the promise you make to the person booking. These are three ways to define it:
One shared moment
A one-off consultation is confirmed for a particular instant. People can see that same appointment in their own local time. Changing the display zone should leave the appointment itself unchanged.
The venue’s local time
A recurring class is advertised for 09:00 in the venue’s named time zone. The recurring schedule follows that local hour, even when its relationship to UTC changes.
The customer’s chosen zone
An appointment is arranged using a zone the customer explicitly chooses. Record that choice and agree whether it anchors only this appointment or a recurring local-time schedule.
The third choice identifies whose local time matters. It still needs the same decision about a fixed appointment versus a recurring local-time schedule. A customer’s current device location and the zone chosen for a booking can be different.
What does the app need to remember?
UTC can identify when a confirmed appointment happens. A recurring schedule also needs its intended local time, named zone and recurrence rule where those define the promise. Saving only the UTC time of the first class does not explain what “every Tuesday at 09:00 here” means for the rest of the series.
For a recurring booking, preserve the rule people agreed to as well as the time of each occurrence.
A named zone such as Europe/Prague is different from a fixed offset such as UTC+01:00. The offset describes a relationship to UTC; it does not identify all the local-time rules that may apply later. IANA maintains time-zone data because political decisions can change boundaries, offsets and daylight-saving rules.
Ask your team to explain how the chosen meaning survives saving, reopening, editing and calendar synchronization. You do not need to choose a database format yourself. You do need to be able to read a saved booking and recognize the time rule you approved.
Plan your booking and calendar integration
We build custom software and connect applications through APIs. Bring an example booking, the calendars it must reach and the local-time rule your customers expect. We can discuss the application and integration work those requirements call for.
Discuss your booking integration
What should customers and operators see?
Show the date, time and zone together wherever someone makes a decision: the booking form, confirmation, account page and rescheduling screen. If you show both the venue time and the customer’s local time, label each one. A bare “09:00” leaves people guessing.
Agree how display preferences work when someone travels. For a confirmed one-off appointment, choosing another display zone should show the same instant at a different local hour. Moving the appointment is a separate rescheduling action. Make that distinction visible and confirm actual changes with the people affected.
Reminders and cancellation information need the same care. Define whether a reminder is sent a duration before the appointment or at a particular local clock time. Show any cancellation cutoff with its date and zone, and agree how rescheduling updates it. These are product rules to approve; the app must also be tested for actual notification delivery.
What happens when a local hour is missing or repeats?
When clocks move forward, some local times do not occur. When they move back, a local time can occur twice. A booking form that accepts a local date and hour needs agreed behavior for both situations.
Ask whether the supported product will reject the choice, request clarification, or apply a documented rule. In a repeated hour, establish which occurrence a confirmation means. Check recurring bookings separately from dates entered directly. The iCalendar standard describes these date-time distinctions, but that does not make one skip, shift or selection rule appropriate for every booking app.
Connected calendars may constrain the choices your app can support. Agree on behavior the whole system can preserve, then check the result in each calendar. Avoid approving a screen that offers a choice the calendar connection later changes.
Test the booking rule in the working app
Choose representative dates using the current rules for the zones you support. For each example, record the expected date, displayed time and zone for the customer and operator, plus the intended instant or recurring local-time rule. Include these situations:
- A normal one-off booking viewed by people in different zones, then viewed again after the customer changes their display zone.
- A weekly local-time series across a clock change, including a period when the customer’s and venue’s zones change clocks on different dates.
- A proposed booking in a missing local hour and one in a repeated hour, with the expected response made explicit.
- Rescheduling or cancelling one occurrence while keeping the rest of the series, followed by a separate whole-series change.
- Confirmations, reminders and cancellation information after those changes, including any failed or delayed notification handling the product supports.
- A booking sent to a connected calendar, read back, changed and cancelled, with the same meaning preserved on both sides.
Google Calendar’s documentation provides a concrete example of why these distinctions matter: its event model distinguishes single events, recurring series and exceptions. Your app may use another calendar. Verify its actual behavior rather than assuming all calendars handle a series or an individual occurrence identically.
A prototype can help people judge whether the labels and choices make sense. Saving, recurrence, reminder delivery and synchronization need the working application. For the wider approval process, see what to test before approving a business app redesign.
Write a booking-time policy someone can approve
Keep the agreed rules together in a short document. Name what anchors the booking, the named zone where relevant, how one-off and recurring appointments differ, and what each role sees. Add the missing-hour and repeated-hour behavior, the rules for changing one occurrence or a series, and how reminders and cancellation information follow a change.
When calendars are connected, name which system owns the booking and how conflicting updates are resolved. Assign someone to maintain time-zone data and recheck affected future bookings when rules or integrations change. Finish with the representative examples and their expected results. That gives the business owner a concrete basis for approval and the team a way to check later changes.
Booking time-zone questions
Is storing appointments in UTC enough?
UTC can identify the instant of a confirmed appointment. Where a recurring booking must keep a local hour, retain its intended named zone and recurrence rule as well. The first occurrence’s UTC time alone does not describe that promise.
Should travelling change an existing booking?
Changing the display zone should show a confirmed one-off appointment at the corresponding local time while preserving its instant. Rescheduling is a separate action. For recurring bookings, follow the explicitly agreed anchor rather than silently substituting the customer’s current location.
What should the app do with a missing or repeated hour?
Agree and test the supported behavior for both conditions, including what the customer sees and confirms. Check directly entered dates and recurring occurrences separately, and verify that connected calendars preserve the result.
What should we ask for before signing off?
Ask for the written booking-time policy and demonstrations of representative bookings in the working app. Cover both roles, clock changes, travel, occurrence and series changes, reminders and calendar readback. Record the expected dates, times and zones so the examples can be checked again.