Engagement Kickoff

A first-fortnight system for consulting engagements: scope confirmed in writing, the client team mapped, governance agreed, data and interviews requested early and a day-by-day first week.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Engagement Kickoff, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

📋 Management Consulting

Engagement Kickoff

Starting a consulting engagement well: confirming scope, the client team, governance, data requests, the interview schedule and a first-week plan.

  1. Line-by-line read of the signed statement of work
  2. One-page scope confirmation note for the sponsor
  3. Client stakeholder map with influence and stance
  4. Pre-kickoff conversation with the client sponsor
  5. Governance and decision rights for the engagement
  6. First data request sent in week one
  7. Interview schedule for the first three weeks
  8. Day-by-day plan for the first week on site
  9. Site access, systems and onboarding logistics
  10. Kickoff deck with objectives, approach and timeline
  11. Kickoff readiness checklist for every new engagement
  12. RAID log opened on day one
  13. Weekly sponsor status note during the first month
  14. Daily team huddle through the launch weeks
  15. Data request tracker with twice-weekly chasing
  16. Interview logistics confirmed a week ahead
  17. Lessons log from every kickoff you run
  18. Personal kickoff template pack
  19. Sixty-day look-ahead of engagement starts
  20. Decision and action log from the first meetings
  21. Scoping questions that expose the real problem
  22. Pre-kickoff client briefing pack
  23. Writing a one-page engagement charter
  24. Running the kickoff session in the room
  25. Scope boundary language for early requests
  26. Client glossary of terms and acronyms
  27. Information handling rules agreed at kickoff
  28. Choosing the on-site and remote rhythm
  29. Collaboration tools and shared folder set-up
  30. Scope change protocol agreed at the start
  31. Engagement success measures agreed with the sponsor
  32. Two-week kickoff retrospective
  33. Pre-mortem on the engagement in week one
  34. Consulting team roles and working norms
  35. Formal kickoff meeting with client leadership
  36. Internal team launch the day before kickoff
  37. Week-one site visit and floor walk
  38. End of week one sponsor check-in
  39. First working team session with client counterparts
  40. Solo kickoff as an independent consultant
  41. Kickoff as a subcontractor on a larger firm's engagement
  42. Joining an engagement already under way
  43. First engagement start as a new analyst
  44. First kickoff as a newly promoted manager
  45. Remote kickoff with a distributed client team
  46. Inception report for a terms of reference engagement
  47. Multi-workstream kickoff across business units
  48. Reset of an engagement that started badly
  49. Kickoff alongside other advisers already on site
  50. Confidential kickoff for a sensitive project

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Line-by-line read of the signed statement of work

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most scope disputes three weeks in trace back to a sentence in the engagement letter that nobody on the delivery team read closely.

First tasks

  • Save the signed statement of work and proposal into the engagement folder
  • List each deliverable with its due date and acceptance condition
  • Highlight every exclusion and every obligation that sits with the client
  • Ask the selling partner what was promised verbally but not written down

One-page scope confirmation note for the sponsor

A sponsor who signed a contract eight weeks ago may now remember a different project. A one-page note restating the objective, the questions the work will answer, what is in and out of scope and the key dates, agreed by email in week one, gives both sides the same reference when someone later asks for more.

First tasks

  • Draft the objective and three to five key questions in plain words
  • Write two short lists, in scope and out of scope
  • Get your partner to review the note before it is sent
  • Send the note to the sponsor and ask for agreement or edits by email

Client stakeholder map with influence and stance

Engagements stall when the team discovers in week five that the finance director was never consulted and quietly opposes the work. Mapping every client stakeholder at the start, with their role, influence, likely stance and who on your team owns the relationship, turns surprises into a plan for who to meet first.

First tasks

  • Ask the sponsor for the client organisation chart and attendee lists
  • Rate each stakeholder for influence and likely stance
  • Assign a consulting team owner to every high influence stakeholder
  • Refresh the stakeholder map with anything learned this month @recurring(monthly:27)

Make it yours.

Install Engagement Kickoff, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.