Project kickoff agenda template

A project kickoff agenda template is a meeting plan for agreeing the project's scope, success criteria, dependency owners and next steps before delivery begins. Fill it from the current project brief and give each discussion a timebox and an expected output. Use it when shared scope or dependencies need discussion, keeping unconfirmed targets marked as proposals.

Short answer

Use this agenda before a team kickoff when shared scope or dependencies need discussion.
Write down what is out of scope as well as what the project includes.
Give each success criterion observable evidence and a date to check it.
Ask each dependency owner to confirm the assignment; keep unaccepted assignments marked as proposed.

What should a project kickoff agenda cover so scope and dependencies are settled early?

For: A project team with a brief that still needs to agree its delivery boundary
What it does: Plans the kickoff around scope exclusions, success criteria and dependency owners.
Works in: Plain Markdown; paste into any notes or docs app

Disclosure. Candor is an app that will compete with some products named here. We describe every product, including Candor, from its own documentation, and we'll test them all with the same published method.

You can join the Candor waitlist at candor.inc. [4]

Use the Copy button on the blank block, or select it and copy. For a plain-text fallback, keep its field labels and put one entry per line. For Google Docs, create a blank document, then paste your copy and check the fields before sharing. [3]

Template

Project kickoff agenda

Prepare before the meeting. Label unconfirmed entries as proposed or unknown.
Repeat a table row for each criterion, dependency or agenda item.

## Meeting details
- Project:
- Date and time (include time zone):
- Duration:
- Meeting link or room:
- Facilitator:
- Sponsor or decision owner:
- Participants and roles:

## Purpose and preparation
- Project purpose:
- What this kickoff should produce:
- Pre-read or source documents, with version and link:
- Preparation requested, owner and due date:

## Scope to confirm
- In scope:
- Explicitly out of scope:
- Assumptions to check:
- Constraints or open questions:

## Success criteria to agree
| Result | Measure or evidence, with source | Proposed target | Check date | Who confirms it | Open question |
|---|---|---|---|---|---|
| | | | | | |

## Dependencies to resolve
| Needed input or decision | Dependency owner | Owner acceptance and status | Needed by | If late, what is affected? |
|---|---|---|---|---|
| | | | | |

## Run of meeting
| Timebox | Topic or question | Lead | Preparation or input | Expected result |
|---|---|---|---|---|
| | | | | |

## Close and follow-through to agree
- Open questions, proposed responder and response date:
- Decision questions for this meeting:
- Proposed next action, owner and due date:
- Where the updated plan and separate meeting record will live:

Filled example

This original fictional example prepares an invoice-export pilot kickoff. All people, source documents and dates are invented. Targets are proposals; no walkthrough has run and no result is reported.

Project kickoff agenda

## Meeting details
- Project: Northstar invoice-export pilot
- Date and time (include time zone): 3 November 2026, 10:00–11:00 India Standard Time (UTC+05:30)
- Duration: 60 minutes
- Meeting link or room: Project room, second floor
- Facilitator: Maya Rao, project lead
- Sponsor or decision owner: Dev Shah, operations director
- Participants and roles: Maya; Dev; Leon Park, engineering; Anika Sen, finance; Nisha Das, support. Invited, attendance unconfirmed.

## Purpose and preparation
- Project purpose: Let pilot users export their invoices as CSV.
- What this kickoff should produce: A pilot boundary and proposed test plan, with unresolved questions assigned for a response.
- Pre-read or source documents, with version and link: Invoice-export brief v0.8, 29 October 2026; shared project folder / Pilot / Brief. Draft walkthrough protocol v0.1 in the same folder.
- Preparation requested, owner and due date: Anika to bring two synthetic invoice samples by 2 November 2026; acceptance pending.

## Scope to confirm
- In scope: CSV export of invoices in the pilot workspace, proposed in brief v0.8 section 2.
- Explicitly out of scope: Billing-page redesign and accounting-system sync, proposed in brief v0.8 section 3.
- Assumptions to check: Pilot users can access their invoice records; Leon to confirm, assignment proposed.
- Constraints or open questions: Support coverage hours and pilot participants are unknown.

## Success criteria to agree
| Result | Measure or evidence, with source | Proposed target | Check date | Who confirms it | Open question |
|---|---|---|---|---|---|
| Pilot users export an invoice as CSV without help | Planned observed walkthrough; protocol v0.1 section 2 | At least 8 of 10 pilot users complete the task | Proposed: 12 November 2026 | Nisha, proposed | Which users will take part? |

## Dependencies to resolve
| Needed input or decision | Dependency owner | Owner acceptance and status | Needed by | If late, what is affected? |
|---|---|---|---|---|
| Final export-column list | Anika, proposed | Acceptance pending; synthetic samples requested for preparation | 5 November 2026, proposed | Export implementation cannot start |
| Pilot workspace access list | Leon, proposed | Acceptance and access review pending | 6 November 2026, proposed | Walkthrough may move past 12 November |

## Run of meeting
| Timebox | Topic or question | Lead | Preparation or input | Expected result |
|---|---|---|---|---|
| 10 min | Purpose and roles | Maya | Brief v0.8 | Shared goal and confirmed responsibilities |
| 15 min | What is in and out of scope? | Dev | Brief sections 2–3 | Boundary or named unresolved question |
| 15 min | How will success be checked? | Nisha | Walkthrough protocol v0.1 | Agreed measure and test date, or gaps to resolve |
| 15 min | Which inputs could block work? | Anika | Synthetic samples; draft access list from Leon | Accepted dependency owners or open assignments |
| 5 min | Close | Maya | Questions still open | Next steps to confirm and record |

## Close and follow-through to agree
- Open questions, proposed responder and response date: Support coverage and pilot participants; Nisha, proposed; response requested by 4 November 2026.
- Decision questions for this meeting: Keep the first pilot CSV-only? Accept the proposed walkthrough target and date?
- Proposed next action, owner and due date: Leon to confirm the pilot access list by 6 November 2026; acceptance pending.
- Where the updated plan and separate meeting record will live: Shared project folder / Pilot / Plan and Pilot / Kickoff record; Maya to update, proposed.

When to use this

Use it when a project has a brief, but contributors still need to settle the delivery boundary. Invite a client or sponsor when their answer changes that boundary. Atlassian's kickoff guidance covers project purpose and roles, includes success tests, and allows teams to adapt its play. [1]

Use the minutes template hub for the later decision record. Keep detailed task estimates and the delivery schedule in a project plan. A one-person task with no shared dependency may only need a checklist.

A kickoff is like agreeing a builder's job before work begins: “renovate the kitchen” still leaves the plumbing boundary unanswered. Write the excluded work beside the included work so someone can challenge the boundary before planning around it. (A heading called “scope” cannot supply the missing answer.)

What to customise

Start with the decisions you need, then set the meeting length. Add the timeboxes and check that they fit; the example totals 60 minutes. If a decision needs evidence that nobody has, assign the missing preparation or defer that item instead of reserving discussion time for a guess.

Add a technical lead or client approver when their authority matters. Remove roles and unused rows. Keep current document versions, use full dates, and spell out the time zone for remote participants.

PMI's July 1995 launch-meeting article discusses scope inclusions and exclusions, restrictions, task ownership and dependencies. It is procedural advice, not a current mandatory agenda standard. [2] Keep this layout optional. Mark a proposed owner as proposed until they accept; “unassigned” is more useful than a name nobody has checked.

Field-by-field guidance

Field-by-field guidance
Field	What to enter	Where to get it	Common mistake
Meeting details	Project, time zone, duration, location, facilitator, decision owner and participant roles	Invite and project brief	Treating an invitee as a confirmed attendee
Purpose and preparation	Project purpose, kickoff output, source version and location; requested prep with owner and date	Current brief and sponsor	Linking an old version or omitting preparation deadlines
In scope	Work the group expects this project to include	Brief, statement of work or sponsor	Listing goals without naming the work boundary
Explicitly out of scope	Nearby work the team is choosing not to include now	Sponsor and project lead	Assuming silence means agreement
Assumptions and constraints	Beliefs to test, limits and unresolved questions	Brief, delivery teams and stakeholders	Writing an assumption as a confirmed fact
Success criteria	Result, evidence source, proposed target, check date, confirmer and open question	Sponsor and people judging the result	Treating a target as a measured result
Dependencies	Needed input, proposed owner, acceptance and status, needed-by date and late impact	People supplying the input	Naming the waiting team instead of the person who can obtain the input
Run of meeting	Timebox, topic, lead, prep and expected result	Facilitator and decision owners	Giving a topic time but no expected output
Close and follow-through to agree	Open questions with responder and response date; decision questions; proposed action with owner and date; plan and record location	Agenda preparer, then participants	Filling in a future decision as if it already happened

Keep observations separate from interpretations. In a fictional preparation note, “the sample has 14 columns” is an observation; “the export is too complex” is an interpretation. After the meeting, put confirmed decisions in the separate record. A proposal stays a proposal until confirmed.

Voice and AI workflow

Dictate preparation notes before the kickoff. Give each note an ID and name its source document or contributor.
Remove confidential or identifying data before pasting anything into AI. If removing it makes the task impossible, fill the agenda yourself.
Supply the blank template and ask for an agenda with source references. An authorised earlier transcript can supply background; it cannot report decisions from the upcoming kickoff.
Check the output against the notes. Confirm every name and any claimed prior decision; check owners and due dates with the people involved. Leave future decisions open.

For work after the meeting, see working from a transcript and recording meetings. A transcript supplies words to check; an omitted answer remains unknown. (Silence supplies no evidence of an accepted assignment.)

Copy this prompt with the blank template and non-confidential preparation notes:

Prepare a project kickoff agenda in Markdown from the supplied blank template
and preparation notes. Preserve its field names and order:
- Meeting details: project, date and time zone, duration, room or link,
  facilitator, sponsor or decision owner, participants and roles.
- Purpose and preparation: project purpose, kickoff output, source versions
  and links, requested preparation with owner and due date.
- Scope to confirm: in-scope work, explicit scope exclusions, assumptions,
  constraints and open questions.
- Success criteria: result, measure or evidence with source, proposed target,
  check date, confirmer and open question.
- Dependencies: needed input or decision, dependency owner, owner acceptance
  and status, needed-by date, and effect of delay.
- Run of meeting: timebox, topic or question, lead, preparation or input,
  and expected result.
- Close and follow-through to agree: open questions with proposed responder
  and response date; decision questions; proposed action, owner and due date;
  location for the updated plan and separate meeting record.

Keep unknowns marked unknown. Mark unaccepted owners and dates as proposed.
Do not invent facts, names, agreement or source references. Preserve source
note IDs beside entries; for authorised earlier transcript excerpts, preserve
speaker and timestamp or section references. Write "Source unknown" when a
reference is absent. Keep conflicting sources visible.

Separate observations from interpretations and proposals from confirmed
prior decisions. Keep the upcoming kickoff's decisions open. Output an
agenda, not minutes. Add supplied timeboxes and flag a mismatch with the
meeting duration; do not invent timings to hide a gap.

Before pasting input, remove confidential or identifying data yourself.
A human must confirm every name, decision, owner and due date before sharing.
Keep unconfirmed entries visibly proposed or unknown.

Non-confidential preparation notes:

What this page can't tell you

The agenda cannot confirm an owner's capacity or a sponsor's authority. Ask the person responsible. Its proposed targets require agreement, and its fields do not replace an approved project plan. Each block has a Copy button; there are no downloadable files.

Questions

What is a project kickoff?

It is a meeting to discuss scope, success criteria, dependencies, and next steps before delivery begins. This template gives those topics timeboxes and expected outputs.

What should a project kickoff agenda include?

Include the project purpose, scope, success criteria, dependencies, and follow-through. This template also asks for an owner and expected result for each agenda item.

How do you run a project launch meeting?

Prepare from the current project brief and give each discussion a timebox and expected output. Keep unconfirmed targets and dependency assignments marked as proposals.

About this page

Candor is being built as personal voice intelligence for everyone. You can join the Candor waitlist at candor.inc. Candor's own documentation is at candor.inc/docs.

Last checked: 4 November 2026. Report an error to support@candor.inc.

Sources

Project Kickoff, Atlassian Team Playbook — https://www.atlassian.com/team-playbook/plays/project-kickoff — checked 2026-11-04
How to manage a project launch meeting, Joan Knutson, PMI — https://www.pmi.org/learning/library/manage-project-launch-meeting-10440 — checked 2026-11-04
Create, view, or download a file, Google Docs Editors Help — https://support.google.com/docs/answer/49114?hl=en — checked 2026-11-04
Candor homepage — https://candor.inc/ — checked 2026-11-04