What Belongs in a Project Kickoff Meeting

Leave with a workable starting agreement

A kickoff can cover every slide and still leave the designer unsure which survey to use or who can approve a layout change. Those are the questions that will shape the first week.

Use the meeting to confirm the result the team is responsible for, the boundaries of the work, and the decisions needed to begin. A small assignment may need a short conversation. A larger project may need separate internal and client sessions, especially where staffing, cost, or commercial details require different participants.

The agenda below is an adaptable 45-minute starting point for a project team and client representative. It assumes the scope has already been agreed; unresolved scope should be identified explicitly rather than settled by accident in the meeting.

Send enough context to prepare

Share the agreed scope, a draft milestone plan, the participant list, and the decisions you need from the meeting. Ask people to flag missing inputs or unrealistic commitments before the session.

Invite the people who own the early work and the person able to resolve the decisions on the agenda. Where an approver cannot attend, establish who will take the question to them and when the answer is needed.

A 45-minute kickoff agenda

1. 0–5 minutes · Purpose and roles. Confirm what the project must accomplish, who is responsible for delivery, and who can approve decisions. Output: named contacts and decision authority.
2. 5–15 minutes · Deliverables and boundaries. Walk through what will be delivered, what counts as complete, and key exclusions. Output: confirmed scope references and questions that still need resolution.
3. 15–25 minutes · Sequence, dates, and inputs. Test the early milestones against information, reviews, and people’s availability. Output: the next milestone, required inputs, and owners for providing them.
4. 25–33 minutes · Assumptions and risks. Identify the uncertainties most likely to affect the first work. Output: checks or responses with owners and dates.
5. 33–40 minutes · Working arrangements. Agree where current files live, how changes are raised, and how urgent decisions reach the right person. Output: a simple communication and approval route.
6. 40–45 minutes · Read back the commitments. Confirm decisions, open questions, owners, and due dates. Output: an action list people can use immediately.

Name what is still unresolved

A kickoff does not have to answer everything. It does need to keep an open question from sounding like agreement. If the client has not confirmed an access location, record the decision needed and the work that depends on it.

That distinction helps the team separate assumptions from current issues. “Proceed using the eastern access as a planning assumption until Friday” is different from “The eastern access is approved.” The record should preserve the difference.

Keep the meeting moving without losing the detail

When a technical question needs a longer discussion, assign a follow-up with the right people. Record any effect on the next milestone before moving on. Otherwise, parking a topic can also park the dependency everyone needs resolved.

Use a deliverable breakdown to keep the scope discussion concrete. For new requests, agree how the team will assess and authorize scope changes. The kickoff is a useful time to establish that route, before a rushed request arrives.

Send a short record people can correct

Send the decisions and actions promptly, with links to the working documents. Include the unresolved questions and next check-in. Ask participants to flag errors; silence should not stand in for any formal approval the project requires.

A usable action reads: “Design lead to confirm revision C survey coverage with the surveyor by Wednesday. Project manager to assess any effect on Friday’s layout milestone.” That gives the next conversation a starting point. At the first check-in, open with those commitments and update the plan from what has actually happened.