Consulting Kickoff Meeting Agenda Template
Five documents and two sheets, led by a Decision and Escalation Map naming one approver and an escalation contact for every recurring decision type.
Free download · No account needed
Decision and Escalation Map · how to read one row
Five cells, and the rule that keeps the fifth one 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.
Search this and every result already tells you to name a decision-maker. Forge's own agenda puts it plainly: who's who on both sides, and crucially who the single decision-maker or approver is. That line is right, and it answers only one question. A client engagement runs on five or six recurring decision types, a scope call, a budget call, a data grant, a resource swap, a technical call, and each one needs its own approver and its own clock.
It does not answer how long to wait before silence becomes its own decision, and the agenda that gets closest calls something else by the same name. Pitchsite's template has an escalation path line that resolves to who to contact when the primary contact is unavailable, not what happens when a live decision has gone quiet. Atlassian's DACI documentation is stricter about the approver role than any agenda template: the one person, yes one, who makes the decision. This pack applies that discipline once per decision type, not once for the whole engagement.
Marrow Creek Advisory learned this the expensive way on an earlier engagement with Alden Grove Logistics. An unmapped scope question took three days to reach the right person, four more of silence, then six more before anyone with authority answered: thirteen business days. On the warehouse consolidation review that followed, the firm mapped scope-boundary calls to a two-day response window and a one-day escalation trigger during kickoff. The next scope question resolved in three business days, because the escalation contact was already named before the question existed.
What's in the pack
Decision and Escalation Map
One row per recurring decision type, an approver named the way a stakeholder pass already names who administers what, a response window and an escalation contact, agreed before a live decision needs any of them.
Milestone Commitment
What the client side owes: an access grant of exactly the kind a system access register already tracks, an interview slot, a sign-off, each dated to the milestone it unblocks.
Kickoff Agenda
A timed run of order that walks the room through a map and a commitment sheet already drafted, sized to however many rows still need a name confirmed live.
Kickoff Deck
Slide by slide content mirroring the agenda's order, with every row of the Decision and Escalation Map on one slide so the room confirms or corrects each name.
Working Agreement
Response times, systems of record and meeting norms for both sides, kept deliberately apart from anything with a real cost attached to running slow, the kind of pattern an engagement risk register tracks by chase count once delivery starts.
Communication Plan
Who gets which update, at what cadence, through which channel, plus the standing meetings this engagement commits to, distinct from who can approve what.
Recap Note
Sent within a day, linking the map and the sheet rather than retyping them, feeding the decision log an engagement keeps once delivery starts with confirmed names instead of guesses.
How to use it
- 1
Open in River, or take it blank
Open the pack in River and send the signed SOW, or download the Word documents and CSV sheets and fill them in yourself.
- 2
Read the SOW and intake first
Names, dates and fee thresholds come from the signed scope and whatever the intake pass already found, not from a live guess in the room.
- 3
Build the map before the agenda
One row per recurring decision type, an approver, a response window and an escalation contact, agreed before a single live decision is sitting on any of them.
- 4
Confirm live, then send the recap
Walk the map and the commitment sheet in the room, correct anything wrong on the spot, then send the recap within a day and ask each approver to confirm their row.
Frequently asked questions
Is this template free?
Yes. The zip is Word documents and CSV sheets, no account and no card needed. Edit with AI is the other branch: it creates a free River account, installs this pack as a private Space, and starts building the Decision and Escalation Map from the SOW you send.
What format are the downloaded files?
The five documents come as .docx and the two sheets as .csv, opening in Word, Pages, Google Docs, Excel, Numbers and Sheets with no conversion needed. Add ?format=pdf to the download link for the documents as PDF.
How is this different from a standard kickoff agenda?
A standard agenda gives the meeting one line for roles and decision rights, usually a single named decision-maker for the whole engagement. This pack treats deciding as five or six separate jobs, one per recurring decision type, each with its own approver, response window and escalation contact, agreed before any of them is live.
How is this different from a decision rights policy?
A decision rights policy is a standing, organization-wide document tested against months of decision history and renewed on a cycle. This pack is scoped to one engagement's opening weeks: six decision types at most, agreed once in the kickoff room, and closed the moment the recap goes out.
Why does Milestone Commitment stay separate from the workplan?
Because they track different promises. The workplan and resource tracker is the consultant team's own task register against the fee. Milestone Commitment is what the client side owes: an access grant, an interview slot, a sign-off, each dated to the milestone it unblocks, so a missed client commitment never quietly reads as the consultant running late.
What happens if this space opens after a decision has already stalled?
It still builds the map, and says so plainly. Naming an escalation contact after a decision has already stalled is a different act from agreeing one in advance. The client hears it as pressure, and the name chosen tends to fit the current problem rather than the decision type going forward. That is a patch, not the reusable instrument this pack is for.
What does 'Edit with AI' actually do?
It reads the signed SOW and whatever the intake pass already found, then drafts the Decision and Escalation Map with a named approver, response window and escalation contact per decision type. Open rows stay flagged rather than filled with a guess, and the agenda and deck get written last, once the map holds real content.
Name the approver before the decision exists
Take the Word documents and CSV sheets blank, or send River the signed SOW and get the Decision and Escalation Map back before the agenda.
Edit with AI