Sophie Bennett
A good project kick-off is not a ceremony. It is the cheapest hour you will ever spend on a project, because it removes the misunderstandings that would otherwise surface three weeks later, usually the day before a deadline. For freelancers and small teams, where there is rarely a project manager to absorb the confusion, that hour is doing real commercial work. Here is how to run one that leaves everyone with the same picture in their head.
Start With a One-Page Brief
Send an agenda 48 hours before you meet. It should fit on one page and cover five things: what the project is, who is in the room and why, what you need to decide today, the working budget or fee, and the delivery date. If you cannot fill that page, you are not ready to meet — you are ready to do a bit more thinking first.
Keep the guest list tight. Four to six people is the sweet spot for a working kick-off; beyond that, airtime gets diluted and the quiet people stop contributing. If someone only needs to know the outcome, they get the summary email, not a seat at the table. Invite the people who will make decisions and the people who will do the work — nobody else needs to be there.
Confirm the Scope Out Loud
Scope is where projects quietly go wrong. Most disagreements are not about what was included; they are about what everyone assumed was included. So say it plainly, and write it down where people can see it.
- What is in: be specific. "Five pages of design, two rounds of revisions, handover files."
- What is out: say this out loud too. "Copywriting, photography and hosting are not part of this phase."
- What happens to new requests: agree now how you will handle them — a separate quote, a change to the timeline, or a swap for something else.
A useful question to ask the room is: "What would make this project a failure in your eyes?" It sounds dramatic, but it surfaces the hidden expectations that never make it into a brief — the launch event nobody mentioned, the stakeholder who has to approve everything, the brand guidelines that are being rewritten next month.
Agree Who Decides What
Shared accountability usually means no accountability. Name one person as the decision-maker for each area, and be clear about who is doing the work, who is reviewing it and who signs it off. If you are a freelancer working with a client, this is the moment to ask two direct questions: who can approve work, and how quickly will they realistically respond? Get a name, not a department.
Also agree your day-to-day contact and your escalation route. If your contact goes quiet or the goalposts shift, you need to know who to call — and so do they. This is not about being difficult. It is about making it easy for everyone to keep things moving without tiptoeing around the awkward conversation later.
Put Dates on the Calendar, Not Just in the Deck
Work backwards from the delivery date and list the milestones that have to happen before it: brief signed off, first draft, feedback window, final approval, invoice. Give every milestone an owner and a date. If a milestone is not on someone's calendar with their name against it, assume it will not happen.
Client-side dependencies deserve special attention, because they are the ones that slip. Feedback windows, asset delivery and sign-off all need fixing now. Build in a sensible buffer — two rounds of revisions rather than unlimited ones — and diarise your review points while everyone's calendar is still open. A short standing check-in every week beats a long email chain every three days.
Decide How You Will Communicate
Different messages need different channels, and mixing them up is a reliable source of friction. Agree in the kick-off:
- Quick questions: a chat channel or messaging app, with a note that it is not for decisions.
- Decisions and anything that changes the plan: email or a shared document, so there is a record.
- Files and versions: one folder, one naming convention. Nobody hunts for "final_v3_DEFINITELY".
- Urgent matters: a phone call. Say what counts as urgent so the definition does not drift.
Also agree a response time you can both live with — one working day is realistic for most small projects — and which single place holds the source of truth. One task board, one folder, one document. Multiplied tools multiply confusion.
Close by Reading Back the Actions
Save the last ten minutes. Read back every decision and action, with the owner and the date attached, and invite corrections. If something sounds vague when you say it out loud, it will be vaguer in practice. It is much easier to fix now than in week four.
Then send a one-page summary within 24 hours: scope, roles, milestones, communication rules and the actions. That document becomes your working reference for the rest of the project. Before people leave, book the next check-in. A kick-off that ends with nothing scheduled is just a nice chat — and nice chats do not deliver projects.
