Planning Rehearsals Across Time Zones

What planning across time zones actually requires

Planning rehearsals across time zones is not a matter of finding one convenient hour and converting it. It is a production-design problem: the schedule must make presence possible, distribute inconvenience fairly, and leave an auditable record of what was agreed. The practical answer is to work in three layers: establish a single reference clock, choose and rotate a sustainable overlap window, and move everything that does not need live presence into asynchronous work. This applies to international co-productions, multilingual rehearsals, remote dramaturgy and digitally networked performance, though the balance changes with each production.

Time-zone planning is often treated as administration. In rehearsal it is closer to access planning. A cast member joining at midnight is not simply available; they are working under different cognitive, physical and domestic conditions. A guide to coordinating pan-African dance rehearsals frames structured time-zone planning as a way to protect rest, reduce injury risk and cut rescheduling email by up to 80 per cent (Artfolio guide to time-zone planning). That evidence comes from dance practice, not theatre, but the underlying point transfers: fatigue and uncertainty are creative problems, not only diary problems.

Build a time-zone map before choosing a slot

Start with a shared board rather than a chain of private messages. A recommended scheduling chain for cross-team work is to make the team map visible, score candidate windows, then publish the agreed instant as a calendar link (itime.day scheduling guide). The board should list every city or office and show whether each participant is currently in work hours, evening, night or the weekend before anyone proposes a time. For theatre, add role and rehearsal function: director, stage manager, translator, movement director, understudy, technician. The person who must attend is not always the person who appears first in the email thread.

Use a stable reference such as Coordinated Universal Time (UTC) for calculations, but keep local time visible for decisions. Avoid abbreviations such as BST, EST or CST without a city and date: they are ambiguous across regions and seasons. A pan-African rehearsal guide notes that collaborations can span eight time offsets, from UTC−01:00 to UTC+04:00 (Artfolio guide to time-zone planning). The wider lesson is not that Africa has one schedule; it is that even a regional project may contain many offsets. Use IANA time-zone identifiers such as Europe/London or Africa/Lagos, and check the date-specific offset rather than relying on memory.

Choose a sustainable overlap window, then rotate the cost

There is no universally correct rehearsal hour. A good cross-team time is not merely the mathematically overlapping hour; it should minimise repeated burden, avoid severe conflicts and remain easy to audit later (itime.day scheduling guide). Use a meeting planner to compare candidate instants, but read the result as a burden map, not a verdict. A planner may show that one city is disadvantaged every week; that pattern matters more than a single convenient date.

When no shared working-hour overlap exists, rotate the inconvenient slot and document the rotation rule (useChrono three-time-zone guide). Rotation turns an invisible hierarchy into an explicit agreement. It also protects against the common failure in three-zone scheduling, where one team absorbs the human cost repeatedly. The same guide distinguishes meeting purposes: status reporting can often be asynchronous, while decisions, conflict resolution and high-context discussion may justify live time (useChrono three-time-zone guide). A production-management guide for international filming lists a 24-hour global production window and 4–6 hours as optimal meeting windows (Fixers in Germany production guide). Those figures are a planning heuristic from screen production, not a theatre rule, but they are useful for sanity-checking an agenda that assumes everyone can meet for three hours.

Fairness also means asking about care responsibilities, transport, health and access needs. A time-zone board can show that someone is outside working hours; it cannot show that they are the only person who can collect a child from school. The schedule owner should ask, record constraints with consent, and avoid treating a calendar as proof of availability.

Separate live rehearsal from asynchronous preparation

Live time is expensive across time zones. Reserve it for work that benefits from simultaneous presence: blocking, scene work, negotiated cuts, directorial decisions, intimacy calls, technical checks and conflict resolution. Move familiarisation, line learning, translation queries, design updates and routine production reporting to asynchronous channels where possible. The cross-team scheduling guidance recommends asynchronous updates by default for status work and live time for decisions and high-context discussion (useChrono three-time-zone guide).

Asynchronous work still needs a deadline, a format and an owner. A recorded scene run is not automatically accessible: provide captions, a transcript or a low-bandwidth audio option where needed. Translated sides and dramaturgical notes should arrive early enough to be read, not at the start of the call. In multilingual rehearsals, interpretation is work: it needs turn-taking, pauses and sometimes a separate channel. Scheduling it as an afterthought makes the live session slower and less equitable.

Design the live session for the hour people actually have

A rehearsal at 09:00 and the same rehearsal at 23:00 are not equivalent. The person joining late at night may be able to read and discuss but not safely perform complex movement or sustained physical work. The pan-African dance guide connects time-zone planning with rest and injury risk (Artfolio guide to time-zone planning). In theatre, the same caution applies to warm-ups, fight calls, intimacy work and any exercise that depends on balance or sustained concentration. The stage manager or session host should pace the call, schedule breaks and avoid placing the most demanding work at the end, when fatigue is highest.

Record only with consent and a clear purpose. A recording made for absent cast members is different from a recording published as documentation. Say which it is, where it will live and who can access it. This is not a bureaucratic extra; it affects how freely performers test material. For digital and networked performance, the recording may also become part of the archive, so consent and attribution need to be settled before the session, not after.

Give the schedule an owner and a paper trail

Every recurring rehearsal needs a named owner: usually a production manager, stage manager or company manager. The owner maintains the time-zone board, confirms daylight-saving changes, publishes the call and keeps the next action visible. The director or rehearsal leader owns priorities: which scenes need live presence, which can be prepared asynchronously, and which decisions cannot wait. A digital host can manage waiting rooms, captions, interpretation channels and recordings. A translator or dramaturg may need a separate document for terminology and context.

Publish the exact instant and base time zone, then generate calendar links rather than asking people to translate manually (itime.day scheduling guide). A usable call sheet gives the date, UTC time, each local time, the joining link and the rehearsal purpose. It should also state whether the session is recorded and what preparation is required. After the session, confirm decisions and the next call in writing. The dance-rehearsal guide reports that structured time-zone planning can reduce rescheduling email by up to 80 per cent (Artfolio guide to time-zone planning); even allowing for context, the principle is sound: fewer ambiguous messages, fewer avoidable absences.

Handle daylight saving and date boundaries explicitly

Daylight saving time is not universal, and its dates differ. A slot that works in January may break in April. The scheduling chain recommended by itime.day is designed to survive daylight saving by moving from comparison to a calendar invite with the exact instant and base time zone (itime.day scheduling guide). In practice, check each date in the IANA database or a reliable converter, not just the current offset. If a participant is in a region without daylight saving, their offset relative to others will still change when those others shift.

Date boundaries are equally easy to miss. A late-evening call in Vancouver may be the next morning in Manila. Write the weekday and date in full, not same time next week, and recalculate after any public holiday or tour move. For a production spanning several countries, keep a single authoritative schedule and a visible change log. When a time changes, say what changed and which local calls are affected.

A practical workflow for the first scheduling meeting

1. Define the purpose of the rehearsal and the must-have participants. Distinguish decision-makers from observers.
2. List every city, role, IANA identifier and date-specific offset. Note known constraints and access needs.
3. Choose a UTC anchor and generate two or three candidate windows, not one.
4. Test the candidates on a time-zone board and meeting planner. Mark who is in work hours, evening, night or weekend.
5. If someone is repeatedly disadvantaged, rotate the slot and write down the rule.
6. Publish the chosen instant in UTC and in each local time, with a calendar link and a plain-text call sheet.
7. Set asynchronous preparation: sides, translation notes, recordings, design updates and deadlines.
8. Run the live session with a timekeeper, breaks and agreed language access.
9. Record decisions with consent; circulate notes and the next call.
10. Review the pattern after a few weeks, not only the individual diary.

Common problems and how to avoid them

• Abbreviation drift. Use city plus IANA identifier; avoid unexplained acronyms.
• Converting the hour but not the date. Show weekday and date in every call sheet.
• Mistaking overlap for fairness. Check repeated burden, not just one workable hour.
• Using live time for status. Move routine updates to written form and keep live time for decisions and scene work.
• Ignoring the hour’s quality. Adapt physical and language-heavy work to the time of day.
• Recording without a stated purpose. Agree consent, access and retention before recording.

The aim is not a perfect calendar. It is a rehearsal culture in which the cost of distance is visible, shared and revisable. When time-zone planning is treated as part of dramaturgy and production rather than as a secretarial task, international rehearsals become more predictable and more humane.