Consulting Kickoff Meeting Agenda Template

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.