Implementation Support Phases

Stay on after the recommendation and help the client make it real: pilots with clear go or no-go criteria, change support, benefits tracked against a locked baseline and a handover the client owns.

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

Then open the Marketplace in the app, search for Implementation Support Phases, 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

Implementation Support Phases

Staying on to help a client implement: pilot design, change support, tracking benefits and planning the handover so the client owns the results.

  1. Implementation phase scope and exit criteria
  2. Recommendation to implementation plan translation
  3. Named client owners for every initiative
  4. Baseline measures locked before any change
  5. Benefits case agreed with client finance
  6. Implementation risk and dependency register
  7. Consultant and client role split charter
  8. Implementation team working rhythm
  9. Organisational readiness check before rollout
  10. Weekly implementation status note to the sponsor
  11. Monthly benefits tracking log
  12. Blocker escalation routine
  13. Adoption measurement for new ways of working
  14. Change champion network across sites
  15. Pilot learning review rhythm
  16. Client capability transfer tracker
  17. Consultant footprint taper plan
  18. Frontline feedback loop on the change
  19. Pilot design principles and controls
  20. Benefits realisation methods
  21. Coaching client owners instead of doing the work
  22. Reading resistance and adoption signals
  23. Standard operating procedures the client will use
  24. Train-the-trainer rollout design
  25. Pilot site selection decision
  26. Pilot scorecard and go or no-go criteria
  27. Scale-up decision after the pilot
  28. Rollout wave sequencing plan
  29. Recovery plan for a stalled initiative
  30. Re-baselining benefits after a scope change
  31. Descoping initiatives that will not land
  32. Sustainment audits after go-live
  33. Pilot launch day preparation
  34. Go-live readiness review for the first wave
  35. Thirty-day post go-live review
  36. Benefits sign-off with the client finance director
  37. Formal handover meeting to client owners
  38. Handover pack and runbook for client owners
  39. Six-month post-exit sustainability check-in
  40. First implementation role after strategy work
  41. Solo implementation support for a smaller client
  42. Embedded at the client site for months
  43. Remote implementation support across many sites
  44. Supporting implementation through a sponsor change
  45. Benefit attribution across overlapping programmes
  46. Controlled pilots with comparison groups
  47. Embedding new KPIs in the client's management reporting
  48. Coordinating system changes with technology vendors
  49. Employee representative consultation during rollout
  50. Implementation lessons debrief with the client

Where it starts.

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

Implementation phase scope and exit criteria

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Implementation phases that start without written exit criteria tend to run until the budget runs out, with the client unsure what it bought and the team unsure when to leave.

First tasks

  • List every recommendation the client approved and mark which carry into implementation
  • Write one observable done state for each initiative in scope
  • Propose a taper point and end date to the engagement partner
  • Walk the sponsor through the draft and record the agreed changes

Recommendation to implementation plan translation

A board-approved recommendation is a statement of intent, not a plan anyone can execute on Monday morning. Breaking each recommendation into initiatives, milestones, dependencies and the people affected turns the readout deck into a plan a client operations manager can open and act on.

First tasks

  • Copy each approved recommendation into a sheet with one row per initiative
  • Draft milestones and dependencies for the three largest initiatives first
  • Ask the client IT lead which system changes the plan quietly assumes
  • Review the draft with two client managers and log their changes

Named client owners for every initiative

Initiatives owned by the consulting team stop the day the team leaves. Securing a named client owner for each one, with time released by their line manager, is the single strongest predictor that the change outlasts the engagement.

First tasks

  • List initiatives that still show a consultant as the owner
  • Ask the sponsor for two candidate owners per open initiative
  • Meet each candidate to explain the role and the time it takes
  • Confirm released time with each owner's line manager in writing

Make it yours.

Install Implementation Support Phases, 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.