Organizer checklist
- For
- Whoever is organizing the event
- You need
- An event under a contract with Saydi. Running it yourself on an Event plan? See Run an event.
Hand this page to whoever is organizing the event. It tells the organizing team what to send, what to confirm, and when, so event day holds no surprises. Most interpretation problems at events come from the audio feed and the venue Wi-Fi, not the software.
Who does what
This split applies when your event is under a contract with Saydi. If you run the event yourself on an Event plan, your team also does the Saydi column: see Run an event.
| Saydi | Organizer |
|---|---|
| Creates the event and configures the language list | Audio feed from the mixer to the Saydi computer |
| Provides the QR code for attendees | Network capacity for the expected audience (or tell attendees to use mobile data) |
| Documentation + one remote technical briefing | Attendees' own phones and earphones |
| One remote rehearsal before the event | Telling attendees to scan the QR (MC, standee, printed programme) |
| Online technical support throughout the event | A technical contact present in the hall |
Timeline
The dates below are recommendations. If your contract sets other deadlines, the contract applies.
- Send Saydi the terminology list: speaker names, organizations, product names, industry terms. This is the biggest accuracy lever. → How to load terms
- Send the session programme: which sessions use Saydi, how long, which language each speaker uses.
- Confirm the list of languages attendees need.
- Send the hall layout + the venue sound team's contact.
Everything technical on one page for the venue's IT and sound crew: Technical requirements.
Network: four numbers to remember
| Requirement | |
|---|---|
| The Saydi computer | ≥ 2 Mbps up/down dedicated · ping to api.saydi.ai < 100 ms · packet loss < 1 % · wired LAN preferred |
| Each attendee on QR | ~0.2 Mbps |
| Whole hall | 100 people ≈ 30 Mbps · 300 ≈ 85 Mbps · 500 ≈ 140 Mbps (40 % headroom included) |
| Wi-Fi access points | 1 AP per 50–75 devices · prefer 5 GHz |
Saydi connects over WebSocket, port 443/TCP outbound. No inbound ports, no VPN. Guest networks that block unusual ports usually work.
The most likely bottleneck