The Event-Day Briefing Checklist Every Agency Should Use
Key Takeaways
- A complete event-day brief prevents the most common performer problems — wrong entrance, wrong attire, missed cue times — before they happen.
- Every brief needs six core sections: venue and arrival, running order, dress code, technical notes, parking and site access, and key contacts.
- Dress code is the most under-specified section in most agency briefs — vague terms like "smart casual" create the exact ambiguity you are trying to eliminate.
- The brief should reach performers at least 72 hours before the event — enough time to read it, ask questions, and resolve anything unclear before the day.
- Attaching the brief directly to the booking record — rather than sending it as a loose email — keeps everything findable and makes acknowledgement tracking straightforward.
A performer who turns up at the wrong entrance, dressed incorrectly, with no idea who to ask for — that is not a worst-case scenario. For agencies that handle event-day communications informally, it is a familiar problem. The event day performer briefing checklist exists to prevent this category of failure entirely: not by adding bureaucracy to your workflow, but by establishing a single, shared source of truth that every performer receives before every booking. This guide sets out exactly what that brief should contain, section by section, why each element matters, and how to build the habit of sending it consistently — without it becoming another manual task that falls through the gaps when the diary gets busy.
Why Most Performance Problems Start Before the Event Does
When a performer arrives late, dressed inappropriately, or asking questions that should have been answered days earlier, the instinct is to treat it as a failure of communication. In practice, it is almost always a failure of documentation. The information existed — someone in the agency knew the venue entrance, the timing, the dress expectation — but it was never consolidated and sent in a consistent, readable format that the performer could refer back to when they needed it.
The impact of performers arriving without preparation is well-documented across the events industry. ReverbNation's performer blog notes that arriving on stage without adequate preparation — even for experienced performers — results in tentative, awkward performances that are visible to any audience and difficult to recover from mid-set. The same principle applies to logistical preparation: a performer who has not received a clear brief arrives in a reactive state, solving problems that should not exist.
Event risk specialists consistently identify unclear role briefings and coordination breakdowns as among the most common causes of live event problems. The pattern across these failures is nearly identical: the information existed within the agency, but it was never compiled and shared in a format that actually reached the performer in a usable form. An email sent two days ago to an address the performer checks infrequently is not the same as a brief that was read, understood, and acknowledged.
For agencies managing multiple bookings simultaneously, a standardised brief also provides accountability. When a performer has received, read, and confirmed a detailed brief, the agency has discharged its operational duty of care. The brief becomes the single point of reference if questions arise after the event — replacing a series of WhatsApp messages, scattered email threads, and phone call recollections that are difficult to retrieve and impossible to consistently rely on.
The Complete Event-Day Performer Briefing Checklist
The following six sections form the minimum viable brief for any performer booking. For simpler gigs — a solo acoustic performer at a private dinner — some sections will be a single line. For large-scale corporate events or multi-act productions, each section may run to several paragraphs. The structure remains the same regardless of scale; what varies is the depth of detail within each section.
1. Venue & Arrival Details
Include the full venue name, complete street address, and — critically — the specific entrance the performer should use. Client-facing venues typically have multiple access points: a main public entrance, a service or staff entrance, and a dedicated backstage or artist access route. A performer who defaults to the main entrance at a black-tie corporate dinner can create exactly the kind of visible disruption that the brief exists to prevent.
Specify the required arrival time, not the performance start time. Most performers need a minimum of 30 minutes before their slot for orientation and technical preparation — state the expected arrival time explicitly and separately from the show time. If a soundcheck is required, list the soundcheck time as its own line item. Include the name of the person the performer should ask for on arrival — a specific name is far more useful than a job title alone, particularly at larger venues where multiple staff members will be on duty.
2. Running Order & Timing
Provide the full running order for the event, or the relevant section for the performer's part of the evening. Include the performer's slot time and expected performance duration, any hard stop times — particularly important for licensed venues with noise curfews or corporate events with back-to-back programming — and the times and durations of any planned breaks or intervals that affect when the performer should be ready to go on.
Where multiple performers share the stage, include transition instructions: how long each handover takes, who manages it, whether there are stage manager cues, and what the performer should be doing in the time immediately before and after their set. A running order that a performer can follow independently — without needing to ask questions on the day — is the benchmark to aim for.
3. Dress Code & Presentation
Dress code is the section most frequently under-specified in agency briefs, and under-specification here creates exactly the ambiguity you are trying to eliminate. Generic terms like "smart casual" or "formal" carry different meanings to different people. Event industry professionals consistently note that plain-language descriptions of expected attire outperform category labels alone — because labels leave room for interpretation that plain language does not.
Write the dress code as a short, specific description: "Dark trousers, formal shirt, jacket preferred. No jeans. No visible branded clothing. Closed-toe shoes only." For themed events, specify exactly how the theme applies to performers — whether they are expected to reflect it subtly, partially, or in full costume. If there are specific colours or styles to avoid because they clash with a corporate colour scheme or stage backdrop, say so explicitly. The two minutes it takes to write this section properly eliminates a category of problem that is otherwise almost guaranteed to recur.
4. Technical Notes & Equipment
List what the venue is providing — microphone type, PA system, monitor feeds, stage dimensions, lighting setup — and what the performer is expected to bring or confirm in advance. If any element differs from the performer's standard technical rider, flag it explicitly in this section; do not assume the performer will notice a discrepancy on arrival.
If there is an AV team or sound engineer on-site, include their name and confirm that the performer can approach them directly on arrival. This one piece of information can prevent 20 minutes of confusion at the start of a soundcheck — the performer knows who to look for, the engineer knows to expect them, and the process moves smoothly rather than starting with everyone trying to find each other.
5. Parking & Site Access
Include the nearest car park, the postcode to use for satellite navigation (venue postcodes and car park postcodes often differ), any height restrictions for larger vehicles, and whether parking is included in the booking or needs to be paid and reclaimed on expenses. If load-in is required for equipment, specify the loading bay access route, any time windows for loading, and whether a trolley or crew assistance is available on site.
For city-centre venues, large hotels, conference centres, or unusual locations such as country estates or private grounds, a brief paragraph covering access is worth considerably more than a venue address alone. These are the locations where performers most commonly report confusion and delay on arrival — and where a clear written paragraph in the brief would have prevented it entirely.
6. Key Contacts
Include a minimum of three contacts for every booking: the agency contact number for the day, the venue or event manager's direct number, and the on-site production or stage manager's number. Three contacts — agency, venue, on-site — is the standard minimum. If the client is contactable during the event, include their number with a brief note on when and how to use it.
The contacts section is not just administrative — it is the section a performer reaches for when something unexpected happens on the day. Make it easy to find and easy to act on. Names, numbers, and a single line on each person's role. Nothing a performer needs in an emergency should require them to search through email threads while standing outside a venue they cannot find the entrance to.
How to Write Each Section So Performers Actually Read It
A brief that nobody reads is operationally equivalent to no brief at all. Three practices make a performer brief significantly more likely to be absorbed before the day of the event.
Keep it scannable. Performers typically read a brief in the 30 minutes before they leave for a booking — often on a phone, often while doing something else. Short paragraphs, clear section headings, and bold text on critical details — arrival time, dress code specifics, who to ask for on arrival — respect that context. A well-structured two-page brief in plain text will outperform a five-page formatted PDF almost every time, because the information a performer needs in a hurry is immediately visible rather than buried in prose.
Lead with the most time-critical information. Open the brief with the arrival time, venue address, and on-site contact number — the three things a performer needs immediately if something goes wrong on the way to the gig. Everything else — running order, dress code, technical notes — can follow in logical order, but the information that matters in a last-minute emergency should be impossible to miss at a glance.
Write for a first-time visitor. Avoid internal agency shorthand and assume the performer has never been to this venue before, because in most cases they have not. "Use the service entrance on the left side of the building, past the car park barrier, blue door, ring the bell" is a usable instruction. "Report to the usual back entrance" is not. If sending the brief via a standardised message template, ensure every venue-specific field is filled in completely before it goes out — template placeholders left unfilled are a common and entirely avoidable source of performer confusion.
For agencies managing performers across multiple concurrent bookings, attaching the brief directly to the relevant performer booking record — rather than managing it as a separate email or document — means it is always findable when a performer calls with a question, and always visible to any team member who picks up the booking.
When to Send the Brief and How to Confirm Receipt
The brief should reach the performer no later than 72 hours before the event. For complex bookings — multi-performer line-ups, large-scale corporate productions, events with significant travel involved — five to seven days is a better target. Sending it with enough lead time gives performers the opportunity to read it properly, raise any questions, and resolve anything unclear before the day itself. Sending it the evening before — which is common practice in agencies managing briefs manually — is functionally too late. A performer who receives the brief at 9pm for a 10am call the following morning has very little time to act on anything that needs clarifying.
The moment of sending matters, but confirmation of receipt matters almost as much. An unacknowledged brief creates ambiguity: did the performer read it? Are there questions sitting unasked? The simplest fix is to include a specific, low-effort acknowledgement request at the end of the brief: "Please reply to confirm you have received this and have no questions about the details above." That sentence takes two seconds to add and transforms the brief from a one-way communication into a confirmed handshake.
Every question a performer raises after reading the brief is a direct indicator of a gap in the template. If performers consistently ask "which car park should I use?", the answer needs to go into the parking section as a standard field. If they regularly ask "who should I check in with on arrival?", that field needs to be more prominent. Use inbound questions to iterate on the standard template over time — a brief that pre-empts every common question reduces day-of contact dramatically and improves the experience for both performers and the clients at the event.
Using scheduled messaging to send briefs automatically at a set point before each booking — rather than relying on a manual step during a busy week — means nothing gets missed even when the agency is running multiple events simultaneously. The brief goes out at the right time, every time, without anyone having to remember to send it.
Frequently Asked Questions
What is the difference between a technical rider and an event brief?
A technical rider is a document provided by the performer that specifies what they need — PA system, monitor feeds, microphone type, stage dimensions, lighting rigs. An event brief is a document provided by the agency that tells the performer what they need to know — where to arrive, who to ask for, what to wear, when their slot is, and who is contactable on the day. Both documents are necessary. A rider covers the performer's requirements; a brief covers the event's logistics. Agencies that conflate the two, or rely on the rider to communicate logistical information, typically end up with performers who are technically equipped but operationally unprepared.
When should I send the event brief to a performer?
The event brief should reach the performer no later than 72 hours before the event. For large-scale events, complex multi-performer line-ups, or bookings involving significant travel, five to seven days is a better target. Sending the brief with enough lead time gives performers the opportunity to read it properly, raise any questions, and resolve anything that needs clarifying before the day. Sending it the evening before is common practice in agencies that manage briefs manually — but it is functionally too late for a performer who needs to prepare, confirm equipment, or arrange travel and parking in advance.
How long should a performer event brief be?
A standard event brief should be readable in under three minutes — typically one to two pages in print, or the equivalent in a digital format. The goal is comprehensiveness within a tight format, not exhaustiveness. Every section should answer a specific question a performer is likely to have: Where do I go? Who do I ask for? What do I wear? When am I on? What happens if something goes wrong? If your brief runs beyond two pages, it is likely including detail that belongs in the contract rather than the day-of brief. A brief that performers actually read will always outperform a thorough document that they skim and set aside.
What if the performer has questions after receiving the brief?
Treat every question as useful feedback on the brief itself. If a performer asks "which entrance should I use?" after receiving the brief, the question tells you that the venue arrival section is not specific enough — it needs to name the entrance explicitly. Most recurring questions from performers point directly to gaps in the standard template. Updating the brief to pre-empt those questions reduces inbound calls before events and, more importantly, reduces the number of performers who had the same question but did not ask it — and arrived at the wrong door anyway.
How do I make sure performers actually read and acknowledge the brief?
Three things significantly improve acknowledgement rates. First, send the brief through a channel that generates a visible reply record — not as an email attachment that may be filed unread, but as a message that invites a response. Second, keep the brief short and scannable so it does not feel like a document to deal with later. Third, include a specific acknowledgement request: "Please reply to confirm you have received this and have no questions" gives performers a clear, low-effort action to take. Agencies using booking management software can attach the brief directly to the booking record and send it through the platform, making acknowledgement tracking part of the booking workflow rather than a manual email chase.
A Brief Sent Is a Problem Prevented
The event day performer briefing checklist is not a complex document — it is six sections, written plainly, sent consistently. The agencies that do this well are not spending significantly more time on each booking; they are spending time once to build a standard template that works across every booking, and then ensuring it goes out reliably every time. The result is fewer day-of calls, fewer performers at the wrong entrance, fewer dress code conversations that should have happened a week ago.
For a complete picture of what a well-run performer booking process looks like — from confirmation through to on-the-day briefing — the performer bookings tools in LiveDesk are built specifically for entertainment agencies. Briefs attach to bookings, go out via scheduled messages, and acknowledgements sit alongside the booking record — so nothing relies on anyone remembering to send it at the right moment.
Brief Every Performer. Every Booking. Automatically.
LiveDesk lets you attach event briefs directly to performer bookings and send them on a schedule — so every performer has the right information before every event, without anyone having to remember to send it.
No credit card required • Cancel anytime • Cloud-based & secure