Project kickoff meeting agenda template
On this page
What must a kickoff meeting agenda settle before work starts?
A kickoff meeting agenda should settle what the team is starting, who can make decisions and which action happens next. Put unresolved scope questions in a visible decision list, especially when a project deadline depends on an input that nobody has agreed to provide yet.
Name the missing owner. "The client will send content" is weaker than "[Content owner] will provide [Approved material] by [Date]", and the difference becomes obvious when delivery pauses.
We recommend separating decisions from background. Send the brief for reading, then use the appointment to confirm exclusions, approval responsibilities and the first dependency. A kickoff isn't proof that everyone agreed to something they haven't seen.
The suggested minutes below are planning examples. They total the advertised duration, but you can shorten introductions when participants already know each other and put that time into the decision that blocks the start.
Which project kickoff meeting agenda template matches the job?
Use the client template to agree the delivery relationship, the internal template to assign execution work, or the reset template when the original plan no longer describes the project. Copy one version, replace its brackets and remove questions already settled in an approved document.
Make the distinction explicit. A client meeting shouldn't spend its first half on internal task allocation, and an internal meeting can't grant approvals that only the client can give.
Client kickoff: 45 minutes for the delivery agreement
Project kickoff: [Project name]
Read beforehand: [Approved brief or statement of work]
Outcome: Agree how the first phase will start.
0 to 5 min: Confirm the intended result and introductions.
5 to 15 min: Review included scope and explicit exclusions.
15 to 25 min: Confirm milestones, dependencies and approval owners.
25 to 35 min: Agree communication and change requests.
35 to 42 min: Resolve start-blocking questions.
42 to 45 min: Read back actions and due dates.
First action: [Action] / [Owner] / [Date].
Unresolved approval: [Question] / [Decision-maker] / [Date].Send this once the commercial basis is clear. If a participant raises new scope, record the request and approval path instead of treating a friendly conversation as an instruction to begin unpaid additional work.
Internal kickoff: 30 minutes for the first delivery phase
Internal kickoff: [Project / phase]
Shared brief: [Link]
Required decision: [What must be settled today]
0 to 4 min: Confirm the outcome and constraints.
4 to 12 min: Assign first deliverables and review owners.
12 to 20 min: Check dependencies, access and delivery risks.
20 to 26 min: Agree hand-offs and escalation contact.
26 to 30 min: Confirm the next checkpoint and actions.
Action record: [Deliverable], [Owner], [Due date].
Blocked item: [Dependency], requested from [Name] by [Date].Choose this after the client-facing agreement has established what the project includes. Bring the people responsible for the first hand-offs; a long attendance list doesn't establish who will approve the first deliverable.
Project reset: 30 minutes after a change
Project reset: [Project name]
Reason: [Change since the previous plan]
Previous plan: [Link / version]
0 to 5 min: Describe the change and confirmed facts.
5 to 13 min: Review the effect on scope and dates.
13 to 22 min: Compare options and record the approved choice.
22 to 27 min: Assign changed responsibilities and communications.
27 to 30 min: Confirm the replacement plan's owner and issue date.
Work that pauses: [Items].
Approval still needed: [Decision], [Person], [Deadline].Use this after a changed dependency, scope decision or delivery constraint. Keep the old plan available for reference, but give the replacement a clear version so people don't continue following two different sets of dates.
What should the kickoff invitation ask people to prepare?
Ask attendees to read the approved brief and bring answers to the decisions they own. Name the document, its access requirements and the question you'll need answered; "come prepared" doesn't tell someone what to do before a project kickoff.
Keep preparation bounded. Someone who must approve a milestone needs different context from someone attending to confirm an access requirement.
The booking-question bank can help gather a project reference before a one-to-one planning call. Don't ask every participant to rewrite the whole project brief on a booking form.
For example, a 45-minute client kickoff allocates 10 minutes to scope and 10 to milestones. If the client hasn't read either section, reading both aloud can consume the time intended for approval questions. Send the documents early enough for the real reading time, and check permissions before sending the invitation.
Can one kickoff link check every project attendee's calendar?
Barq Meet checks the named host's selected Google calendars, not a collective set of project participants' availability. Confirm the other required attendees' availability through your calendar process before using a personal link to arrange a kickoff.
Check required attendees yourself. We let hosts choose which Google calendars count as busy. We also support extra guests, but adding guests doesn't create collective scheduling or prove that a client approver can attend the chosen time.
Use the booking page controls for the final host-and-client appointment once you've agreed who needs to be there. For a large internal group, arrange the meeting through the process you already use to reconcile the full attendee list.
A booking link shortens the invitation's time negotiation: "Choose a 45-minute kickoff here: [Booking link]." It leaves the agenda, documents and attendance responsibilities in the email, where the recipient can see them before choosing.
How should I share the kickoff agenda and decisions?
Put the agenda in the invitation body or link to a shared document, then record decisions in that document during the meeting. Give actions an owner and date, and distinguish an approved decision from a question that still needs someone else's authority.
One list is enough. Avoid keeping different action records in a calendar description, a chat thread and a project board without naming which record the team should follow.
For booking-triggered messages in Barq Meet:
- Match the event duration to the selected agenda.
- Open "Notifications" and edit the confirmation with an agenda or preparation-document link.
- Book a test appointment and check both the message and document access.
We send the confirmation through the platform with the host as Reply-To. You still send the project decision record yourself; a booked appointment isn't a project approval.
Use the invite-body examples to keep joining instructions beside the purpose. Check the included scheduling controls, then offer a client kickoff time.
Frequently asked questions
Does the kickoff replace a signed statement of work?
No. Use the kickoff to confirm how agreed work will begin and record questions that still need approval. When scope or commercial terms change, take that change through your normal agreement process before treating it as authorised work. Use the kickoff to clarify the work already agreed and identify unresolved decisions, with any new commercial commitment handled through the project's normal approval process instead of implied by attendance at the meeting.
Who should send the kickoff notes afterwards?
Assign a note owner before the meeting ends. That person should send decisions, actions and unresolved questions to the agreed participants, with a correction deadline, so responsibility doesn't disappear into an assumption that someone else wrote it down. Assign the owner before the session ends and include the agreed actions and decision dates, so everybody knows which written record to use instead of circulating conflicting versions after the call.
Should we postpone if a decision-maker cannot attend?
Postpone when the missing person must approve a decision required to start work. Otherwise narrow the agenda to preparation, name what remains provisional and arrange an explicit approval step instead of allowing attendance to imply consent. Identify which decisions require that person's authority and decide whether to narrow the session, obtain a written answer or move the appointment, instead of proceeding as though their approval had been supplied.
Related pages
- Booking form question examples by profession
Copy 5 booking question sets by profession. Start with 2 or 3 prompts that change preparation, and keep passwords and sensitive records off the form.
- Calendar invite description template
Copy 4 calendar invite descriptions with an agenda, joining details and preparation. Keep private notes out and distinguish booking from joining.
- Booking pages that ask the questions you need answered
Give guests a booking page with duration choices, custom questions and your branding. Start with a 30-minute event; guests don't need an account.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link