Multi-Location Studio Scheduling: One System That Works Across Timezones

Timezone errors in multi-location scheduling are the second most common member support complaint, after cancellation handling. They are entirely a software configuration problem — not a staff error. A studio that configures location-level timezones correctly in their booking platform eliminates the problem at the root.

Why Timezone Errors Happen in Multi-Location Studios

The error is almost always a configuration default, not a bug.

Most scheduling software defaults to a single timezone at the account level — set when the first location is configured. When a second location is added in a different timezone, the software continues to display times in the original account timezone unless the configuration is explicitly changed at the location level.

A studio based in Austin (CT) that opens a second location in Denver (MT) and doesn't update the timezone configuration presents Denver classes at the wrong time to Denver members. The 10am Wednesday class in Denver shows as 11am in the app. Members in Denver book the wrong slot or miss classes because the displayed time was an hour off.

The fix takes five minutes in any properly designed scheduling platform. But you have to know the configuration exists.

How Should Location-Level Timezone Configuration Work?

Each physical location should have its own timezone setting, independent of the account-level default.

In Zatrovo, each location record has a timezone field that governs how class times are displayed for members assigned to that location. When a class is created at a location, the display time is rendered in that location's timezone — not the account owner's browser timezone and not UTC.

In Mindbody, timezone configuration lives in the site settings for each business location. Multi-site accounts need to configure this per site. Mariana Tek handles timezone at the location level in their multi-location configuration. Glofox has had reported inconsistencies in timezone handling across locations — test explicitly.

The test: create a class at 10am local time at your Denver location. Log into the member-facing app as a Denver member. Verify that the class displays at 10am MT, not 11am CT or 9am PT.

How Do Member Location Assignments Work?

Every member account should have a home location assignment. The home location determines the default timetable view, the timezone for display, and (where relevant) which location's pricing and packages apply.

Location assignment best practices:

• Assign members to a home location at onboarding
• Allow members to browse and book at other locations without changing their home location
• Display cross-location class times in the local timezone of the class location, labeled explicitly

The member who wants to visit the Denver location while traveling from Austin should see Denver class times in Mountain time when browsing the Denver location — not Austin time. Most platforms support this if location timezone is correctly configured; the display for a visiting member typically inherits the location's timezone, not the member's home location timezone.

How Should Staff Scheduling Handle Timezones?

Staff-facing scheduling is a separate concern from member-facing booking display.

An instructor in Denver should see their schedule in MT, not in CT or PT. If the studio's management dashboard is set to a default timezone that doesn't match the location's timezone, instructors see incorrect times in their schedule views.

Configure staff timezone display at the user level or, where the platform supports it, inherit the location timezone for staff accounts assigned to that location.

For payroll purposes, hours worked must be recorded in the local timezone to comply with state labor laws. A shift that starts at 6am MT and ends at 10am MT is a 4-hour shift in Colorado, regardless of what timezone the payroll platform's clock is set to. Confirm your payroll software records in local time or converts correctly.

What Does Cross-Location Booking Display Look Like?

Cross-location booking — where a member books a class at a location other than their home location — is the highest timezone risk in a multi-location setup.

The booking confirmation email, the calendar invite, and the reminder message must all display the class time in the timezone of the class location, with that timezone explicitly labeled.

"Your class is at 10:00 AM" is ambiguous for a member whose device is set to a different timezone than the class location.

"Your class is at 10:00 AM MT at our Denver location" is unambiguous.

Most platforms generate booking confirmations from a template. Edit that template to include {class_time} {class_timezone} at {location_name} rather than just {class_time}. This single template change eliminates the ambiguity for every cross-location booking confirmation.

For the full multi-location operations framework, see the multi-location studio playbook and the scheduling software playbook for how timetable configuration affects member experience. For instructor availability management across locations, see the instructor availability management guide.