The Brief Template and Checklists We Teach in Project Stages

Learners often expect the first module to begin with cameras or lighting. It begins with a printed brief template and a pencil. The reason is simple: every decision later in a launch, from how many presenters rehearse to how long the load-in takes, grows from what was written down in the first conversation with the client.

In my coaching work with speakers I see the same pattern. When a presenter arrives at rehearsal and the brief is vague, the time goes on questions that should have been settled weeks earlier. The template we use in Module 1 exists to move those questions to the front of the project, where they cost a phone call rather than a delayed doors-open.

The template is deliberately plain. It has no scoring, no clever formatting and no software behind it. Learners fill it in by hand during the first practice session, using a fictionless but realistic scenario handed out by the instructor, and then compare what they captured with what the scenario actually required.

The intake brief runs to two pages. The first page covers the purpose of the event: what is being launched or premiered, who the audience is, and what the client wants people to do or feel by the end. Learners are asked to write the purpose in a single sentence, and most need three attempts.

The second page covers the practical frame: preferred date and any fallback, venue or shortlist of venues, expected audience size, number of presenters, and whether the event will be streamed or recorded. We also ask who on the client side can approve decisions, because an unnamed approver is one of the quietest causes of late changes.

Nothing on the form is optional in practice. A blank field is treated as a question to be asked, not a gap to be filled with an assumption. Learners practise phrasing those follow-up questions politely and briefly, since a long questionnaire can put a new client off before the work has started.

• Purpose of the launch in one sentence
• Date, fallback date and venue
• Audience size and presenter count
• Streaming or recording needs
• Named approver on the client side

Once the brief is complete, learners move to the stage checklist, which lays out the life of a launch project in order: enquiry, brief, quotation, planning, rehearsal, setup, event day and delivery of recordings. Each stage lists what must be finished before the next can begin.

The checklist is not a rigid timeline. A small product presentation may compress planning and rehearsal into a few days, while a creative premiere may stretch them over weeks. What the checklist protects is the sequence, so that nobody books a rehearsal before the run sheet exists or promises a recording delivery date before the filming plan is settled.

In class we mark up the checklist differently for each scenario. Learners find that the same eight stages hold across very different events, and that is the point of teaching them as a fixed frame rather than a one-off plan.

A quotation written too early is a guess with a price on it. Module 1 gives learners a short list of information that has to be in hand first: the confirmed purpose, the venue and its access times, the running order in outline, the technical scope such as cameras and streaming, and the delivery format for any recording.

We teach learners to treat the quotation as a summary of the brief, not a separate document. If a line in the quote cannot be traced back to an answer on the brief, either the quote is padded or the brief is incomplete. Practising that tracing in pairs is one of the most useful exercises in the module.

Learners also practise saying what is not included. Naming exclusions plainly, such as travel, extra rehearsal hours or additional edits, prevents the awkward conversation that otherwise arrives after the event.

• Confirmed purpose and audience
• Venue, access and setup window
• Outline running order
• Technical scope: cameras, streaming, audio
• Recording format and delivery method

Practice sessions in this module are built around role play. One learner plays the client with a scenario card, another plays the producer, and a third observes with the checklist. After fifteen minutes they swap. The observer's job is to note which brief fields were skipped and which questions were asked well.

I sit in on these sessions as a presenter coach, and what I listen for is tone. A producer who rushes through the form can make a nervous first-time client feel interrogated. Learners are encouraged to explain why each question matters, in one short sentence, before asking it.

By the end of the module each learner has completed at least one full brief and stage checklist of their own, based on a scenario of their choosing from a short list. Those documents become the starting point for the cue planning work in the next module.

The realistic outcome of Module 1 is not a polished business process but a habit: asking the same core questions every time and writing the answers down before any price or plan is discussed. Learners leave with their own filled-in brief and checklist as reference.

These documents are working tools, and they get worn in. Learners tell us they rewrite the template after their first real project, adding a field here, trimming one there. That is encouraged. A template that is never changed has probably never been used under pressure.

As the autumn season brings more product presentations and creative premieres, a clear brief is the cheapest preparation any producer can do. It costs an hour of careful conversation and saves days of correction later.