Agenda for a project kick off meeting (copy-paste template)

The best kickoff agenda is not a longer list of topics. It is a timed, role-assigned script that forces three things onto paper before any work starts: exactly one accountable owner per workstream, an explicit in-scope and out-of-scope boundary plus the change-request process, and shared success criteria everyone signs off on. Most kickoff agendas fail because they turn into a presentation (you talk, the client listens) instead of a working session that produces written agreements. The template below is built to run in 60 minutes, get sent 48 hours ahead with a pre-read, and end with every decision and action item captured as a durable record.

Below is the full agenda first, because that is what you came for. After it, I will explain why each block earns its minutes and which ones you can never cut.

The 60-minute project kickoff agenda (copy, paste, send)

Paste this straight into a Google Calendar invite or a shared doc. Replace the bracketed placeholders. Each block has a time box and, more importantly, one decision it must produce. If a block does not produce its decision, you have not finished it.

PROJECT KICKOFF: [Project name]
Date / time: [date], [start]-[end] (60 min)
Attendees: [client owner], [your PM], [delivery leads], [sponsor]
Pre-read (sent 48h ahead): project brief / charter v0.1, draft RACI

00:00  Welcome + intros (5 min)
       -> Everyone knows who does what and who decides.

00:05  Project purpose: why this, why now (5 min)
       -> One agreed sentence on the business outcome we are after.

00:10  Scope: in / out + change process (10 min)
       -> Written in-scope list, out-of-scope list, and the
          change-request path. THIS is the anti-scope-creep block.

00:20  Plan + milestones (10 min)
       -> Agreed milestone dates and the critical-path dependencies.

00:30  Roles + RACI (10 min)
       -> Exactly one Accountable owner per workstream; one escalation
          contact per side.

00:40  Communication + tools (5 min)
       -> Where updates live, status cadence, response-time norms.

00:45  Risks + dependencies (5 min)
       -> Top 3 risks named with an owner each; client dependencies dated.

00:50  Q&A / open questions (5 min)
       -> Every open question either answered or assigned an owner + date.

00:55  Next steps + action items (5 min)
       -> Read back the action items, owners, and due dates out loud.

The timing is a knob, not a rule. Asana's official kickoff guide recommends 30 to 45 minutes for a simple internal project and 60 to 90 minutes for a complex multi-stakeholder one, with 5 to 10 focused attendees rather than a crowd (Asana, "How to run a project kickoff meeting," accessed 2026-06-12). Atlassian's Project Kickoff Play budgets 90 minutes plus 30 minutes of prep for groups of 3 to 14 (Atlassian Team Playbook, accessed 2026-06-12). Start at 60 and stretch the Scope and Plan blocks for bigger engagements.

1. 1

   Welcome + intros (5m)

   Who is in the room and what they own. Decision: everyone knows the cast.

2. 2

   Purpose (5m)

   Why this project, why now. Decision: one agreed outcome sentence.

3. 3

   Scope: in / out + change process (10m)

   Write both lists live. Decision: the boundary and how changes get approved.

4. 4

   Plan + milestones (10m)

   Dates and dependencies. Decision: agreed milestones.

5. 5

   Roles + RACI (10m)

   One Accountable owner per workstream. Decision: the RACI is ratified.

6. 6

   Comms + tools (5m)

   Where work lives, cadence, norms. Decision: the single source of truth.

7. 7

   Risks + dependencies (5m)

   Top three risks, each with an owner. Decision: risks logged.

8. 8

   Q&A (5m)

   Open questions answered or assigned. Decision: nothing left vague.

9. 9

   Next steps (5m)

   Read back action items aloud. Decision: owners and due dates confirmed.

What a kickoff is actually for (and the number one reason they fail)

A kickoff is not a status update and it is not a pitch. Its job is to convert ambiguity into written, agreed decisions before the team commits real hours. It is an alignment ritual, and the test of a good one is simple: when it ends, is there a finished artifact that everyone signed off on, or just a warm feeling that "we are aligned"?

The most common failure mode is the one-way presentation. You build beautiful slides, walk the client through them, get nods, and leave with agreement-in-the-room and nothing on paper. Two weeks later the scope is contested and nobody can point to where it was settled. The fix is to anchor the entire meeting to one document. PMBOK calls this the project charter: a document issued by the sponsor that formally authorizes the project and gives the project manager authority to apply resources. Its standard contents are the project purpose, measurable objectives and success criteria, high-level requirements, scope boundaries and deliverables, assumptions and constraints, a summary milestone schedule, the key stakeholder list, approval and exit criteria, and the sponsor's authorizing sign-off (CSU Ohio, "Project Charter," PMBOK-based, accessed 2026-06-12). Your kickoff blocks map one-to-one onto those charter sections. The meeting ends when the charter is ratified, not when the hour runs out.

One more non-negotiable: send the agenda and the pre-read at least 48 hours ahead. If people walk in cold, you will spend the hour delivering context that a one-page brief could have carried, and you will run out of time before the blocks that prevent failure. The pre-read is what lets the hour be about resolving, not informing. See our meeting preparation checklist for the full pre-send routine.

Internal vs client kickoff: same bones, different polish

The agenda above works for both, but the emphasis shifts. Asana's guidance is worth internalizing here: an internal kickoff exists to align the delivery team on objectives, roles, and cadence with minimal polish, while a client or external kickoff should be "the most polished version," built to set expectations, establish business value, and build trust (Asana, accessed 2026-06-12). The smart move at an agency is to run the internal kickoff first, workshop the plan there, then face the client with a clean story.

Internal kickoff

• Goal: align the delivery team on objectives, roles, and workflow.
• Attendees: the people doing the work, plus the PM.
• Polish: low. Whiteboard and argue freely.
• Heaviest blocks: Roles/RACI and Plan/milestones.
• Run it first to pressure-test the plan before the client sees it.

Client / agency kickoff

• Goal: set expectations, establish business value, build trust.
• Attendees: client owner, sponsor, your lead, key delivery leads.
• Polish: high. This is the most polished version.
• Heaviest blocks: Scope boundary + change process, and Comms.
• Add: budget boundary, client-side approval owner, cross-org escalation path.

If you run client work, the agency-specific add-ons matter: name the client-side approval owner (who signs off on deliverables), agree the budget and scope boundary explicitly, and write down the escalation path between the two organizations. Our guides on managing client expectations and the project management workflow for agencies go deeper on the relationship side.

The three blocks that actually prevent project failure

If you only get three things right, get these. They are the difference between a project that drifts and one that ships.

1. Scope, written live. During the Scope block, do not describe the work in prose. Open two lists, "In scope" and "Out of scope," and fill them on the screen while everyone watches. Then write the change-request process: who can request a change, who approves it, and what it does to the timeline and budget. Asana ties unmanaged scope directly to scope creep and recommends clarifying scope early and often (accessed 2026-06-12). The out-of-scope list is the one people skip and the one that saves you. For the full defensive playbook, see how to prevent scope creep.

2. Roles via RACI, not a name list. Listing "who is on the team" is not the same as assigning accountability. A RACI matrix gives every task four roles: Responsible (does the work), Accountable (the single owner who answers for completion), Consulted (gives input before the work is done), and Informed (kept up to date). The hard rule is that every workstream has exactly one Accountable owner (Atlassian, "RACI chart," accessed 2026-06-12).

3. Success criteria, measurable. Before the meeting ends, write the definition of done that everyone can agree to. Atlassian frames these as Mission Tests: the indicators that tell you the project succeeded. PMBOK calls them success criteria and exit criteria. Either way, they must be measurable, not aspirational. "Launch the new site" is not a success criterion. "New site live on [date], passing [load-time target], with [conversion baseline] measured for two weeks" is. If you cannot measure it, you cannot agree on whether the project worked.

Map the agenda to the charter (so "done" is unambiguous)

Here is the trick that makes a kickoff feel inevitable instead of improvised: each agenda block fills one section of the charter. Run the meeting and the charter fills itself in.

Agenda block	Charter section it completes
Purpose	Project purpose + measurable objectives
Scope: in / out + change process	Scope boundaries, deliverables, change control
Plan + milestones	Summary milestone schedule
Roles + RACI	Project team + key stakeholder list
Risks + dependencies	Overall risk, assumptions, constraints
Success criteria (in Purpose + Q&A)	Approval and exit criteria
Next steps	Sponsor sign-off to proceed

When the last cell is filled, you are done. If a cell is still blank, that is your remaining open question, and it gets an owner and a date in the Next steps block. For the artifact itself, our project summary template and project kickoff meeting agenda post give you fill-in-the-blank starting points.

Capture the alignment so it survives the meeting

You fought for written scope, a clean RACI, and measurable success criteria. All of it evaporates if the only record is a few hurried notes. The durable output of a kickoff is three things: a transcript, a decisions log, and action items with owners and due dates, distributed the same day before anyone's memory fades.

If your team is on a paid Google Workspace plan, native Meet recording can help, but know the limits. Recording is gated to specific paid editions (Business Standard/Plus, the Enterprise tiers, Education Plus, Workspace Individual, and Google One 2TB and up), the recording saves to the organizer's Meet Recordings folder in Drive, and free or personal Google accounts cannot record at all (Google Meet Help, "Record a video meeting," accessed 2026-06-12). A raw recording also is not a decisions log or an action-item list. Someone still has to watch it back and type those up.

This is the one place Scribbl is honestly the right tool. Scribbl is an AI notetaker for Google Meet that records, transcribes, and auto-extracts action items from your kickoff with no bot sitting in the meeting, then produces a shareable recap. It runs from the browser, it is free for individuals, Pro adds unlimited recording, and Team adds Zoom and Microsoft Teams. For project managers specifically, the PM workflow is the same loop every time.

The full loop is: send the agenda and pre-read 48 hours ahead, run the timed kickoff, let the recap tool capture decisions and action items as they are agreed, then distribute the recap and assign owners before everyone leaves the call. For the assigning side, our action items template and meeting action items template keep the format consistent across every project.

Frequently asked questions

How long should a project kickoff meeting be?

Start at 60 minutes. Asana recommends 30 to 45 minutes for a simple internal project and 60 to 90 minutes for a complex, multi-stakeholder one (accessed 2026-06-12). The variable that drives length is the Scope and Plan blocks, so stretch those for bigger engagements and keep intros tight. Atlassian's play budgets 90 minutes plus 30 minutes of prep for groups up to 14 people.

Who should attend the kickoff?

Keep it to 5 to 10 people who can actually decide and do the work: the project sponsor, the project manager or lead, the delivery leads for each workstream, and on a client engagement, the client owner and their approval authority. A crowd of observers slows decisions. If someone only needs the outcome, send them the recap instead of a seat.

What is the single most important part of the agenda?

The Scope block: writing the in-scope and out-of-scope lists plus the change-request process live, in front of everyone. It is the best defense against scope creep, and it is the block people most often rush. The Roles/RACI block is a close second, because exactly one Accountable owner per workstream is what makes the scope decisions stick.

How is a kickoff agenda different from the project charter?

The agenda is the script for the meeting; the charter is the artifact the meeting produces. Each agenda block fills one charter section (purpose, scope, milestones, team, risks, exit criteria). When the charter is fully filled in and signed off by the sponsor, the kickoff is genuinely done.

Do I need to record the kickoff?

You need a durable record, which is not the same as a video file. The minimum is a decisions log and action items with owners and due dates, shared the same day. A recording and transcript make that easier and let people who missed it catch up. Native Google Meet recording requires a paid Workspace edition and saves to the organizer's Drive (accessed 2026-06-12); a tool like Scribbl works on free Google accounts and turns the call into a recap with action items automatically. For the manual approach, see how to take better meeting notes.