Kick off meeting: agenda, checklist, example — for a project and for a new client, and how the kickoff becomes the channel (2026)

A kick off meeting is the first meeting of a project: the one where the people who will do the work agree what the project is for, what "done" means and by when, who owns which part, how they will communicate while it runs, and what could go wrong — before any of the work starts. It is held once per project, and once per client when a new engagement begins. A project with a kickoff has a record of what everyone signed up to; a project without one finds out in week six that two people were building different things.

This guide is the craft first — what the kickoff must leave behind, the checklist for before, during and after, a 60-minute agenda you can copy, two filled-in examples — then the mechanics: where the record lives in the tools your team already uses, what the person outside your organization gets, and what happens to the kickoff after it ends. Because the kickoff's real test is not the hour itself. It is the month after, when a new person joins the project and asks where to read what was agreed.

What a kick off meeting is — and what it isn't

Four meetings sit around the start of a project, and they are often confused:

The kickoff is the third one, and it exists because the first two were held by a few people. The discovery call decided that the project is worth doing; the planning meeting decided how; the kickoff is where the whole team — and the client, if there is one — hears the same version and gets to say "that is not what I understood". It is not the planning meeting with more people in the room, and it is not a presentation of the plan: a kickoff where nobody but the lead speaks has produced a deck, not an agreement.

What the kickoff must leave behind

Everything a kickoff should contain follows from the five things it must produce. Write these five down before you write the agenda; if an item on the agenda serves none of them, it belongs in a message.

1. The purpose, in one sentence, with the person it is for. "Replace the warehouse system before the autumn season so the Lisbon depot ships the same day" — not "warehouse project". The sentence is what the team will measure the scope creep of week eight against.
2. The definition of done, and the date it is judged on. What exists at the end that does not exist now, and who says it is done. A kickoff that ends without a date and a judge has postponed its hardest decision to the moment it is most expensive.
3. The workstreams, with one owner each. Not a team per stream — a name. The owner is the person who will be asked in the weekly where the stream is, and who can say "we are late" without checking with anyone.
4. How the project communicates. Where the project's messages live, when the weekly happens, who writes the recap and where it goes, and how someone escalates. This is the item most kickoffs skip because it feels administrative; it is the one the month after is made of.
5. The risks each person already sees, and the first next steps. Everyone in the room has already spotted something that worries them. Five minutes of saying it aloud at the start costs less than discovering it in a status meeting. Then: the first three actions, with names and dates.

What stays out: the detailed schedule (a pre-read), the budget line by line (the sponsor's meeting), and anything that only two people need to discuss.

The kick off meeting checklist: before, during, after

Before — a week to a day ahead.

• Write the purpose sentence and the definition of done as a draft, and send them with the invitation. The kickoff confirms or corrects them; it does not discover them from scratch.
• Choose the people: everyone who will own a workstream, the sponsor, and — for a client project — the client's decision-maker, not only their project contact. Anyone who is "nice to have" gets the recap instead.
• Post the pre-reads where the project will live from now on: the brief, the statement of work or the plan, the draft schedule. Three documents at most. A kickoff where the pre-reads arrive during the meeting spends its first twenty minutes reading.
• Book the time with the agenda inside the invitation, item by item with minutes, so that people arrive knowing the meeting ends with owners and dates.
• Open the place the project will live in — the channel — before the kickoff, with the invited people already in it, so that the first message of the project is the agenda rather than "where do I find the link".

During — run the list, not the clock.

• Open with the purpose sentence, read aloud by the sponsor or the client, not by the lead. Hearing the person who wants the result say what the result is changes what the room agrees to.
• For the definition of done, ask one question and wait: "On the date, what will exist that does not exist now?" Write the answer down in front of everyone while they watch.
• Go through the workstreams one by one, and leave each one only when a name is next to it. "The design team" is not a name.
• Spend ten real minutes on how the project will communicate: the channel, the cadence of the weekly, who writes the recap, how something urgent is raised. Decide, do not describe.
• Do the risk round as a round: each person, one risk, one sentence, no discussion. Park anything that needs a decision.
• Reserve the last five minutes to read the outcomes back: purpose, done, owners, how we work, risks, first actions with names and dates. Reading it aloud is what turns a conversation into a record while everyone who had it is still there.

After — the same day.

• Publish the recap to everyone invited, including the people who could not come: the five outcomes, the decisions, the actions with names and dates, the parking lot.
• Put it where the project lives, not in one person's notes, so that it is the first thing a new member of the project reads.
• Create the weekly from the kickoff — same place, same link, the cadence you agreed — before the day ends. A kickoff whose weekly is scheduled "next week" has already lost the first one.
• Start the actions. The first three should be visible as done or in progress by the first weekly, or the kickoff has taught the team that dates are decorative.

A kick off meeting agenda template

[Project name] — kick off meeting
Date: [date] · Time: [start]–[end] · Link: [meeting link]
Purpose: [one sentence — what this project produces and for whom]
Facilitator: [name] · Recap: [name or "the recap"]
Pre-reads: [the brief], [the plan or statement of work], [the draft schedule]

1. Why this project, and for whom — sponsor or client — 10 min — information
[The purpose sentence, read by the person who wants the result. One question each from the room.]

2. What done means, and the date it is judged on — project lead — 15 min — decision
[What exists at the end that does not exist now; who judges it; the date.]

3. Workstreams and owners — project lead — 15 min — decision
[One line per workstream: what it delivers, who owns it, its first milestone.]

4. How we work: channel, weekly, recap, escalation — project lead — 10 min — decision
[Where messages live; the day and time of the weekly; who writes the recap and where it goes; how something urgent is raised.]

5. Risks each person already sees — everyone — 5 min — discussion
[One risk per person, one sentence each; parked, not solved.]

6. Outcomes and first actions — facilitator — 5 min
Purpose, done, owners, how we work, risks — read back. First actions: [name] — [task] — by [date].

Parking lot: [raised, not decided — carried to the first weekly]

Sixty minutes is the usual booking: items 2 and 3 are the ones that run over, so the agenda gives them half the hour. For a small project with three workstreams, forty-five minutes works; a kickoff that needs two hours is usually a planning meeting that has not happened yet.

Two filled-in examples

Internal project kickoff — a new warehouse system, 60 minutes

A 60-person distributor in Valencia replaces its warehouse software with an integrator's team in Bucharest. The sponsor is the operations director; the team is the warehouse lead, the finance lead, the integrator's project manager and two of their developers.

Purpose: ship from the new system before the autumn season, so that the Lisbon depot ships the same day it receives an order.
1. Why this project, and for whom — Marta, operations director — 10 min — information
2. Done means: all three depots on the new system by 15 September, judged by Marta on the first full week of live orders — Andrei, project lead — 15 min — decision
3. Workstreams: data migration (Andrei), warehouse process and training (Luis), finance integration (Carmen), go-live and support (Ioana) — 15 min — decision
4. How we work: the project channel; weekly on Tuesday 10:00; recap written from the meeting and posted to the channel; anything blocking a depot goes to Marta the same day — 10 min — decision
5. Risks: the barcode printers in Lisbon, the finance close in August, two developers on holiday in the same fortnight — everyone — 5 min — discussion
6. Outcomes and first actions — 5 min
Leaves behind: the project's first record — done means X by 15 September, four owners, a channel and a weekly, three risks with a name next to each.

Client kickoff — an agency starts a six-month engagement, 60 minutes

A 25-person agency in Lyon starts a new website and campaign for a client in Madrid. The client's marketing director and their e-commerce lead join; the agency brings the account lead, the project manager and the creative lead.

Purpose: launch the new site and the first campaign before the client's spring collection, with the client's team able to run the site themselves afterwards.
1. Why this project, and for whom — Elena, client marketing director — 10 min — information
2. Done means: site live in two languages by 1 March, campaign live by 15 March, the client's team trained to publish; judged by Elena against the statement of work — Claire, project manager — 15 min — decision
3. Workstreams: content and structure (Elena's team), design and build (Julien), campaign (Claire), training and hand-over (Julien) — 15 min — decision
4. How we work: one shared channel for both sides; weekly on Thursday 14:00; recap to both sides the same day; changes to scope go to Elena and the account lead, not into the channel as a request — 10 min — decision
5. Risks: product photography not ready until January, two approvers on the client side, the payment provider's integration — everyone — 5 min — discussion
6. Outcomes and first actions — 5 min
Leaves behind: a definition of done the client said yes to in the room, one channel both sides read, and the first weekly in the calendar.

The shape of the two is the same; what differs is who reads the purpose sentence and who judges done. The remaining items of a project's life — the weekly, the stand-up, the review — have their own agendas in meeting agenda examples; the anatomy of the format is in the meeting agenda template guide.

Client kickoff: what changes when the other side is the client

Three things change when the kickoff is with a new client rather than with your own team.

The client reads the purpose sentence, and the client judges done. In an internal kickoff the sponsor says what the result is; in a client kickoff the client does, in their words, and the team writes those words down rather than translating them into the agency's. The definition of done is read against the statement of work, line by line, in the room — the kickoff is the last cheap moment to find that the client expected three languages where the proposal said two.

Two sides, one record. A client kickoff produces one agreement, not two sets of notes. The recap goes to both sides the same day, from the same text; a client who receives a different summary than the team has not been in the same meeting. The same holds for the channel: one place both sides read, where the agency's question and the client's answer sit next to each other, rather than an internal channel and an email thread with the client.

The client's people are not your organization. They have their own tools, their own accounts, often their own language. Whatever you use for the kickoff, the question to answer before sending the link is what the client's decision-maker needs to join from a phone between two other meetings — an account, an app, a licence — and what they will have afterwards: the record, or only their memory of it.

Where the kickoff's record lives in the tools you already use

Each major platform has a place for the agenda and a form of record after the meeting, and each stops at a different point for the person outside the organization. Documented behaviour only, from the vendors' own pages; each cell names the month its fact was checked.

Two things are the same across the four. The record of the kickoff is one document or one summary, in the language the room used; and for the person outside the organization, each page cited draws a line — the notes an external attendee cannot open, the email an unauthenticated participant does not get, the document shared with hosts only. Where that is fine, the table is the whole answer and any of the four will do. Where the project has two sides, the next section is one way the job gets done.

How the kickoff becomes the channel

InterMIND is a communication space where a meeting lives in a channel, so the kickoff has an obvious continuation: the channel it was held in is the project. The channel's chat is kept between sessions, its meeting link is permanent, and the weekly is set once, in Google Calendar or Outlook, on an event that carries that link — the same room opens every Tuesday, with the kickoff's agenda one scroll up. A channel created from the calendar event takes its title from the event.

The agenda is a note in the channel's chat, posted the day before, with the pre-reads next to it — a PDF or a Word file dropped into the channel, or a Google Doc or OneDrive document linked from it. During the kickoff, the facilitator puts the note on everyone's screen with Share to conference: it opens next to the video tiles for every participant, the facilitator edits it live as the room decides — done means this, by this date, this owner — and each participant reads it in their own language, with the original a toggle away. The brief itself can go on every screen the same way, late joiners included. The whole space works like that: a message typed in French is read in Spanish by the client's e-commerce lead, in Romanian by the integrator's developer and in French by the sender, as are the files, the notes and the recap — the chat, the recap and the history, not one meeting at a time.

When the kickoff ends, the recap is written from the meeting itself: a summary, the points marked agreed, open or disputed, the action items with owners, each line keeping its timestamp. It arrives by email, as a message in the channel and as a link in the calendar event, and every signed-in member reads it in their own language — the record is translated per reader, not written once in the language the room happened to use. Any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session, so on the first weekly the kickoff's definition of done is one click away, and in month four the new designer reads the whole project from its first hour. The host can add a recap copy to any address — the client's project mailbox, a CRM inbox — so the outcomes reach the system of record without anyone forwarding anything.

For a channel's recurring meeting, the open action items of the previous session are read back when the next recap is written and judged against what was said: an item someone reported finished is marked done, anything else is marked not done with the reason in the words of the meeting, or "not discussed" — and at the start of the next session Mia names the open items and their owners, so the kickoff's first three actions are spoken about at the first weekly rather than lost. This part runs for selected accounts while it is being refined.

The client's decision-maker who is in the kickoff only joins by link, without an account and at no cost — from a phone, in the browser, by typing a name — and the host admits them. They hear the meeting live in their own language and read the agenda on their screen in it. There is no record for a guest afterwards: a guest of one meeting gets nothing after it ends, and the chat of a call held outside a channel is wiped when the call ends. The client's people who should read the project are added to the channel by email instead, onto a free account; from then on they read the whole channel — every message, every file, every recap — in their own language, and every call from the channel is theirs to join. The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat, asked Mia; members who go quiet keep their access at no cost, and the client's people in the channel are not counted.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

The kickoff as a craft survives every tool: somebody still has to get a sponsor to say what done means and a name next to each workstream. What does not have to survive is the second project — the one where the record is rewritten by hand, in one language, for a client who reads another.

FAQ

What is a kick off meeting?

A kick off meeting is the first meeting of a project, held once at its start, where everyone who will do the work — and the sponsor or the client — agree what the project is for, what "done" means and by when, who owns each workstream, how the project will communicate, and what risks they already see. It produces the project's first record; the planning that came before it was done by fewer people, and the kickoff is where the whole team hears one version and can correct it.

What is the purpose of a kickoff meeting?

To put one shared understanding in the room before any work starts. Five outcomes: a purpose sentence naming who the result is for; a definition of done with a date and a judge; a named owner per workstream; the way the project communicates — channel, weekly, recap, escalation; and the risks each person already sees, with the first actions dated. A kickoff that produces these five has done its job; one that presents the plan and takes questions has produced a deck.

How do you run a kickoff meeting?

Send the purpose sentence and the draft definition of done with the invitation, with the pre-reads posted where the project will live. In the meeting, let the sponsor or the client read the purpose aloud; decide done and its date in front of everyone; leave each workstream only when a name is next to it; decide how the project communicates rather than describing it; run the risks as a one-sentence round; and spend the last five minutes reading the outcomes back. Publish the recap the same day, in the project's channel, and create the weekly before the day ends.

What should be included in a kickoff meeting agenda?

Six items in an hour: why this project and for whom (10 minutes, the sponsor or client); what done means and the date it is judged on (15, decision); workstreams and owners (15, decision); how we work — channel, weekly, recap, escalation (10, decision); risks each person already sees (5, a round); outcomes and first actions, read back (5). The template above is this list with the placeholders; the two examples are it filled in.

How long should a kickoff meeting be?

Sixty minutes for most projects, forty-five for a small one with three workstreams or fewer. The two decision items — done and owners — take half the hour; everything else is shorter than people expect once the pre-reads were actually read. A kickoff that needs two hours is usually missing its planning meeting: the room is estimating and sequencing, which is a different meeting with fewer people.

Who should attend a kickoff meeting?

Everyone who will own a workstream, the sponsor, and — for a client project — the client's decision-maker, not only their day-to-day contact. The people who need to hear the agreement but will not own anything get the recap; a kickoff with twenty people in it is an announcement. One test per name on the invitation: will this person be asked, in the first weekly, where something stands? If not, they read the recap.

What is the difference between a kickoff meeting and a project planning meeting?

The planning meeting produces the plan — scope, phases, estimates, a draft schedule — and is held by the lead with the people who estimate. The kickoff takes that plan to everyone who will do the work and to the sponsor or client, and produces agreement: the same purpose, the same definition of done, named owners. Planning comes first; a kickoff held without it spends the hour planning in a room too large for it.

What is a client kickoff meeting?

The kickoff held with a new client at the start of an engagement. It follows the same agenda, with three differences: the client reads the purpose sentence and judges done, against the statement of work, in the room; both sides get one recap from the same text the same day; and the client's people join from their own tools and often their own language, so the choice of where the kickoff is held decides what the client can open afterwards — the notes, the summary, the channel — and what they cannot.

Is it "kick off meeting", "kickoff meeting" or "kick-off meeting"?

All three name the same meeting; the spelling varies by region and by house style, and the search box treats them as one query. Use one spelling in your own documents and do not worry about it in anyone else's.

Sources: Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Recap in Microsoft Teams; Zoom — Using Meeting Summary with AI Companion; Zoom — Generating meeting agenda with AI Companion; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Slack — Use huddles in Slack; Slack — Meeting agenda template. Vendors change plans, features and language lists over time; check their pages for the current state. Each table cell names the month its fact was checked — the earliest checked August 2026, the latest checked October 2026.