International online theatre is scheduled twice: once as a single instant and once as many local experiences. A rehearsal, livestream or hybrid performance begins at one moment, but every participant reads it on a different clock. The practical answer is to fix one canonical time—normally UTC—and to publish local times alongside it, with explicit time-zone names and dates, rather than relying on an unqualified clock time.
This is not only an administrative detail. Online theatre depends on split-second coordination: performers wait for a cue, a technician opens a waiting room, a translator joins a breakout room, and an audience arrives for a live start. If the published time is ambiguous, the production can lose the shared moment that makes networked performance feel live. Scheduling therefore belongs to production dramaturgy, not only to the box office.
Start with a canonical instant
A time zone is a region whose local clock follows a particular offset from Coordinated Universal Time (UTC), together with any seasonal daylight-saving rules. An offset alone, such as UTC+01:00, describes a clock difference but not the rules that will apply on another date. For international work, the safer label is an IANA time-zone identifier such as Europe/London, America/New_York or Asia/Tokyo, because these identifiers encode the local rules, including daylight saving.
Use UTC as the canonical reference for the production schedule. UTC is a fixed standard, so it does not move when a country changes its clocks. Record the same event in at least three layers: the canonical UTC time; the official event time in the producing organisation, venue or festival time zone; and the local time for each participant or audience group that needs a separate call. The official event time matters for public communication, while participant local times matter for access and consent.
Name one person to own the master clock. In a small company this may be the stage manager or producer; in a larger international collaboration it may be a production coordinator. That person maintains the master calendar, checks conversion before publication, and is the single point of correction when a time changes. A shared document is useful only if someone is responsible for it.
Understand what platforms actually convert
Event and streaming platforms do not all treat time zones in the same way. Some are venue-centred, some are festival-centred, and some display times in the viewer’s local zone. The differences are practical, not cosmetic.
CrowdWork’s documentation for theatre events illustrates a venue-centred model: every event is scheduled in the theatre’s time zone, and an event taking place elsewhere is entered after conversion into that zone. The public page then labels the show in the theatre’s time zone (CrowdWork, ‘Scheduling an Event in Another Timezone’). The same source gives a New York theatre example: a 7:00 PM Los Angeles show is entered as 10:00 PM Eastern, and the public page labels it ’10:00 PM EDT’. That model is clear for a single venue, but an online audience may need the actual local time stated in words as well.
SparqFest separates the festival time zone from venue time zones and states that online events are governed by the festival time zone (SparqFest, ‘Times and Time Zones’). This distinction is useful for hybrid festivals, where an in-person screening and an online programme may need different display rules. Momice’s help centre describes an organiser-selected host time zone and automatic adjustment of programme times for participants, with a message when displayed times have been adjusted (Momice, ‘Streaming across different time zones’). Automatic conversion can help audiences, but it does not remove the need for a canonical record.
Teamup describes shared calendars as a way for collaborators in different time zones to see plans and add events to their own calendars (Teamup, ‘Schedule and Share Events Across Different Time Zones’). That is valuable for the production team, though a shared production calendar does not by itself settle public ticketing display or audience access.
| System or context | Documented pattern | Implication for online theatre |
|---|---|---|
| CrowdWork theatre events | Every event scheduled in the theatre’s time zone; externally located events entered after conversion; public page labels the show in the theatre’s time zone. | Good for venue-centred ticketing; add the event’s actual local time in the description or event name when an online audience may be confused. |
| SparqFest festival | Festival time zone and venue time zones are distinguished; online events are governed by the festival time zone. | Separate online and in-person display rules in hybrid festivals. |
| Momice programme | Organiser selects the host time zone; participant times adjust automatically, with a notice when adjustment occurs. | Useful for logged-in audiences; still publish a canonical time in the public programme. |
| Teamup shared calendar | Collaborators across time zones see shared plans and can add events to their own calendars. | Good for rehearsal and production teams; not a substitute for audience-facing time policy. |
Plan for daylight saving and date rollover
Daylight saving time is the seasonal clock change adopted in some jurisdictions. It alters the local offset, so a recurring weekly rehearsal can move by an hour for some participants when one country changes clocks and another does not. Countries and regions do not all change on the same date, and some do not change at all. A schedule that worked in January may be wrong in April.
Put the relevant transition dates in the production calendar and check them before the first rehearsal and before the public performance. Use IANA identifiers rather than abbreviations alone. ‘CET’ may be used loosely for Central European Time or Central European Summer Time, and ‘ET’ can refer to Eastern Time in different daylight-saving states. A label such as Europe/Berlin plus an explicit offset, such as UTC+01:00 or UTC+02:00, removes ambiguity.
Date rollover is the other common trap. A Friday evening performance in the Americas can be a Saturday morning for participants in East Asia or Oceania. Public pages should show the date and weekday as well as the time, and call sheets should repeat the date in the canonical and local formats. When a production runs near midnight UTC, the date in one participant’s calendar may differ from the date in the producer’s. That is not a minor display issue: it can cause a missed call.
Make the call sheet a time-zone document
For online theatre, the call sheet should list more than the start time. It should include the access window, technical check, warm-up, start, interval if any, end, and post-show notes. Each of these is a separate scheduling event, and each needs the same time-zone discipline as the performance.
- Master line: the canonical UTC time, written with the date and the label UTC.
- Official event line: the producing organisation, venue or festival time zone, using an IANA identifier and the local date.
- Participant lines: local times for each company, language team or guest, again with IANA identifiers.
- Date and weekday: repeated for every local line, especially when the UTC date and local date differ.
- Contact and correction route: the named scheduler and the channel for reporting a conversion error.
- Access note: whether the event is live-only, recorded, or available for a limited window, with consent and recording terms stated where relevant.
Use a consistent clock format. A 24-hour format such as 19:00 avoids the ambiguity of 12:00 am and 12:00 pm. If a company normally uses a 12-hour clock, show both formats in the first schedule and then keep one convention. For multilingual teams, translate the explanatory notes but keep time-zone identifiers, dates and UTC labels in a standard form. Translating ‘Europe/London’ into a local-language description is less useful than preserving the identifier and adding a plain-language explanation.
Test the public display from more than one device and, where possible, from more than one logged-in location. Automatic conversion depends on the viewer’s device settings, and a wrongly set device time zone can produce a wrongly displayed time even when the platform’s underlying record is correct. The production team should know which display is authoritative and say so in the programme.
Address access and power in scheduling
Time-zone choices are also access choices. A schedule that is convenient for a European director and a North American producer may fall in the middle of the night for a performer in Asia or Oceania. Repeating the same inconvenient hour for every rehearsal can exclude the same participants each time, even when the technology works perfectly.
Where possible, rotate meeting times across a rehearsal period, separate technical checks from creative sessions, and record sessions with consent for those who cannot attend live. State the rotation policy in advance so that participants can plan. For public online performances, consider whether a single live start is the only access model or whether a repeat, an on-demand window, or a captioned recording can widen participation without pretending that asynchronous access is the same as liveness.
These decisions should be documented alongside the schedule. A note such as ‘this performance is 19:00 UTC, 20:00 Europe/London, 15:00 America/New_York and 05:00 next day Asia/Tokyo’ is more useful than a single converted time, because it makes the distribution of inconvenience visible. The example is illustrative; the actual zones and dates must be checked for the production.
Common failures to check
- Publishing a single abbreviation such as ‘CET’ without an offset or IANA identifier.
- Converting the start time but not the technical check, access window or end time.
- Assuming an automatic platform conversion is correct for every viewer.
- Forgetting that a local date may be the next or previous day.
- Scheduling recurring rehearsals without checking daylight-saving transition dates.
- Letting a shared production calendar stand in for a public audience time policy.
The reliable pattern is not complicated: one canonical instant, explicit local displays, a named scheduler, and a call sheet that treats time zones as production information. That pattern keeps international online theatre legible across borders without pretending that every participant experiences the same clock.
FAQ
Should international online theatre be scheduled in UTC or local time?
Use UTC as the canonical reference for the production record, then publish the official event time and participant local times alongside it. UTC keeps the underlying instant stable, while local times make the schedule usable for each person.
How do we handle daylight saving changes?
Use IANA time-zone identifiers and check transition dates before rehearsals and performances. A recurring meeting can shift by an hour when one country changes clocks and another does not.
What should an online theatre call sheet include?
It should include the canonical UTC time, the official event time zone, participant local times, the date and weekday, access window, technical check, start and end, plus the named person responsible for corrections.
Does an online event need one time zone or many?
It needs one canonical instant and as many local displays as the participants and audiences require. Platform settings vary: some display a theatre or festival time zone, while others adjust to the viewer.
How can we avoid excluding participants in distant time zones?
Treat scheduling as an access decision. Rotate meeting times where possible, separate technical checks from creative work, and use consented recordings or repeats when live attendance is unreasonable for some participants.
Leave a Reply