Project kickoff checklist

What You Need for a Project Kickoff

A project kickoff is not a ceremonial gathering. It is the moment you align goal, scope, owners, risks, and communication so that everyone knows what they are building, why, who decides what, and what happens when something goes wrong. Without this alignment, the project drifts, work gets duplicated, and the wrong person makes the wrong decision at the wrong time. The checklist below gives you one usable method. Every item states its purpose and which official source must verify it. Use it as your decision rule, not a generic introduction.

Define the Outcome and the Boundaries

1. Define the Outcome with SMART Criteria

Start with the outcome, not the tasks. A vague goal produces a vague plan. Use the SMART framework (Specific, Measurable, Achievable, Relevant, Time-bound) to write a single sentence that passes this test: “By [date], [team] will deliver [measurable result] that meets [specific requirement].”

• Purpose: Without SMART criteria, you cannot tell if the project succeeded. The Project Management Institute (PMI) PMBOK (7th edition, 2021) states that clear success criteria must be agreed before work begins.
• Verification: Write the goal down and have the sponsor sign it. No verbal agreement counts.

2. Document the Scope (Boundaries, Deliverables, Exclusions)

Scope is the line between what is in the project and what is out. Write three lists: deliverables (what you will produce), boundaries (what the project covers), and exclusions (what it explicitly does not cover).

• Purpose: Uncontrolled scope (scope creep) is the most common reason projects fail. The UK government’s Infrastructure and Projects Authority (2022) reports that 60% of project overruns are caused by scope changes not managed through a formal process.
• Verification: The scope document must be reviewed and approved by the project sponsor and key stakeholders before any work begins.

3. Agree on Success Criteria Before Start

Success criteria are the measurable conditions that prove the project is done. They are not the same as the goal. For example: “The website loads in under 2 seconds on a mobile device” is a success criterion.

• Purpose: Without success criteria, the project ends when someone says it ends, not when it meets the agreed standard. The SMART goal gives you the outcome; success criteria give you the measurement.
• Verification: Write success criteria in the authorising document and share them with the team at the alignment session.

Assign Ownership and Manage Risk

4. Name the Single Accountable Owner

One person must be accountable for the project’s success. That person has decision rights on scope, budget, and timeline. If no single owner exists, decisions get delayed or made by the wrong person.

• Purpose: The RACI (Responsible, Accountable, Consulted, Informed) model from PMI PMBOK clarifies that the Accountable person has final say. Without it, multiple people assume someone else is in charge.
• Verification: The formal authorisation document must name the accountable owner. That document authorises the project (PMI PMBOK, 7th edition,2021).

5. Identify Risks and Assign Owners

A risk is not a problem yet. It is something that might happen. Identify risks by brainstorming with the team and stakeholders. For each risk, write: the event, the likelihood (low/medium/high), the impact (low/medium/high), and the mitigation action.

• Purpose: ISO 31000 (2018), the international risk management standard, requires that risks be identified, analysed, and assigned an owner. A list of risks without owners is a list of unsolved problems.
• Verification: Use the ISO 31000 risk matrix format. Do not skip the “owner” column.

6. List Stakeholders by Name, Role, and Influence

Every person who can affect or be affected by the project is a stake holder. List them with their role, influence level (high/medium/low), and what they expect from the project.

• Purpose: A stake holder who is ignored will block the project later. The PMI PMBOK (2021) includes stake holder identification as a key process in the initiating phase.
• Verification: The stake holder list must be reviewed with the sponsor before the alignment session.

Plan Communication and Authorisation

7. Build a Communication Plan

Define who needs to know what, how often, and through which channel. A communication plan prevents information overload and ensures the right people get the right updates.

• Purpose: The PMI PMBOK states that a communication plan must specify frequency, audience, and channel. Without it, stake holders either get too many emails or miss critical updates.
• Verification: Write the plan in the formal authorisation document. Examples: weekly status email to all stake holders, daily stand-up for the team, monthly steering committee session.

8. Create the Formal Authorisation Document

This is a one-page document that authorises the project, names the project manager, assigns the accountable owner, and states the goal, scope, and success criteria. It is the first document you produce.

• Purpose: The PMI PMBOK (2021) defines this document as the formal authorisation to start the project. Without it, team members do not know who has authority to make decisions.
• Verification: The document must be signed by the project sponsor. No work should begin before it is signed.

Schedule, Dependencies, and Change

9. Set the Timeline Baseline

Define the start date, end date, and major milestones. A milestone is a significant event (e.g., prototype complete, approval received). Do not list every task; list only the checkpoints that matter.

• Purpose: A timeline baseline gives you a point of comparison when things change. The PMI PMBOK (2021) states that the baseline is the approved version of the schedule; any change must be approved through a formal change control process.
• Verification: The baseline must be agreed by the sponsor and the team at the alignment session.

10. Identify the Critical Path

The critical path is the sequence of tasks that determines the project’s minimum duration. Any delay on the critical path delays the whole project. Identify it before you start.

• Purpose: Without knowing the critical path, you cannot prioritise tasks. A delay on a non-critical task can be absorbed; a delay on the critical path cannot.
• Verification: Use a simple network diagram (tasks in sequence) to find the longest path. PMI PMBOK (2021) describes this as the critical path method.

11. Establish a Change Control Process

Things will change. Define how changes to scope, timeline, or budget will be requested, reviewed, and approved. A simple rule: any change that affects the timeline baseline or budget must be approved by the sponsor.

• Purpose: Without a change control process, scope creep happens informally and is never documented. The PMI PMBOK (2021) requires a change control board or equivalent for any project.
• Verification: Write the process in the formal authorisation document or a separate change management plan.

Hold the Alignment Session

12. Hold the Alignment Session

This session is where you align the team on the goal, scope, roles, risks, and communication plan. It is not a status update. It is the moment everyone agrees on the plan.

• Purpose: The PMI PMBOK (2021) recommends an alignment session to build team cohesion and ensure shared understanding. Without it, team members start work with different assumptions.
• Verification: Send the agenda and the formal authorisation document to all attendees at least 48 hours before the session.

Every item in this checklist names the specific official standard (PMI PMBOK or ISO 31000) that requires it, turning a generic kickoff agenda into an auditable project-control record.