Kickoff Meeting Agenda: What to Cover in the First Project Call

A kickoff meeting without an agenda tends to drift — into background context you don’t need, discussion of future phases that aren’t in scope, or time spent answering questions that should have been in the brief. A prepared agenda keeps the meeting focused, ensures you cover what matters, and signals to the client that you run projects with structure.

Here’s the agenda template and what to cover in each section.

The agenda

[Project Name] — Kickoff Meeting Date | [Time] | [Duration: 45 minutes]

1. Project overview and goals
2. Scope confirmation
3. Timeline and milestones
4. Client responsibilities
5. Communication format
6. Open questions and next steps

Send this to the client the day before the call. You don’t need to send a detailed version — a list of topics is enough to help them prepare.

Section 1: Project overview and goals (5 minutes)

Open by stating the project in your own words and asking the client to confirm or correct your understanding. This surfaces any misalignment immediately rather than after work has started.

“Based on the brief and our proposal, my understanding is that we’re [doing X] to achieve [goal Y] by [date Z]. Does that match how you’re thinking about it?”

Ask about success criteria: “What would a successful outcome look like to you? What’s the most important thing this project needs to accomplish?”

The answers here often reveal priorities that weren’t explicit in the brief — and occasionally reveal that the client’s goal is different from what the proposal assumed.

Section 2: Scope confirmation (10 minutes)

Go through the deliverables list from the proposal — or your project brief — and confirm each one. This is the most important part of the kickoff for scope protection.

For each deliverable, ask: “Is [deliverable] what you were expecting? Are there any aspects of this you want to clarify before we start?”

This is also where you confirm what isn’t included. You can do this directly: “The proposal doesn’t include [X] and [Y] — I want to confirm we’re aligned on that before we start, so if those come up later we have a process for handling them.”

Section 3: Timeline and milestones (10 minutes)

Present the project timeline with major milestones. Confirm each date and any dependencies:

• When you’ll deliver the first milestone
• How many days the client has to provide feedback at each milestone
• Any hard deadlines (product launches, events) that the project needs to respect
• Any deliverables that depend on the client providing content or assets first

Any milestone that depends on the client providing something — content, approvals, access — should have a specific “due from client by” date in the timeline, not just a “we deliver on” date.

When the client sees a milestone labeled “Wait for client feedback — 3 days,” they understand that the timeline includes their response time, not just yours. This changes how they approach the feedback process.

Section 4: Client responsibilities (5 minutes)

Clarify what you’ll need from the client and when. Common items:

• Who is the primary point of contact?
• Who needs to approve deliverables at each stage?
• What assets need to be delivered before work begins?
• What’s the turnaround time for feedback at each milestone?
• If there are multiple stakeholders — who has final say?

The approval chain question is especially important on larger projects. Finding out that a deliverable needs sign-off from three people is better learned at kickoff than after the first revision round.

Section 5: Communication format (5 minutes)

Establish how and how often you’ll communicate during the project:

• Primary channel: Where should questions and day-to-day communication happen? (Email, Slack, a project management tool)
• Update frequency: How often will you send status updates? (Weekly email, milestone-based check-ins, a standing call)
• Feedback format: How should the client send feedback? (Inline comments, a shared document, email reply)
• Availability: What are your working hours? What’s your response time for questions?

You don’t need to be rigid — but having agreed-on answers to these questions prevents the situation where a client is texting at 9pm wondering why they haven’t heard from you.

Section 6: Open questions (5–10 minutes)

Leave time at the end for anything that hasn’t been covered. Ask the client directly: “Is there anything you want to make sure we discuss before we start?” and “Is there anything in the brief or proposal that you’d like to clarify?”

Close the meeting with a summary of the confirmed next steps: what you’ll do next, what the client needs to do next, and when the first milestone is due.

After the meeting: send the summary

Within 24 hours of the kickoff, send a written summary covering what was confirmed, any clarifications made, the agreed timeline, and next steps with owners. Keep it to one page or less.

This summary is the foundation of the project record. If a question comes up in week four about what was agreed at the start, this is the document both parties can refer to.

A kickoff meeting that runs on a clear agenda and ends with a written summary sets the professional tone for the entire engagement — and prevents most of the confusion that makes projects harder than they need to be.

Ready to send stronger proposals?

Build, send, and track proposals in one place so follow-up is easier.

Start your free trial →