Project Kickoff Checklist
A project kickoff checklist with a client kickoff agenda: prep, goals, scope, roles, timeline, risks and follow-up, so every project starts aligned.
- Typical schedule per project
- The checklist 5 sections, 23 items
- Variables
{{project}}{{client}}
Use this checklist for the kickoff of any client project, from a two-week landing page to a six-month rebuild. The kickoff meeting is the last cheap moment to find out that the client expects something different from what the proposal says. The checklist covers the preparation, the meeting agenda itself, and the follow-up, because a kickoff without written follow-up is quickly forgotten.
Who owns it
The project manager or account lead owns the run and chairs the meeting. The delivery leads (design, development, content) should attend, and so should the client's decision maker, not only their day-to-day contact.
Common pitfalls
- Re-reading the proposal aloud. Everyone has seen it. Use the time to test assumptions, agree priorities and find risks.
- The real decision maker is missing. If the person who signs off final work is not in the kickoff, expect late changes. Ask for at least the first 30 minutes of their time.
- Vague success measures. "A better website" cannot be checked. Agree on a few concrete outcomes.
- No change process. Agree how new requests are handled before the first one arrives.
The finished run, with the summary linked, is the shared record of what was agreed. It is the document you come back to when scope is questioned later.
The checklist: Kick off {{project}} for {{client}}
Before the meeting
-
Contract, scope and budget reviewed by the whole delivery team
-
Internal pre-kickoff held to agree open questions and risks
-
Client attendees confirmed, including the final decision maker
-
Agenda sent to the client at least two days ahead
-
Questionnaire or brief sent for the client to fill in before the meeting optional
Goals and scope
-
Business goals and the problem the project solves restated by the client
-
Success measures agreed (e.g. launch date, conversion goal, pages migrated)
-
Deliverables and what is out of scope confirmed
-
Assumptions in the proposal checked with the client
-
Target audience and key user journeys discussed
People and process
-
Roles agreed on both sides: decision maker, day-to-day contact, content provider
-
Approval process agreed: who signs off, how many feedback rounds
-
Change request process agreed for work outside scope
-
Communication channel and meeting rhythm agreed
-
Tools agreed and access requested (e.g. project board, design files, staging)
Timeline and risks
-
Milestones and the dates when the client must deliver content or feedback agreed
-
Holidays and blackout periods on both sides noted
-
Main risks and dependencies listed with an owner
-
Technical constraints discussed: hosting, integrations, existing systems optional
Follow-up
-
Kickoff summary with decisions, owners and dates sent within one working day
-
Project plan and timeline shared with the client
-
First milestone and next meeting scheduled
-
Open questions from the kickoff assigned with due dates
Checklist as Markdown
Frequently asked questions
What should be on a client kickoff meeting agenda?
A good agenda covers introductions and roles, the goals and success measures, scope and what is out of scope, the timeline with client dependencies, how approvals and changes work, communication, and the next steps. Leave room for questions about assumptions, because that is where most misunderstandings surface.
How long should a project kickoff meeting be?
For small projects, an hour is usually enough. Larger projects may need half a day, or a series of shorter workshops on goals, users and technical topics. Keep the decision maker for the goals and scope part even if they cannot stay for the rest.
What is the difference between an internal and a client kickoff?
The internal kickoff aligns your own team on scope, budget, risks and open questions before you meet the client. The client kickoff confirms goals, roles and process with the client. Running the internal one first means you arrive with a shared view and good questions.
Updated