---
{
  "title": "What brief should you send for a conference translation quote?",
  "description": "Gather programme, rooms, languages, audio, headsets and responsibilities in a clear conference translation brief, with confirmed facts and open questions separated.",
  "date": "2026-10-24",
  "language": "en",
  "canonical": "https://uni-translate.fr/en/blog/conference-translation-event-brief/"
}
---

# What brief should you send for a conference translation quote?

To obtain a relevant proposal, send a programme showing simultaneous sessions, spoken and listening languages, available equipment and expected responsibilities. Separate confirmed facts from open questions. The template below frames the discussion; it does not set a price, establish availability or define the contractual content of a translation service before the provider confirms its scope.

![A generous document and microphone connect planning questions with the stage.](https://uni-translate.fr/ascii-art/svg/preparation-event-brief.svg)

## Describe the event and the decision required {#evenement}
Start with the date, venue, access times and person responsible for organising the event. Say whether you want a complete service or a rack integrated into an existing audiovisual setup. Explain the participant outcome: listening to a plenary, following workshops or asking questions. The [rental, purchase or service guide](https://uni-translate.fr/en/blog/rental-purchase-service/) helps establish this scope before comparing proposals that might cover very different services, equipment and operational responsibilities for the same programme.

## Attach a programme showing simultaneous sessions {#programme}
For each sequence, give the room, time, format, spoken languages and requested listening languages. Mark what remains unconfirmed and the expected decision date. Show simultaneous workshops even when they are brief. Add important transitions, audience questions and any remote contributions as needs to examine. An overall language list does not by itself reveal how many installations must run at once or how exchanges will reach the audio system, so retain the session detail in the document you send.

![A shared running order makes timings, transitions and simultaneous sessions visible.](https://uni-translate.fr/ascii-art/svg/preparation-run-of-show.svg)

## Inventory audio and distribution {#audio}
Describe microphones, mixer, available audio feed and intended listening system. If a technical reference is unknown, write “to be confirmed by the audiovisual team” rather than inventing compatibility. The [rack specifications](https://uni-translate.fr/en/specifications/) state one input and four jack outputs, without replacing validation of your connection. Say who supplies headsets, receivers, cables and operation, and when an end-to-end trial can take place at the venue. This makes missing information visible before it becomes an installation problem.

## A brief template to reuse {#modele}
Copy these fields into your message, distinguishing confirmed information from open requests. Attach a readable running order rather than several conflicting screenshots. The recipient should be able to identify questions blocking the proposal and the person who can answer them before the requested response date, without having to reconstruct the programme from separate messages.

- Event: date, venue, access, contact and response deadline.
- Programme: timings, rooms, simultaneous sessions and speaking formats.
- Languages: announced sources, requested outputs and pairs to validate.
- Audio: team, microphones, mixer and available feed to confirm.
- Listening: headsets, receivers and supply responsibilities.
- Operation: installation, rehearsal, technical presence and fallback to clarify.

## Request a scope you can verify {#reponse}
When the proposal arrives, check inclusions, exclusions and items still conditional. Do not interpret [rack rental](https://uni-translate.fr/en/rent-rack/) as automatically including all listening distribution or its operation. Ask for rehearsal arrangements, responsibilities and acceptance procedures to be specified. Then circulate the approved version to the teams concerned. A programme change should trigger a check of its installation impact before the public announcement is simply updated with the new session details or languages.

## Sources and useful links

- [Rack specifications](https://uni-translate.fr/en/specifications/)
- [Rack rental](https://uni-translate.fr/en/rent-rack/)

## Read next

- [Which languages should your conference offer?](https://uni-translate.fr/en/blog/choose-conference-languages/)
- [Connect a translation rack to an audio mixer](https://uni-translate.fr/en/blog/connect-translation-rack-mixer/)
- [Full service, rental or purchase: how to choose a translation rack](https://uni-translate.fr/en/blog/rental-purchase-service/)

By Uni-Translate. Written with AI assistance using public product specifications and documented sources.