A kickoff meeting takes ninety minutes. Getting a project to the point where that meeting is worth holding takes a week or two of work that is easy to skip. This free project kickoff checklist gives project managers, PMOs and agency and consultancy delivery leads a workflow from “the project is approved” to “the team is executing”: the mandate and sponsor, a charter with a written scope boundary, stakeholders and a RACI, a baseline the sponsor approves, governance and access, the kickoff meeting itself and the first two weeks of follow-through. Two questions at the start show a client phase for work delivered to an external client and a backlog task for iterative delivery.
A project usually reaches its kickoff through two earlier decisions. The business case decides whether the work is worth doing. The charter, in PMI’s long-standing definition, is the document issued by the sponsor that formally authorises the project and gives the project manager authority to apply the organisation’s resources to it. PRINCE2 puts the same agreement in its project initiation documentation, which acts as the contract between the project manager and the project board. The kickoff is the third step: the point where the people who will do the work hear the authorised plan together, and say what is wrong with it while it is still cheap to change.
Most kickoff checklists are a meeting agenda. The meeting is the easy part. What goes wrong is everything around it: a scope boundary nobody wrote down, a sponsor who has not agreed the budget, a team that arrives on day one without access, or a client who signed a statement of work that says something different from the charter. This checklist starts at approval and ends two weeks into delivery, so the meeting has something solid to present and its decisions are followed up.
If you are still deciding whether to do the project, start with the Business Case Checklist. If the project is under way and you need its documents kept current, the Project Management Documentation Checklist covers the whole lifecycle. On a client project you will usually hold two kickoffs, and they do different jobs.
Seven phases run from confirming the mandate to the first status report. Phase 2 appears only when the project is delivered for an external client, and the backlog and sprint task in Phase 5 appears only when the work is delivered in sprints or iterations.
Answer the two scope questions first. They decide whether the client phase and the sprint setup task appear.
Shown only when the project is delivered for an external client. It runs before the charter so the charter matches the contract.
The sponsor approval at the end halts the checklist. No kickoff invitations go out until it is given.
The backlog task appears only when the work is delivered in sprints or iterations.
Ninety minutes suits a team of up to about a dozen people. Shorten the walkthroughs for a small internal project. For a large one, hold this meeting with the workstream leads and run shorter team sessions after it. The pre-reads go out at least three working days before, so the time is spent on questions rather than reading slides aloud.
The sponsor explains the problem, the decision to fund it and what success looks like from where they sit.
The project manager walks the in-scope and out-of-scope lists. Undecided items are logged with an owner and a date, not debated.
The approved baseline, the critical path, the tolerances and what happens when one is breached.
Each person states what they own. Rows with two Accountables, or none, are settled before moving on.
Review the top five, ask for new ones and give each an owner. Assumptions nobody can confirm become risks.
Status reports, meetings, change control, where documents live and how to escalate.
Read back every decision and action with its owner and date, and confirm when the first status report is due.
For a client kickoff, keep the order and change the content. Let the client sponsor speak in the first slot alongside yours, replace the budget detail with the commercial milestones in the statement of work, and add ten minutes on access, approvals and who signs acceptance. Margins, staffing debates and risks about the client themselves belong in the internal session.
Every task carries a due date offset from the day the checklist starts, so the charter, the sponsor approval and the kickoff pre-reads fall in the right order without a plan for the plan. Tasks are assigned from the sponsor and project manager fields as each kickoff begins.
The charter and baseline stop at an approval step until the sponsor answers, so invitations never go out on a scope nobody has agreed. The approval, the comments and the attached charter stay in the checklist history.
Dropdown answers show the client phase and the sprint setup task only where they apply. Reports show which projects are stuck before kickoff, and the API and MCP server can start a kickoff from your own systems.
Kickoff sets the success criteria that the Project Closeout Checklist tests at the end, and the Scope Change Request Checklist handles changes to the boundary you agree here. Agencies taking on a new account can run the Marketing Agency Client Onboarding Checklist alongside the first project kickoff.
Starting projects across a portfolio, or for clients? CheckFlow’s workflow software runs every project start the same way, and professional services firms use it to make client kickoffs as consistent as internal ones.
Everything that has to be true before the team starts work, not just the meeting agenda. That means a confirmed sponsor and mandate, a charter with measurable objectives, a written scope boundary and success criteria, a stakeholder map and RACI, milestones, budget and named resources, an open RAID log, a governance and change control route, access for every team member, the kickoff meeting with pre-reads, and a check two weeks later that its actions are moving. Client projects add a contract check and a client kickoff.
The charter authorises the project; the kickoff launches it with the people who will do the work. In PMI’s definition the charter is issued by the sponsor, formally authorises the project and gives the project manager authority to use the organisation’s resources. The kickoff meeting comes after that: it presents the authorised objectives, scope and plan to the team and stakeholders and settles roles. Holding a kickoff before the charter is approved asks the team to plan around a scope that may still change.
After the sponsor has approved the charter and baseline, and before the team starts delivery work. The PMBOK Guide Sixth Edition associates the kickoff with the end of planning and the start of executing, while noting that on small projects, where one team plans and delivers, it happens shortly after initiation. Projects with several phases often hold a kickoff at the start of each phase. Either way, the people doing the work should be in the room before they are asked to commit to dates.
The sponsor, the project manager, everyone with a named role in the RACI and the leads of any team the project depends on. The sponsor should open the meeting, because hearing why the project matters from the person funding it carries more weight than hearing it from the project manager. Keep observers out. If the list grows past about a dozen, hold the main session with workstream leads and run short team kickoffs after it.
A client kickoff aligns two organisations on a plan that a contract already constrains, so it starts from the signed statement of work rather than the charter alone. It names the client’s sponsor, day-to-day contact and approvers, agrees reporting and escalation, and confirms access and data handling. Run the internal kickoff first. That is where the team can discuss margin, staffing and risks about the client openly, and it means the client hears one plan.
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
