What a Project Brief Needs Before We Can Quote a Launch

In Module 1 we spend a full session on one document, the project brief. Learners often arrive expecting to start with cameras or cue sheets, and some are surprised that the first practical task is a page of questions. The reason is simple. A quotation is a promise about time, people and equipment, and a promise built on guesses tends to be revised twice before the event.

This autumn, with several learners preparing mock launches for the first time, I have been watching the same pattern in the room. The groups that slow down and fill in the brief carefully spend less time arguing later about what was agreed. Those who skip ahead to the fun parts of the show end up returning to the brief anyway, usually the night before a rehearsal.

The aim of this session is not paperwork for its own sake. It is learning to ask a client the questions that will otherwise come back as problems on the day.

We teach a short list of facts that must be on the page before anyone talks about cost. First is the purpose of the event: a product reveal, a creative premiere and a press showing each need a different shape. Second is the audience, both who will be in the room and who will watch a stream or recording afterwards. Third is the date, plus any fixed points such as a press embargo or a speaker who can only attend in the morning.

Fourth is the venue, even if it is only a shortlist. Ceiling height, loading access and available power change the crew size and the setup time more than most clients expect. Fifth is the content itself: how many presenters, whether there is video playback, and whether anything is being unveiled physically on stage.

Learners practise extracting these facts from a deliberately vague client message, which is closer to real life than a tidy form.

• Purpose and format of the event
• Expected audience, in the room and online
• Fixed date and any hard deadlines
• Venue or shortlist of venues
• Presenters, playback and reveal moments

Most clients answer the obvious points readily. What they leave out is usually what costs time later. Who approves the final run order, and how quickly can that person respond? Are there guests who need accessible seating or a quiet area? Will the recording be shared publicly, privately or only inside the company? Each of these changes the plan, and none of them feels urgent in the first conversation.

In class we role-play a first call, with one learner as producer and another as a slightly distracted client. The producer's job is to leave the call with a list of open items rather than a false sense of completeness. We mark the list, not the charm.

A useful habit is to repeat back what you have heard in plain words and ask the client to correct it. It takes two minutes and often surfaces a misunderstanding about scope.

Once the brief is complete enough, it feeds the stages we walk through in the module: discovery, proposal, planning, rehearsal, event day and delivery. Each stage has its own output. Discovery produces the brief, the proposal produces a scope and quotation, and planning produces the run sheet and venue notes that Modules 2 and 6 develop in detail.

Learners draw the stages as a simple timeline for their own sample project and mark where the client has to make a decision. Those decision points are where schedules slip, so we label them clearly and agree in advance how long each decision may take.

The timeline is also where honesty about time pays off. If a client wants a launch in three weeks and the venue cannot be accessed until the day before, the brief should say so, and the proposal should reflect it rather than hope.

By the end of the session each learner has a one-page brief for an imagined launch, written from a set of rough client notes, along with a list of questions still to be answered. We read several aloud and discuss what a reader who had never met the client would still be unsure about.

This is deliberately a small exercise. The skill being built is reading carefully and writing plainly, not producing an impressive document. A brief that fits on a single page and can be understood in two minutes is more useful than a long one nobody opens.

Prerequisites are modest. You do not need production experience, only a willingness to ask direct questions and write down the answers in order. Learners from marketing and creative backgrounds usually find the session familiar in spirit, even if the vocabulary is new.

The brief is the thread running through every later module. Cue planning draws its running order from it, presenter rehearsals use its timings, and filming and streaming plans depend on the audience section. When a learner gets stuck in Module 4 deciding where to place a camera, the answer is often a line in the brief they wrote in week one.

I return to the brief repeatedly during the course and ask learners to amend it as the project develops. A brief that never changes usually means nobody is reading it. Revising it, with dates noted, is a realistic habit and one that clients tend to appreciate.

If you are weighing whether this course suits you, the first module is a fair preview of the whole: calm preparation, clear questions and a written record of what was agreed.