Project Kickoff Meeting Agenda: Template + Example

A project kickoff meeting agenda for a client engagement runs 60 to 90 minutes in eight blocks: introductions, why the project exists, scope and deliverables, roles and decision rights, success criteria, risks, ways of working, and the first-week plan. Send a pre-read two working days before, and close by reading decisions and actions back to the room.

Send the pre-read two working days ahead, so people arrive having read the scope rather than meeting it for the first time in the room.

• The agenda, with the time and the outcome for each block, so people know what they are deciding, not only what they are discussing.
• A one-page brief: objective, scope in and out, deliverables and dates, as agreed in the proposal or statement of work.
• A draft roles table (below), so the room corrects names instead of starting from a blank page.
• Your list of inputs and access: data, documents, systems and people to interview, each with the date you need it.
• The attendee list with roles, and the two or three questions you need answered in the room.

Then hold a 30-minute internal kickoff with your own team: who presents which block, who takes notes, which scope lines you will not move without a change request, and what you will ask the client for.

Only have 60 minutes? Keep the same blocks and cut them to 5, 5, 10, 10, 10, 5, 5 and 10 minutes. Scope, roles and the read-back are the last places to save time.

A full RACI matrix with every task is too much for a kickoff, and nobody reads it. Use a short version: one row per deliverable or decision, four columns, and one rule: exactly one approver per row.

If two people on the client side each think they approve the same deliverable, settle it in the kickoff. Finding out at the final presentation is the expensive version.

A success criterion is a measure, a baseline, a source and a date. "Improve efficiency" is none of those. Agree two or three, and write down where each number will come from, so nobody argues about the data at the end.

Separate the client’s outcome from your deliverable. You control the recommendations; the client controls whether the cost falls. Say which is which, out loud, in the kickoff.

Ask the room: what could stop this project in the next eight weeks? On client engagements, the same risks come up again and again:

• Data or system access arrives late.
• Key people have no time: holidays, a year-end close, another project.
• The sponsor changes or loses interest.
• Scope grows one small request at a time.
• The client team expects the firm to do work the proposal left to them, or the other way round.

Book the whole series before the meeting ends. A cadence that lives only in the minutes slips by the second week.

Close the kickoff with the next five working days on both sides. Most early delays sit with the client, so their column matters as much as yours.

Here is the agenda run end to end for a made-up engagement, with what each block produced.

• Engagement: regional logistics company, warehouse cost review, 10 weeks. Client: Sofia (CFO, sponsor), Marc (operations director, day-to-day contact), Ines (IT lead). Firm: Lena (lead), Omar (analyst, notes).
• 0-10 min: introductions. Lena states the goal: leave with agreed scope, approvers, success measures and a first-week plan.
• 10-20 min: Sofia explains that warehouse costs have risen three quarters in a row, and the board wants a plan in January.
• 20-35 min: in scope: three warehouses and outbound shipping. Out: suppliers, IT systems, pricing. Deliverables: current-state report on 4 December, recommendations on 15 January 2027. Scope changes go to Sofia in writing.
• 35-50 min: approvers agreed as in the roles table above; Marc is the single day-to-day contact.
• 50-60 min: success = cost per order shipped, from the monthly finance report, against the Q3 average. The firm’s deliverable = a decision paper for the January board.
• 60-70 min: risk: the data extract depends on Ines’s team during a system upgrade; owner Ines, next step: a date by Friday. Assumption: each site manager gives 45 minutes for an interview.
• 70-80 min: weekly status on Mondays at 09:00; steering committee every four weeks, chaired by Sofia; one shared folder.
• 80-90 min, read-back: data request out today (Omar, firm); extract date by Friday (Ines, client); interviews booked by Wednesday (Marc, client).

An internal project kickoff, with only your own team, uses the same agenda with two changes. The "why" comes from the proposal and the sales conversation instead of the sponsor, and more time goes to who does what inside the team and what you will ask the client for. Hold it before the client kickoff, not after.

The kickoff only counts once it is written down. Send two things within one working day: the kickoff minutes, which are the record of what was agreed, and a short follow-up email that people will actually read.

For the minutes, add the kickoff block (objective, scope, deliverables, roles, ways of working, inputs and assumptions) above the usual decisions, actions, risks and open questions. Our consulting minutes template has it with a filled example.

A recording helps you check what the sponsor actually said about scope or dates before it goes into the minutes. Reline’s desktop app records your microphone and the system audio on your computer, with no bot joining the call, and transcribes the meeting live while it records. Capture is local; transcription, AI and storage run in the cloud. Transcription covers 60+ languages.

To get the kickoff back in the shape above, start from a Lens. In the app, go to Lenses, open Action Items with Owners and press "Add to my workspace": you get your own copy, which you can edit to add the kickoff blocks (scope, approvers, success criteria, risks). Run it by typing its command in the kickoff note’s chat, and use Draft Follow-Up Email for the email. Keep the note in the client’s folder: later, a question in that folder’s chat draws on its notes.

Every draft is a starting point. Check each scope line, approver and date against the transcript, where you can press play on any line to hear it again.

• On a call, transcript lines are labeled as you or the other side, not person by person, and in a meeting room everyone reaches the laptop through one microphone. Write the owners’ names yourself.
• Reline transcribes live only. It cannot transcribe a recording you already have or an uploaded file; for a past meeting, use the meeting platform’s own transcript.
• It records audio and the transcript, not video or the screen.
• There is no SOC 2 report. A DPA is available. If a client contract asks for a certification from your tools, check before you record.
• The free plan includes 10 hours of transcription and up to 1 hour of recording per note, so a 90-minute kickoff runs past what one note can hold. Professional ($15 a month) removes both limits.

Often, you need their agreement. Recording a conversation can require the consent of everyone on it, and the rules differ between countries, regions and employers. Reline puts no notice in the meeting, so telling people is your job: say at the start that you are recording and why, offer to stop if anyone objects, and check the rules where everyone on the call is. Check your client contract too: some say whether meetings may be recorded. This is general information, not legal advice.

Eight blocks, one outcome each, a pre-read two days before and the minutes the day after. Copy the agenda, swap the example for your client’s names, and send it.