GUIDES · BETSLIP DOCTOR
What should I verify when a club event time is shown in another timezone?
Check the full date, the displayed clock time, and the event's named timezone together. The recorded event model carries exact start and end instants as well as a separate IANA timezone name, so the label matters when comparing it with your own calendar. Do not assume the same clock hour in another zone or rely on a fixed offset alone. The backend source does not establish how every client renders local time or sends reminders.
For Club members and creators arranging community events · Updated
Read the date, time and timezone as one description
An event time is more than a number on a clock. The event data keeps a start instant and a named timezone, so make sure the date and timezone label belong to the displayed time you are checking.
When comparing two calendars, convert from the named zone for that event and for your own location. Seasonal clock changes can make a remembered hour difference unreliable.
Check the latest event details before making plans
If the event is available in your current BSD experience, check its latest start time, end time and timezone label. The event response includes the time data and a revision, so an updated event can have newer details than an earlier view.
The recorded source does not promise a particular local-time display, automatic calendar conversion, or reminder delivery. Compare the values your client actually shows with your own calendar.
Do not infer the event zone from a fixed offset
A named timezone identifies the region's time rules; a UTC offset is only the difference at a particular date. Use the event's timezone label rather than assuming that a remembered offset remains the same all year.
If the date, local time, or zone is missing or inconsistent, do not guess which one the organizer intended.
Hypothetical: checking a cross-zone event
Imagine a club event is shown at 7:00 PM in its named timezone. A member in another region checks the event date and zone, then compares the converted time with the member's own calendar. The member does not assume that 7:00 PM is local in both places or rely on a fixed seasonal offset.
Related questions
Should I use the event timezone or my local timezone?
Use the event's named timezone to identify the scheduled time, then compare it with your own local calendar. Keep the date attached to the conversion.
Will BSD automatically convert the event time for every device?
The cited backend source returns a start instant and timezone label but does not establish how every client renders local time or sends reminders.