Executes consulting project closeout: deliverable handover, knowledge transfer, lessons learned, retrospectives, financial reconciliation. For wrapping up engagements or transitions to BAU.
npx claudepluginhub anotb/management-consulting-pluginThis skill uses the workspace's default tool permissions.
Manage the full consulting engagement closeout process: ensuring deliverables are handed over, knowledge is transferred, lessons are captured, and the client is equipped to operate independently. Treat closure as a structured workstream, not an afterthought.
Guides first weeks of consulting engagements from contract to running project: kickoff workshops, discovery planning, stakeholder mapping, workstreams, cadences. For new clients or stalled resets.
Structures unstructured client data into legal matter briefs for proposals, captures agreed baselines, or reconstructs scopes mid-matter. Outputs .docx files.
Generates formal Scope of Work documents defining project objectives, deliverables, acceptance criteria, in/out scope, work breakdown structure, milestones, and change request processes.
Share bugs, ideas, or general feedback.
Manage the full consulting engagement closeout process: ensuring deliverables are handed over, knowledge is transferred, lessons are captured, and the client is equipped to operate independently. Treat closure as a structured workstream, not an afterthought.
Closeout depends on what was delivered and what remains. Confirm before proceeding:
Allocate closeout effort explicitly. Teams consistently underestimate this.
| Engagement Size | Typical Closeout Effort | Duration |
|---|---|---|
| Small (< $500K, < 6 months, < 10 people) | 3-5% of total engagement cost | 2-3 weeks |
| Medium ($500K-$2M, 6-12 months, 10-30 people) | 5-8% of total engagement cost | 4-6 weeks |
| Large ($2M+, 12+ months, 30+ people) | 8-12% of total engagement cost | 6-10 weeks |
| Multi-workstream transformation | 10-15% of total engagement cost | 8-12 weeks |
Build closeout into the project plan from the start. Backloading it into the last week guarantees it gets rushed or skipped.
Assign clear ownership before closeout begins. Ambiguity here is how things fall through cracks.
| Activity | Engagement Manager | Workstream Leads | Client Sponsor | PMO |
|---|---|---|---|---|
| Closure readiness assessment | A | R | C | I |
| Deliverable handover | A | R | C | I |
| Client acceptance sign-off | R | C | A | I |
| Knowledge transfer sessions | A | R | I | C |
| Benefits tracking handover | R | C | A | I |
| Stakeholder transition | R | R | A | I |
| Lessons learned / retrospective | A | R | C | C |
| Financial reconciliation | A | I | C | R |
| Documentation archive | I | R | I | A |
| Resource release | A | R | I | R |
R = Responsible, A = Accountable, C = Consulted, I = Informed
Before initiating closure, verify that completion criteria are actually met.
Determine which type of closure applies:
| Type | Description | Requirements |
|---|---|---|
| Successful Completion | All objectives met | Full closure process |
| Early Termination | Project cancelled | Document rationale, partial handover |
| On Hold | Suspended temporarily | Document conditions for restart |
| Rolled into BAU | Integrated into operations | Full handover, no formal end |
Walk through each criterion systematically:
If any criterion is unmet, determine whether it blocks closure or can be resolved as part of the closeout process.
Transfer all project outputs to the client with proper documentation.
For each deliverable, document:
Prepare two packages:
User Handover Package
Technical Handover Package
Formalize acceptance with a clear record. Keep it concise: the goal is an unambiguous "yes, we accept."
Project Closure: [Project Name] | Client: [Client Organization] | Date: [Date]
DELIVERABLES ACCEPTED:
1. [Deliverable] - [Status]
2. [Deliverable] - [Status]
Client confirms all deliverables received and acceptable.
Outstanding items (if any) have an agreed resolution path.
Client Representative: _________________ Date: __________
Consulting Representative: _________________ Date: __________
The goal is client independence. When the consulting team leaves, the client should be able to operate, maintain, and evolve what was built.
| Method | Best For |
|---|---|
| Live workshop | Complex processes, interactive Q&A |
| Recorded video | Procedural knowledge, repeatable tasks |
| Written documentation | Reference materials, runbooks |
| Interactive guides | Step-by-step tasks in software |
| Async Q&A | Distributed teams, follow-up questions |
For each knowledge area, define:
For each knowledge transfer session, capture:
Ensure these documents exist and are handed over:
| Document | Purpose |
|---|---|
| Run Book | Day-to-day operations procedures |
| Support Guide | Troubleshooting common issues |
| Escalation Matrix | Who to contact for what |
| Contact List | Key contacts with roles |
Define the post-project support model:
Benefits don't stop being measured when the consulting team leaves. This is where most engagements fail: the team departs, and nobody owns measurement.
For each benefit identified in the business case, document:
| Benefit | Baseline | Target | Current | Owner (Post-Departure) | Measurement Method | Frequency |
|---|---|---|---|---|---|---|
| e.g., Process cycle time | 14 days | 5 days | 7 days | VP Operations | System report #X | Monthly |
| e.g., Cost savings | $0 | $8M/yr | $3M (annualized) | CFO | P&L line item | Quarterly |
Map expected benefit realization against milestones:
Include a scheduled check-in at 3 and 6 months post-departure to review realization against plan.
Consulting teams build relationships that the client organization needs to sustain. Plan the transition explicitly.
For each key stakeholder relationship:
| Stakeholder Group | Message | Channel | Timing | Owner |
|---|---|---|---|---|
| Executive sponsor | Engagement complete, benefits summary, ongoing support model | 1:1 meeting | 2 weeks before departure | Engagement Manager |
| Steering committee | Final status, transition plan, open items | Formal presentation | 3-4 weeks before departure | Engagement Manager |
| Working team leads | KT completion, support contacts, escalation paths | Working session | 1-2 weeks before departure | Workstream Leads |
| End users | What's changing, where to get help, training resources | Email + town hall | 1 week before departure | Client Change Lead |
| IT / Operations | Support handover, system access, monitoring | Technical meeting | 2 weeks before departure | Technical Lead |
| Vendors / Partners | Contract transitions, new contact points | Formal letter + call | 3-4 weeks before departure | PMO |
Lessons learned are the most commonly skipped and most valuable part of project closure. Run a proper retrospective.
Choose a format that fits the team:
Start / Stop / Continue
4Ls (Liked, Learned, Lacked, Longed For)
Sailboat Method
Document lessons in two categories:
What Went Well
For each success factor, capture the area, what specifically worked, and the evidence (a concrete example, not a vague impression).
What Could Be Improved
For each challenge, capture what didn't work and a specific recommendation for improvement. "Communication could be better" is not useful. "Weekly status calls should include the IT lead, not just the business sponsor" is.
Translate lessons into prioritized recommendations:
Run the session with:
Reconcile all financial obligations:
| Item | Details |
|---|---|
| Total Budget | Original approved amount |
| Actual Spend | What was actually spent |
| Variance | Amount and percentage |
| Final Invoice | Amount and payment status |
| Final Expenses | Submission status |
For each team member, confirm:
For each vendor or subcontractor:
Archive all project documentation with appropriate retention periods. At minimum: project charter, governance docs, final deliverables, lessons learned, financial records, and contracts.
Acknowledge individual contributions. This is not a formality. People remember how engagements ended.
Distinct from annual performance reviews and more valuable because they capture performance in context. Conduct these before the team disbands, not weeks later when memory fades.
For each team member, assess:
| Dimension | Rating (1-5) | Evidence | Development Recommendation |
|---|---|---|---|
| Technical quality of work | _ | Specific deliverables or analyses | What to build on or improve |
| Client relationship management | _ | Interactions observed, client feedback | Growth areas |
| Team contribution | _ | Collaboration, mentoring, initiative | Next engagement fit |
| Problem-solving under pressure | _ | How they handled ambiguity, setbacks, tight deadlines | Stretch opportunities |
| Communication (written and verbal) | _ | Deliverable quality, presentation skill, stakeholder updates | Development suggestions |
Process:
Why this matters: Consulting team members are evaluated on engagement performance. If you don't do this, they either get no feedback (bad) or get feedback from someone who wasn't there (worse).
Produce a closure report that serves as the definitive record of the engagement.
Project Closure Report: [Project Name]
Executive Summary
[Overview: objectives, outcomes, key metrics, overall assessment]
1. Project Overview
- Original objectives
- Scope (included and excluded)
- Timeline by phase
2. Deliverables
- Completed deliverables with status and location
- Handover confirmation
3. Financial Summary
- Budget vs. actual (total and by category)
- Variance explanation
4. Benefits
- Benefits achieved to date (quantified)
- Expected future benefits (with measurement plan)
- Benefits tracking ownership (who measures what, post-departure)
5. Lessons Learned
- Success factors
- Improvement areas
- Specific recommendations for future engagements
6. Team Recognition
- Key contributions
7. Appendices
- Deliverable inventory
- Change log
- Final risk register
- Stakeholder list
Certain industries impose specific closeout requirements beyond standard practice. Failing to address these creates compliance risk that outlasts the engagement.
Not every engagement ends well. Client dissatisfaction, budget cuts, leadership changes, strategy pivots, or genuine delivery failures can all terminate an engagement early. How you handle the ending determines whether the client relationship (and your reputation) survives.
| Scenario | Your Priority | Key Actions |
|---|---|---|
| Client pulls budget (external pressure, not dissatisfaction) | Preserve relationship, close cleanly | Express understanding. Deliver whatever is complete in usable form. Offer to resume if funding returns. Don't fight it. |
| Client is dissatisfied with delivery quality | Damage control, relationship salvage | Acknowledge the concern without being defensive. Offer a concrete remediation plan (at reduced or no cost). Involve your leadership. |
| Leadership change kills the project | Protect team, maintain firm reputation | Document what was delivered and its value. Brief the new leadership if they'll take the meeting. Accept the decision gracefully. |
| Scope was wrong from the start | Honest reckoning | Acknowledge the misscoping. Deliver what's useful from work completed. Offer a re-scoped approach if the underlying need still exists. |
| Mutual agreement to stop | Clean handover | Treat as normal closeout but on compressed timeline. No hard feelings, but document everything. |
Regardless of cause, these actions are non-negotiable:
Rarely discussed but sometimes necessary. Situations where the firm should initiate termination:
In these cases, raise the concern with your firm's leadership, document the issue, and follow your firm's protocol for disengagement. Do it promptly and professionally.
While closing the engagement, identify potential follow-on work. This is not about selling; it's about recognizing where the client still has unresolved needs that surfaced during the engagement.
Look for:
Document these with enough context that a business development conversation can happen naturally, not as a sales pitch embedded in a closure meeting.