Skip to content
An independent guide to international theatreMany cultures. A shared stage.
The InternationalistsTHEATRE ACROSS BORDERS

A GUIDE TO THEATRE ACROSS BORDERS

Touring, Festivals & Mobility

How to Write a Technical Rider for an International Theatre Festival

THE SHORT ANSWER

A technical rider is a plain-language operational annex to a performance contract. For an international theatre festival, it should state the production's space, power, crew, schedule, language and safety requirements, distinguish company-supplied from venue-supplied items, and be negotiated and versioned with the host venue.

At a glance Quick facts
Document type
Operational and contractual annex to a touring or performance contract
Core purpose
States the production's technical, spatial, staffing and scheduling requirements for a venue
Key drafting principle
Use simple, helpful and reasonable language; avoid unreasonable conditions that venues may ignore
Touring responsibility
One person should be responsible for planning and executing technical elements, ideally supported by a production designer and stage manager
International details
Include dimensions, audience capacity, plug type, voltage and frequency; metric units first and local equivalents where useful
Site-specific example
FUGIT's rider requires identification of designated spaces and a two-day technical visit by two company members two to four months before performances

A technical rider is the working document that tells a festival, venue or receiving host what your production needs in order to be performed safely and as intended. It is not a press release or a simple repeat of the application form. The ABTT model technical rider describes it as a corollary to a contract that details technical requirements; it should form part of, or be attached to, the main contract between the theatre and the visiting company. In an international festival context, the rider also has to translate your practice into a form that a venue in another language, power system and labour culture can act on. Write it early, keep it specific, and treat it as a negotiated annex rather than a wish list.

What a technical rider is and what it is not

A festival application form often collects the first layer of technical information. The Tbilisi International Festival of Theatre 2026 international programme form, for example, asks for playing-area width, depth and height; minimum and maximum requirements; type of space; maximum audience; entries and cloakrooms; and detailed light and sound needs, including plug type. It also asks for an online Vimeo link, the original and English title, credits, duration, premiere year, touring party and whether the company has travel support. These questions are prompts for selection and initial planning. They are not a substitute for a rider that has been checked against a particular venue, schedule and local crew arrangement.

The rider should also be distinguished from the venue’s own technical specification. The venue specification describes what the host has; the rider describes what the production needs, what the company brings, who does which tasks, and what must be confirmed. A useful rider is therefore a three-way document: company requirements, venue resources, and shared responsibilities.

DocumentMain purposeTypical content
Festival application formSelection and initial planningCompany details, video link, title, credits, duration, touring party, summary of space and technical needs
Technical riderOperational and contractual annexDetailed requirements, responsibilities, schedules, equipment, power, crew, plans and risk information
Venue technical specificationHost’s available resourcesDimensions, equipment inventory, power, staffing, load-in arrangements and house rules

Start from the festival and the venue, not a template

International festivals may use several venues, from purpose-built theatres to found spaces. A master rider can describe the production’s invariant needs, but each venue usually needs a venue-specific appendix. Ask the festival for the technical specification, the name and language of the venue technical contact, the allocated local crew, get-in and get-out times, and any restrictions on rigging, floor loading, noise, access or audience capacity. If the venue is not yet confirmed, write the rider with clear venue categories and mark the unknowns for confirmation rather than inventing details.

The rider must also identify who is in charge. Battery Dance Company International’s touring guidance stresses that one person on tour should be responsible for planning and executing all technical elements, ideally a production designer and a stage manager, though tight budgets often mean one person covers the range of responsibilities. Name that person in the rider, with a backup contact where possible. A festival needs to know whom to call when a cable fails, a cue changes or a truck arrives late.

The core sections of an international rider

Production identity and people

Begin with the production title in the original language and in English, the company name, the premiere year, duration, interval and a short synopsis. List the full touring party by role, not only by name: performer, director, designer, stage manager, technician, translator or operator. State who operates equipment and who supervises. Include contacts for the touring technical lead, the producer and an emergency contact, and note working languages and preferred contact methods.

Space, schedule and audience

Give the playing area in metres first, with local equivalents if useful: width, depth and height, plus minimum and maximum dimensions. Describe the floor, masking, entrances, get-in route and any need for a black box, raked seating, natural light or outdoor cover. State audience capacity and any front-of-house needs. Then set out the working schedule: load-in, fit-up, focus, technical rehearsal, dress rehearsal, performances and get-out. Include crew call times and turnaround requirements. For site-specific work, the rider may need to cover more than a stage. The FUGIT technical rider is a useful example of this expanded logic: it requires preliminary identification of designated spaces and a two-day technical visit by two company members two to four months before performance, and it specifies an audience of 90 people per performance. That is not a universal template, but it shows why site-specific riders must address audience routes, meeting points and temporary infrastructure as well as lights and sound.

Lighting, sound, video and power

List equipment by type and quantity, and separate company-supplied items from venue-supplied items. For lighting, include positions, fixtures, dimming, control, focus and any special effects. For sound, include the channel list, playback, microphones, DI boxes, PA, monitors, cue playback and operator. For video or projection, include source formats, resolution, aspect ratio, inputs, projection distance, screen or surface, software and operator. Power deserves its own section: state voltage, frequency, total load, phase requirement, plug type and whether adaptors or transformers are needed. A festival form may ask only for plug type, but an international rider should give enough information for a venue electrician to assess the supply safely. Include photographs of unusual connectors and label company cables clearly.

Stage management, crew and safety

State how many local crew are required and what they are expected to do: load-in, rigging assistance, focus, changeovers, wardrobe, get-out or front-of-house. Distinguish technicians who operate from those who assist. Identify who calls cues and who speaks which language. Safety information should be proportionate: working at height, rigging, floor loading, trip hazards, smoke or haze, strobe, pyrotechnics, weapons, water, food or other special risks. The ABTT guidance notes that technical riders relate directly or indirectly to safety and good practice. The rider is not necessarily the full risk assessment, but it should point to one and make safety-critical requirements explicit.

Access, wardrobe and audience information

Include accessible routes, dressing rooms, showers, laundry, quick-change space and any need for a quiet or warm-up area. Note content warnings, age guidance, latecomer policy, photography or recording restrictions, and whether the audience is seated, standing, promenading or moving between sites. If the production uses surtitles, translation, audio description or a bilingual front-of-house announcement, state the equipment, operator and language needs. These details are often omitted from technical riders, yet they can determine whether an international presentation works for its audience.

Annexes and version control

Attach the documents that make the rider actionable: a floor plan, lighting plot, sound patch, cue list, equipment list, risk assessment, contact sheet, production photographs and, where the festival requests it, a link to performance video. Give every version a number and date, and name the author. Mark clearly whether the rider is a draft, a venue-confirmed version or a final version. A rider without version control quickly becomes unreliable when several festivals are negotiating at once.

Writing for readers across languages and systems

Use plain English, short sentences and consistent terms. Define abbreviations and avoid local slang that a translator or venue technician may not recognise. Use metric units first; include imperial conversions only if they help a particular host. Write dates with the month in words, and give times with the timezone when scheduling international calls. For power, give voltage and frequency as well as plug type, because the same connector can be used in different supply systems. Plug type names vary, so combine the name with a photograph and ask the venue electrician to confirm. If the rider is likely to be read in another language, provide key sections bilingually or have the safety-critical parts translated by a competent human translator. Machine translation can help with routine vocabulary, but it is a poor substitute for checking contractual and safety information.

Negotiate and attach the rider

The ABTT model advises that technical riders are most effective when worded to be helpful and informative, in simple rather than legalistic language. It also observes that many riders include unreasonable conditions and that large parts are simply ignored. A practical rider therefore separates essential requirements from preferred options and from items the venue is asked to confirm. Use a clear status column or annotation: essential, preferred, company-supplied, venue-supplied, to be confirmed. Ask the festival to return the rider with acceptance notes or alternatives, and keep the email trail with the contract. The rider does not replace discussion about visas, work permits, tax, customs, insurance or freight; those belong with the producer or festival, using the relevant official routes. The rider can still note who is responsible for each logistical task so that nothing disappears between departments.

A practical checklist

  • Header: production title, company, festival and venue, performance dates, version number, date and author.
  • Contacts: touring technical lead, producer, festival technical contact and emergency contact, with languages and timezone.
  • Production: original and English title, credits, duration, interval, synopsis, premiere year and content notes.
  • Touring party: names, roles, arrival and departure, and who operates or supervises technical elements.
  • Space: dimensions, floor, audience capacity, entrances, cloakrooms, accessibility and load-in route.
  • Schedule: get-in, fit-up, focus, technical rehearsal, dress, performances and get-out, with crew calls.
  • Equipment: lighting, sound, video, rigging and consumables, clearly marked company-supplied or venue-supplied.
  • Power: voltage, frequency, plug type, total load, phase, adaptors and earthing requirements.
  • Crew: number, skills, language, tasks and who calls cues.
  • Documents: floor plan, plot, patch, cue list, risk assessment, photographs and video link.
  • Negotiation: essential and preferred items, venue confirmations, signatures or email acceptance.

Common problems to avoid

Vague equipment lists, missing power specifications, unnumbered local crew, outdated plots and riders copied from another production are frequent causes of festival friction. So is treating the application form as if it were a rider, or sending a rider before checking the venue’s actual resources. Overlong prose can be as unhelpful as missing detail: use tables and annexes for technical data, and keep the main narrative focused on responsibilities. Finally, do not present unconfirmed assumptions as settled facts. A rider that says the venue will provide a particular item without agreement is not a plan; it is a dispute waiting to happen.

For an international theatre festival, the technical rider is both a safety document and a diplomatic document. It should be specific enough to be built from, reasonable enough to be accepted, and clear enough to survive translation, time pressure and a change of venue. Start with the festival’s form and the venue’s specification, write for a reader who does not share your language or power standards, attach the rider to the contract, and keep every version visible.

FAQ

What is the difference between a technical rider and a festival application form?

An application form supports selection and initial planning. A technical rider is an operational and contractual annex that sets out detailed requirements, responsibilities, schedules and venue-specific confirmations.

How long should an international technical rider be?

There is no fixed length. Keep the main text focused on requirements and responsibilities, and use tables and annexes for plots, patches, equipment lists and schedules. A short rider with clear annexes is usually more usable than a long narrative.

Should the rider be written in English?

English is often used as a working language in international festivals, but check the festival's preference. Provide bilingual key sections where possible, and have safety-critical parts translated by a competent human translator rather than relying only on machine translation.

What should I do if the venue does not have the exact plug or equipment?

State what the company can supply and what the venue must confirm. Give voltage, frequency, plug type and load information, include photographs, and ask the venue electrician to confirm any adaptor, transformer or alternative arrangement.

When should the rider be sent?

Send the information requested with the application. After selection, issue a draft rider, then finalise it once the venue, schedule and local crew are confirmed. Keep version numbers and dates so that all parties know which document is current.

READ FURTHER

Sources & references

  1. Tbilisi International Festival of Theatre, Application form for International Program NEW 2026, https://www.tbilisiinternational.com/storage/files/doc/Application_form_NEW_2026.pdf
  2. Battery Dance Company International, The Technical Challenges of Touring Internationally, https://toolkit.batterydance.org/stories/217
  3. Association of British Theatre Technicians (ABTT), Model Technical Rider, hosted by StageSoc, https://stagesoc.org.uk/gallery/upload/2586_a5VBWVy0.pdf
  4. Kamchatka and FUGIT, Technical Rider, 2022, http://kamchatka.cat/download/FUGIT/eng/TechRider_FUGIT-ENG2022.pdf

THE LANGUAGE OF PRACTICE

Related terms

Technical rider
An annex to a performance contract that details technical requirements, responsibilities and schedules.
Festival application form
A selection and planning form that collects summary information; it is not a substitute for the rider.
Lighting plot
A scale drawing showing lighting positions, fixtures, circuits and focus.
Patch
A schedule mapping sound or lighting channels to sources, destinations and control desks.
Site-specific performance
Performance made for a particular place, often requiring the rider to address access, audience routes and temporary infrastructure.
Local crew
Technicians engaged by the venue or festival to assist with load-in, focus, changeovers and get-out.

A SHARED BODY OF KNOWLEDGE

Something to add or correct? Help us keep the conversation informed.

Corrections & updates

Leave a Reply

Your email address will not be published. Required fields are marked *

THE CONVERSATION CONTINUES

Keep a window open to the world.

Fresh perspectives and practical reading, straight to your feed reader.

Subscribe via RSS

FOLLOW YOUR CURIOSITY

Find your next idea.

Search the journal, practical guides, and pages.

THE PRACTICAL TOOLKIT / 01

Your first conversations.

Use these prompts to begin planning with your collaborators. Your progress is saved in this browser.

A starting point for discussion. Adapt it to your project and check local requirements with the relevant organisations.

THE PRACTICAL TOOLKIT / 02

A time to come together.

Choose a date and time in UTC to see when your collaborators would meet. Times account for daylight saving on your chosen date.

Shaded times fall outside 09:00–18:00 local time. Agree working hours and access needs with your team.

BEHIND THE IMAGES

Photography credits

Editorial stock photographs illustrate themes; they do not document the productions discussed on this site. Used under the Pexels licence.