A project kickoff meeting is the one moment in a creative engagement where the client, the studio, and the brief are all in the same room at the same time. Get it right and the project has a shared foundation to return to when things shift. Miss it and you'll spend the next six weeks resolving disagreements that should never have formed. The agenda isn't a formality. It's a document that does real work.
What a kickoff meeting actually needs to achieve
Most studios schedule a kickoff call without thinking about what it's meant to produce. The goal isn't to repeat the brief back to the client. It's to surface the gaps the brief didn't cover, lock in decisions before production starts, and give everyone a shared reference point for the weeks ahead.
Four things need to come out of every kickoff meeting:
- Confirmed scope, with specific deliverables named and counted
- Clear ownership of each approval stage, with named contacts, not job titles
- An agreed timeline with dates attached, not just phases
- A communication protocol both sides will actually follow
If the meeting ends without all four documented, it wasn't a kickoff. It was a chat.
The agenda, section by section
1. Introductions and roles (5 minutes)
This isn't filler. On larger projects, the client contact who signs off creative may be a different person to the one who briefed the job. West Melbourne Studios runs every kickoff by mapping every name to every role in the room, including who has final approval authority. Knowing that early prevents a revision round from appearing in week four from someone nobody knew was involved.
2. Project overview and objectives (10 minutes)
The studio lead reads back the project objectives in concrete terms and invites the client to correct or add to them. Not "a brand video that represents our values," but "a 90-second brand film for use on the homepage and LinkedIn, targeting procurement managers in the construction sector." Specificity is what makes the objective useful later when decisions need to be tested against it.
3. Scope confirmation (15 minutes)
Walk through every deliverable. Name the formats, durations, aspect ratios, and cut-down versions expected at the end of the job. This is where a well-written statement of work becomes the single most valuable document in the room: the agenda references it, but the SOW carries the binding detail. If there's disagreement between the brief and the SOW, resolve it before the meeting ends.
Scope confirmation is also where most studios underinvest time. Fifteen minutes feels generous until you discover the client assumed three cut-downs were included and your quote covered one.
4. Timeline walkthrough (15 minutes)
Present the full production timeline with specific dates, not week numbers. Week 3 means nothing to a client with a product launch in their calendar. Show them the shoot date, the first cut delivery date, the feedback window, the final delivery date, and the hard deadline. Then ask: are there any dates on your side that would affect this? Public holidays, internal approval freezes, and exec availability can all shift timelines. Better to know now.
5. Review and approval process (10 minutes)
Agree on how feedback gets submitted, by whom, and by when. West Melbourne Studios uses a single consolidated feedback document per round, with one named approver per client. Two contacts sending separate feedback emails creates conflicting directions and revision bloat. The kickoff is the right moment to name the approver and agree on the format.
This is directly connected to how you handle what comes later. A clear approval process is the first defence against scope creep, and scope creep rarely arrives as a single large request. It accumulates in small adjustments across multiple review rounds.
6. Communication norms (5 minutes)
Cover three things: the primary communication channel (email, Slack, project management platform), expected response time from both sides, and who to contact for urgent issues. Studios that skip this section spend the next month chasing replies on three different platforms simultaneously.
7. Open questions (10 minutes)
Leave time for both sides to raise anything the agenda didn't cover. A client who has a concern at kickoff and no space to voice it will raise it at the worst possible moment: during the final delivery round. Give the open questions section a hard time limit and keep a running notes document so nothing drops out.
What to send before and after the meeting
Send the agenda 48 hours before the meeting, not 10 minutes before. Include the SOW, the brief, and the production timeline as attachments. Clients who arrive prepared ask better questions and make faster decisions.
After the meeting, send a written summary within 24 hours. The summary should cover every decision made, every item flagged as unresolved, and the next action for each open item with an owner named. This document becomes the reference point whenever a disagreement surfaces later in the project. It doesn't need to be long. It needs to be accurate and sent quickly.
Common mistakes studios make at kickoff
Running the kickoff as a presentation rather than a conversation is the most common failure. The client sits through 40 minutes of slides and leaves without having been genuinely heard. A kickoff is a working session, not a pitch replay.
The second mistake is treating the meeting as a one-way download of information from studio to client. The most useful kickoffs surface client-side assumptions that the brief never made explicit. Ask questions. What does success look like in six months? Who else will be watching this internally? Has this been tried before?
Third: skipping the kickoff entirely on small projects. Short jobs have the same misalignment risks as large ones, compressed into a tighter timeline with less room to recover. A 20-minute kickoff call on a one-day shoot is worth every minute.
Connecting kickoff to the rest of your process
A kickoff meeting agenda works best when it connects directly to the documents that surround it. The discovery brief that preceded the project feeds into the agenda's objective-setting section. The SOW and the payment terms become the reference documents for scope and invoicing conversations. The project debrief at the end of the job often returns to the kickoff notes to measure what was promised against what was delivered.
Studios that run structured kickoffs consistently report fewer revision rounds, fewer scope disputes, and shorter feedback cycles. Those outcomes aren't coincidental. They're the direct result of decisions made clearly at the start, documented in writing, and referenced throughout.
Build the agenda once, adapt it for each job, and treat the kickoff as the most important 60 minutes in any project. The work that follows will reflect the quality of that first hour.