Project kickoff agenda: a 60-minute template that sets the scope

Most kickoff meetings are a round of introductions, a slide of the timeline, and a general feeling of optimism. Everyone leaves happy and nobody leaves with anything decided. Then week six arrives, and it turns out the client’s head of sales thought the project included something the scope excludes on page two.

I treat the kickoff as the most important hour in a project’s commercial life. The contract was agreed between two people. The work will involve ten. The kickoff is the one moment when all ten are in the same room, in a good mood, with nothing yet at stake. That is the cheapest possible time to say what is included, what is excluded, and what happens when someone wants more.

The agenda below is built around that idea. It is the third of the three documents described on the Scope hub, alongside the scope of work and the change request form.

Why a kickoff belongs in a discussion of scope

A scope document only protects you from people who have read it. On a typical project, the people who will generate requests (the client’s team, the late-arriving stakeholders, your own designers and developers) have never seen it. They are working from a mental picture formed by a sales deck, a hallway conversation, or the project’s name.

Unspoken expectations are the raw material of scope creep. The kickoff is where you replace them with the written version, out loud. Twenty-five of the agenda’s sixty minutes go to the deliverables, the exclusions, the assumptions, and the change process, and that share is deliberate.

Before the meeting

Get the right people

Three people on the client side matter most: the sponsor who controls the budget, the project contact who approves work day to day, and anyone who owns a system or department the project touches.

The sponsor is the one who tends to send apologies. Do not proceed without them. The sponsor is the person who will decide, two months from now, whether a change request gets approved. If they heard the exclusions and the change process themselves, that decision takes a day. If they did not, it starts with “nobody told me”. Thirty minutes of their time is enough, which is why the scope items sit in the first half of the agenda.

Send the pre-read

Three business days ahead, send the signed scope with the deliverables and exclusions marked, the timeline, a one-page summary of the change process with a blank form attached, and the list of materials and access you need.

Half the attendees will not read it. Send it anyway. It puts the exclusions and the change process in writing before the meeting, so nothing said in the room is a surprise. It also includes one request that tests the client early: confirm your project contact in writing before we meet. A client who cannot name one person with authority to approve has just shown you the biggest risk on the project.

Run an internal kickoff first

Spend 30 minutes with your own team the day before. Read them the scope, including the limits and exclusions. Most of the team was not involved in the sale and will build whatever they are asked to build unless they know where the edges are. Give them the sentence to use when a request arrives mid-project:

Good idea. I will pass it to the project lead and we will come back to you with what it involves.

Running the meeting

Introductions with decision rights

Ask each person for their name, their role on this project, and what they approve or decide. The third part is the useful one. It surfaces, in five minutes, whether the person you thought was the approver really is.

The outcome, from the sponsor

The sponsor states in their own words why the project exists and what success looks like in six months. Write the sentence down. You will use it later, when a change request comes in and the question is whether it serves the goal.

The scope, read aloud

Read the deliverables table line by line, including every limit: eight page templates, two user roles, two rounds of revisions, one integration in one direction. It feels slow. It is ten minutes that regularly saves ten thousand dollars.

Someone will interrupt with “does that include…?” Good. That question in week one costs a line in the notes. The same question in week nine costs a change order and an argument. Anything that cannot be settled in two minutes goes on the open questions list with an owner and a date.

The exclusions, and one question

Read the exclusions list. Then ask:

What did you expect to see in this project that you have not heard yet?

Then wait. The silence is uncomfortable and productive. Each answer falls into one of three groups. It was always included, and you can say so. It is excluded, and now everyone knows. Or it is a new requirement, and you raise it as the first change request that same week, at the point when the client is most receptive.

The change process, with a rehearsal

Explain how changes work using a made-up example and the actual form:

Say in week four you decide you want the site in a second language. You email me. Within two business days I send you this one-page form with the cost, the effect on the launch date, and a few options. You pick one. We start when you approve it in writing.

Then ask the sponsor directly: “Does that work for you?” A spoken yes in front of their own team is the most valuable sentence of the meeting. When the first real change arrives, you are following a process they agreed to, in public. The steps behind the form are on the change request process page.

Timeline, materials, communication

These three items are routine, with two cautions.

On the timeline, say plainly what happens to the dates when feedback is late. The scope has a clause for it. Read it.

On materials, refuse collective ownership. “The marketing team will send the content” means nobody will. Every line gets one name and one date. Late client materials are one of the most common reasons a launch date moves, and the materials table is your record when it does.

Many of these items overlap with general client setup, such as billing contacts, tool access, and reporting cadence. If you take on clients for ongoing work, a fuller client onboarding process handles those, and the kickoff can stay focused on the project.

Risks

Ask each side to name the single thing most likely to make the project late. This gets better answers than “any concerns?”. Clients will tell you about the approval committee, the legacy system nobody understands, or the trade show the launch is secretly tied to.

Recap

The note taker reads back the decisions and the actions. Tick the checklist in section 4 of the template. Anything unticked becomes an open question with an owner.

The decisions that matter most

The template lists eleven decisions. If the meeting runs short, protect these four:

A kickoff that produces these four has done its job even if everything else is handled by email.

After the meeting

Send the recap the same day. Keep it short enough to read on a phone: decisions, materials with owners and dates, open questions, next three dates. End with:

Please reply “confirmed” so we all have the same record.

That reply is evidence. Six weeks later, when someone says they were never told about the revision limit, you forward one email and the conversation ends politely.

Then do the follow-through in section 7 of the template: calendar invitations for every milestone review, the shared channel, the first invoice if it falls due at kickoff, and a change request for anything raised in the meeting that falls outside the scope.

Common mistakes

Treating it as a social call. Rapport matters, and you build more of it by running a sharp meeting than by spending 40 minutes on introductions.

Presenting slides about your process. The client bought the project already. Use the time for decisions.

Skipping the exclusions because it feels negative. Clients respect a supplier who is clear about boundaries. The awkwardness you avoid at kickoff comes back larger in the middle of the project, and the scope creep examples show what it costs.

Letting the salesperson disappear. The person who sold the work knows what was promised informally. They need to be in the room to confirm or correct it.

No written recap. A kickoff with no recap is a pleasant conversation that each attendee remembers differently.

If the scope document itself is thin, fix that before the kickoff. Reading a vague scope aloud only spreads the vagueness to more people. The short-form scope of work template gives you a version worth reading out. For larger projects, the full statement of work plays the same role.