Five of nine cells, and the rule that keeps the escalation contact honest
Column
What it has to name
Decision Type
One recurring type this engagement will hit, never a single decision
Approver
Exactly one named person, never a function or a team
Response Window
A number of business days, calibrated to what the decision actually gates
Escalation Trigger
Business days overdue before escalation fires, stated as a number
Escalation Contact
One person, one level up, agreed before any decision of that type is live
The escalation contact can never be the approver for that same row. An escalation with nobody above the stalled approver is not an escalation, it is the same person asked twice.
How to run a consulting kickoff meeting
A consulting kickoff meeting is the first working session after a client signs the statement of work (SOW). In 60 to 90 minutes, the client and consulting teams confirm the goals and scope, and agree who approves each kind of decision and how fast. They also settle what the client must provide by when, and how both sides will work day to day. After a good kickoff, all of it is in writing within a day.
Treat the meeting as a confirmation, not a brainstorm. Draft the decisions and commitments before anyone sits down, so the room spends its time correcting names and dates rather than inventing them.
Walk the room through what is already drafted, one row at a time. Photo: Campaign Creators on Unsplash
Start from the signed SOW
By kickoff, you have already sold the work, so don't present the proposal again. Atlassian, which makes the project software Jira, notes that a kickoff typically takes place after the statement of work has been finalized1. Reread the signed version and pull out the deliverables, dates, fee, named client roles and change process.
Note what it leaves unsaid, too. Who on the client side can approve a fee change, grant access to a system or replace an expert you were promised? The person who signed may not hold all of those powers. If you don't know who does, sketch a stakeholder analysis before the meeting.
One named decision-maker is not enough for a whole engagement. The same kinds of decision come up again and again, and each often sits with a different person. They include scope questions, fee changes, data and system access, swapping a named expert, technical direction, and dates tied to a board or regulator.
Then give each kind a clock. Set a response window in business days and an escalation trigger, the number of days overdue before you escalate. Name an escalation contact one level up who is not the approver. A data-access grant that blocks tomorrow's work might get a 1-day window; a fee change that needs the client's finance team, 3 days.
ExampleOne row of a decision and escalation mapAn illustrative example written for this guide
Decision type: a fee change, such as adding a fourth warehouse to the review.
Approver: the client's CFO. Driver on the consulting side: the engagement lead.
Response window: 3 business days. Escalation trigger: 2 days overdue. Escalation contact: the COO, by email and phone.
Read as a sentence: if the CFO hasn't answered within 3 business days, the request is overdue. Two business days later it goes to the COO, who can make the call.
A person, not a department. The approver is one named individual, never “Finance.”
Escalation goes up. The escalation contact is never the approver on the same row.
Agree it before anything stalls
Naming an escalation contact after a decision has stalled reads as pressure, and the name gets picked to fix that one problem. Agreed at kickoff, it is simply how the engagement runs.
For tasks, a RACI matrix does a related job, recording who does the work and who answers for the result. The decision map is narrower: who approves each kind of decision, and how long everyone waits.
Write down what the client owes
Much of the first month can depend on the client: system access, interview slots, an org chart, a sign-off. List each one with a named owner, a needed-by date worked back from the milestone it unblocks, and how it was confirmed. A promise made out loud in the room is not the same as one confirmed by email.
Keep this list separate from your team's workplan, so a missed client commitment can't be mistaken for your team running late. If a commitment depends on a decision nobody has made yet, name that decision in the notes instead of guessing a date.
Agree how you'll work together
Put the routine norms in a short working agreement. Cover how fast each side answers ordinary messages, how long draft reviews take, which tool holds decisions and formal requests, and how many review rounds a deliverable gets. Write response times for both sides, so the client's reviews and replies have a deadline too.
Leave approvals out of it. A slow reply to a status email and a stalled scope call are different problems, and the decision map handles the second. Who gets which update, how often and through which channel belongs in a communication plan.
Send the recap within a day
Send a short recap the same day or the next business day, while everyone remembers the same meeting. Link the decision map and the commitment list instead of retyping them, so there is only one version to check.
In the body, restate the goals as confirmed, list any row corrected in the room, and name the three commitments due soonest, with owners and dates. Finish by asking each approver to reply confirming their row within 2 business days. An approver who won't confirm now is telling you something before the first real decision reaches them.
Before you send the recap
Each decision type has one named approver, not a team
Each response window is a number of business days
No escalation contact is also the approver on that row
Each client commitment has an owner, a date and the milestone it unblocks
Every correction made in the room is listed
Each approver has a date to confirm their row by
The agenda, deck, both sheets, working agreement, communication plan and recap note are all in the template at the top of this page. Open it with Edit with AI and send your signed SOW, and River drafts the decision map first, leaving open any name it can't confirm. Once the work starts, use the weekly status report template to keep the client updated.
How to use this template
Use the files as they are, or open them in River with Edit with AI. River asks for the signed SOW or proposal and anything your intake work found, such as a stakeholder list. It builds the decision and escalation map first, then the client's commitments, the working agreement and the communication plan, and writes the agenda and deck last.
It won't invent a name, title, fee limit or date. Anything it can't find in your files stays open and is listed for you to confirm before the meeting.
1
Download it or open it in River
Download the five Word documents and two CSV sheets free, or open the whole template in River to work on it with AI.
2
Share the SOW and notes
Send the signed SOW or proposal and any stakeholder list. River drafts the decision map first and leaves unknown names open.
3
Confirm it in the room
Walk the map and the client's commitments row by row, correcting any name or date on the spot.
4
Send the recap
Have River draft the recap note, then send it with both sheets linked and ask each approver to confirm their row.
What's in the template
The two sheets, filled for one engagement's kickoffThe Decision and Escalation Map and the Milestone Commitment sheet.
Consulting Kickoff Meeting Agenda Template
Decision and Escalation Map
Arial10
A1fx
Marrow Creek Advisory for Alden Grove Logistics · warehouse consolidation review
Six decision types, six clocks, agreed before kickoff ended
Decision Type
Client Approver
Window
Trigger
Escalation Contact
Scope boundary interpretation
Derek Fenwick, VP Operations
2 days
1 day
Renata Kowalski, COO
Budget or fee change
Owen Baptiste, CFO
3 days
2 days
Renata Kowalski, COO
Data or system access grant
Priya Nandakumar, IT Director
1 day
1 day
Derek Fenwick, VP Operations
Named resource or SME swap
Marisol Toledo, VP People
2 days
2 days
Derek Fenwick, VP Operations
Technical or design-direction call
Derek Fenwick, VP Operations
2 days
1 day
Renata Kowalski, COO
Timeline shift vs. board date
Renata Kowalski, COO
1 day
0 days
Grant Ashby, CEO
The escalation contact is never that row's own approver. Renata is the escalation contact on three of six rows and the approver on the one row with a board date behind it, which escalates to Grant instead.
Milestone Commitment
Arial10
A1fx
Milestone Commitment · what Alden Grove Logistics owes, not what Marrow Creek owes them
Six commitments, three already closed the week after kickoff
Commitment
Client Owner
Needed By
Status
Grant pick-and-pack export access (WMS)
Priya Nandakumar
16 Sep
On track
Confirm interview list and availability, round one
Marisol Toledo
18 Sep
At risk
Nominate the budget-change approver if not the CFO
Renata Kowalski
9 Sep
Closed
Provide the depot network org chart and headcount
Marisol Toledo
17 Sep
On track
Confirm the board date the review has to hit
Renata Kowalski
9 Sep
Closed
Name the single point of contact for the systems workstream
Derek Fenwick
15 Sep
Closed
Availability confirmed for four of six named interviewees so far, which is why round one reads at risk before its own date has even passed.
Kickoff AgendaA timed run of eight segments, from goals and scope to decision rights, client commitments, risks and next steps.
Kickoff DeckThe words for each slide, in the agenda's order, with the full decision map on one slide.
Working AgreementResponse times for both sides, systems of record, meeting norms and the number of review rounds per deliverable.
Communication PlanWho gets which update, how often and through which channel, plus the standing meetings and who attends them.
Recap NoteThe follow-up email: goals as confirmed, corrections made live, commitments due first, and a request that approvers confirm their rows.
Decision and Escalation Map sheetOne row per decision type, naming the approver, response window, escalation trigger and contact, and whether the approver confirmed.
Milestone Commitment sheetWhat the client owes, such as access, interviews and sign-offs, each with an owner, a date and what it unlocks.
Common questions
What should a consulting kickoff meeting agenda include?
A consulting kickoff agenda should cover eight timed items: welcome and roles, goals, scope, decision rights, client commitments, working norms, risks and next steps. Each item should end with something written down, such as a named approver or a dated client commitment. Draft the decisions and commitments beforehand and the whole agenda fits into 60 to 90 minutes.
How long should a client kickoff meeting be?
Plan 60 to 90 minutes for most consulting engagements. Give the longest single slot, about 20 minutes, to confirming who approves each type of decision. If several approvers are still unnamed, hold a short follow-up with the people concerned instead of letting the kickoff run long.
Who should attend a consulting kickoff meeting?
The client sponsor, the day-to-day contact and anyone who will approve a type of decision, such as the budget owner or whoever grants system access. From the consulting side, bring the engagement lead and the workstream leads. People needed for a single segment can join for that part only.
How is a decision map different from a RACI chart?
A RACI chart assigns roles on tasks: who does the work, who is accountable, who is consulted and who is kept informed. A decision map answers a narrower question. For each recurring type of decision, it names the one approver, how many business days they have to answer, and who can decide if they don't.
What should you send after a kickoff meeting?
Send a recap within 1 business day. It should link the decision map and commitment list rather than retype them, note any correction made in the room, and name the three commitments due soonest. Close by asking each approver to confirm their row in writing by a set date.
Is this kickoff meeting template free?
Yes. The five Word documents and two CSV sheets download free, with no account needed. Both sheets open with a made-up engagement already filled in, so you can see how a finished row reads before you clear it. Edit with AI opens the same files in a free River workspace.
What does Edit with AI do?
It opens the template in a free River workspace and asks for your signed SOW or proposal, plus any stakeholder list or intake notes. River fills in the decision map before anything else, then the client's commitments and working documents, and the agenda and deck last. Without an SOW, it asks about each type of decision in turn. Unknown names stay open.
Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.