name: mid-engagement-review-runner description: > Executes the full Mid-Engagement Review SOP — from building a structured progress summary through profitability analysis to assembling a one-page client review document with quick wins and scope flags. Run at the midpoint of any engagement. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Mid-Engagement Review" category: "Client Delivery & Prep" frequency: "Trigger-Based" estimated-time: "60 min" trigger: "At the midpoint of any engagement"

Mid-Engagement Review — Runner

You are executing the Mid-Engagement Review SOP for an independent consultant. The midpoint of an engagement is where drift becomes undeniable — scope has crept, the original problem has evolved, or the client's priorities have shifted. This process resets alignment, identifies what's working, and gives you the data to have a confident conversation about the engagement's second half.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done: A documented progress summary, a profitability read, a second-half plan with quick wins prioritized, and a completed mid-engagement review document ready to run the client conversation. Any scope or contract issues are surfaced and addressed — not carried silently to the close.

Step 1: Collect All Inputs

Gather the following from the user in a single prompt. Accept whatever detail level they provide. Flag gaps but keep moving.

Engagement identity:

• Client name
• Engagement type (retainer, project, sprint, advisory)
• Engagement start date and expected end date (to confirm midpoint)
• Original SOW scope summary (1-3 sentences — what you were hired to do)

Progress data:

• Session recaps or summary of sessions completed (dates, topics, outcomes)
• Completed deliverables (list each with delivery date)
• Open action items (yours and the client's)
• Any milestones from the original plan and their current status (complete, in progress, not started, blocked)

Scope and change history:

• Any formal change orders signed since engagement start
• Any informal scope additions — work that happened outside the contract but inside your time budget
• Client requests or priorities that have shifted since kickoff

Financial data (for profitability analysis):

• Engagement fee structure (fixed, retainer, hourly) and total fee or monthly fee
• Contracted or estimated hours for the engagement
• Actual hours logged to date (include meetings, email, prep, admin, revision cycles)
• Estimated hours remaining to complete the engagement
• Your target hourly rate
• Fees collected to date

Second-half context:

• Remaining deliverables or milestones on the original plan
• Any new priorities the client has surfaced since kickoff
• Known blockers or risks for the second half
• Is this a retainer engagement where renewal discussion is relevant?

Review session details:

• Date of the scheduled mid-engagement review session with the client
• Format (in-person or virtual)
• Attendees

Step 2: Build Progress Summary (Progress Update Builder — Condensed)

Using the engagement history, session recaps, completed deliverables, and open action items, produce a structured progress summary.

2a. Progress Snapshot

Map each completed milestone to the engagement timeline:

• What was delivered — name it specifically (not "continued work on the project")
• When — date or time period
• Status relative to plan — on time, ahead, or behind (and by how much)

Lead with the most significant accomplishment. If behind schedule, state the reason and the impact on downstream milestones. Don't hedge.

Format: 3-5 bullet points or short paragraph.

2b. Upcoming Milestones

List the next 2-4 milestones in chronological order:

• What's being delivered — specific deliverable or outcome
• Target timing — date range or session number
• Client dependencies — anything you need from them (be specific: "the Q1 revenue data," not "some information")

Format: Numbered list. Bold the milestone name.

2c. Blockers and Risks

If blockers exist, state each one:

• What's blocked — the specific work item
• Why — root cause
• Impact — what happens if unresolved
• Proposed resolution — what you recommend

If no blockers: "No blockers at this time. All workstreams are progressing as planned."

2d. Overall Engagement Health

One sentence capturing overall status. Use one of three frames:

• On track: "The engagement is on track. We're [at/ahead of/slightly behind] the timeline with [X] of [Y] milestones complete."
• At risk: "The engagement is at risk of [specific issue] due to [specific cause]. Proposed resolution: [action]."
• Needs attention: "[Specific area] needs attention before we can proceed to [next phase]. Recommended next step: [action]."

This line is the one the client will quote when their boss asks how things are going. Make it accurate and quotable.

Progress summary rules:

• Every completed item must map to an engagement milestone, not just a task you performed. "Updated the project tracker" isn't progress — "Completed the process audit" is.
• Keep it under 300 words. Progress updates that become reports don't get read.
• Use the client's language for milestones — reference the SOW wording, not your internal shorthand.
• If the same milestones keep appearing as "next" across the engagement, the engagement is stalled. Flag it.

Step 3: Compare Progress to SOW

With the progress summary in hand, compare it against the original SOW:

• Milestones on track: List items progressing as contracted
• Milestones behind: List items delayed with cause and downstream impact
• Informal scope additions: Work that happened outside the contract but inside your time budget — name each one specifically
• Scope creep assessment: If informal additions are significant, flag this as a Change Order Management conversation

Rule: Don't gloss over informal scope additions. These are the invisible hours that erode profitability. Name them so you can decide whether to formalize, push back, or absorb intentionally.

Step 4: Identify Quick Wins for the Second Half (Quick-Win Identifier — Condensed)

Using the engagement context and second-half scope, identify 2-3 high-visibility actions that can be completed before the engagement closes.

4a. Situation Scan

Review the second-half scope, open action items, and any new priorities for quick-win candidates. Tag each item:

4b. Quick-Win Filter

A qualifying quick win must pass ALL four criteria:

1. Completable before engagement close with current access and effort
2. Zero or minimal dependencies — no budget approvals, no new tools, no stakeholders you haven't met
3. Visible to the client — something they can see, touch, or feel
4. Connected to stated goals — even loosely, relates to why they hired you

Cut anything that fails any criterion.

4c. Scoring Matrix

Score surviving candidates (1-5 each):

• Visibility — how noticeable is the result? (5 = client brings it up unprompted)
• Effort — how easy to execute? (5 = you can do it this week)
• Alignment — how closely does it connect to engagement goals? (5 = directly advances main objective)

4d. Top Win Execution Plan

For the #1 ranked quick win:

• What: one sentence
• Steps: numbered list
• Timeline: session-by-session or week-by-week
• How to make it visible: the specific moment the client sees the result
• How to connect it forward: one sentence linking this win to the engagement arc or a potential next engagement

4e. Backup Win

Document the #2 ranked candidate with the same structure.

Quick-win rules:

• Never recommend more than 3 candidates. Overloading the list defeats the purpose.
• Always include a timeline. "Do it soon" is not a plan.
• The execution plan must be specific enough that you could hand it to a colleague.
• Include "how to make it visible" — a win the client doesn't see is not a win.
• Flag any quick win that could create a negative side effect.

Step 5: Analyze Engagement Profitability (Client Profitability Analyzer — Condensed)

Using time logged, fees collected, and estimated remaining hours, calculate the engagement's true profitability.

5a. Profitability Calculation

5b. Scope Creep Audit

For each identified scope creep item from Step 3:

Scope creep as % of total hours: [creep hours / total actual hours]

5c. Profitability Assessment

Assign an engagement health category:

• Healthy — effective hourly rate at or above target. Scope is clean.
• At risk — effective hourly rate within 20% below target. Some scope creep but manageable. Needs monitoring.
• Underperforming — effective hourly rate more than 20% below target. Significant scope creep or structural underpricing. Needs intervention.

5d. Recommendation

If the engagement is at risk or underperforming:

• Signal: the specific data point (e.g., "realization rate of 72% driven by scope creep consuming X hours per month")
• Do This: specific action with conversation language where applicable
• For scope conversations: "At the mid-engagement review, say: 'I want to review what we're covering against our original scope. I've noticed we've added [specific items]. I'd like to either adjust the scope or update the fee to reflect the actual workload.'"
• For pace adjustments: name what changes and the expected impact on the effective rate
• Timeline: when to act (at the review session, before the next session, etc.)

Profitability rules:

• Calculate from actual hours, not SOW hours. The gap between the two is where profitability disappears.
• Include all time: meetings, email, prep, admin, and revision cycles.
• Scope creep must be quantified in hours and revenue, not just identified.
• Never recommend disengagement as a first step. Sequence: scope conversation, then fee adjustment, then disengagement.
• Round effective hourly rates to the nearest whole dollar.
• Escape dollar signs as \$ for Notion compatibility.

Step 6: Prepare the Mid-Engagement Review Document

Assemble a one-page mid-engagement summary that will run the review session with the client. This is the deliverable you bring to the meeting.

Step 7: Assemble Final Output

Present one unified document containing all sections:

A. Engagement Summary Header

# Mid-Engagement Review: [Client Name]
**Date:** [Review session date] | **Engagement:** [Type] | **Midpoint:** [Current date relative to start/end]
**Original scope:** [1-2 sentence SOW summary]

B. Progress Summary

The progress snapshot, upcoming milestones, blockers, and overall engagement health sentence from Step 2.

C. Scope Comparison

SOW vs. actual progress table from Step 3. Informal additions listed. Scope creep flag if applicable.

D. Quick Wins for the Second Half

Scoring matrix and execution plans from Step 4 (primary and backup wins).

E. Profitability Read

Profitability calculation table, scope creep audit, health category, and recommendation from Step 5. Mark this section as internal — not for the client.

F. Client-Facing Review Document

The one-page summary from Step 6, formatted for sharing:

• Progress to date (3-5 bullets)
• Second-half plan (numbered milestones with timing)
• Quick wins identified (1-2 with brief description)
• Scope or timeline flags (if any)
• Discussion questions for the review session

G. Review Session Agenda

Adjust timing based on whether scope flags or renewal discussion are relevant. If neither applies, redistribute time to Progress Review and Second-Half Priorities.

H. SOPs to Trigger

• [ ] Change Order Management — if significant informal scope additions were identified
• [ ] Retainer Renewal Process — if this is a retainer engagement and renewal window is approaching
• [ ] Client Offboarding Process — confirm it's in the engagement timeline for the close

Quality Check

Rules

1. Run the profitability analysis even if the client relationship feels good. Client satisfaction and engagement profitability are not the same thing. Discovering at close that you worked 40% over budget is a systems failure, not bad luck.
2. Treat the mid-engagement review as a reset, not a check-in. A casual conversation at the halfway point doesn't surface scope drift or profitability problems. You need the data in front of you.
3. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
4. Name informal scope additions specifically. "Some extra work" is invisible. "Built an additional reporting template and attended three unplanned stakeholder meetings" is actionable.
5. Quick wins must be completable before engagement close. Don't recommend wins that require timeline extensions or new approvals.
6. The client-facing document runs the meeting. If you walk in without it, the review becomes a meandering conversation that misses the hard topics.
7. Surface scope and contract issues at the midpoint. Carrying them silently to the close turns a manageable conversation into a difficult one.
8. If the engagement is a retainer, use this review as the natural renewal window. Don't let the renewal conversation happen for the first time at month five.
9. Progress means milestones, not activity. "Held three sessions" is activity. "Completed the process audit and delivered the gap analysis" is progress.
10. Profitability calculations use all time. Meetings, email, prep, admin, travel, and revision cycles. If you spent time thinking about this client, that's time.
11. Round effective hourly rates to the nearest whole dollar. Precision to the cent implies accuracy that estimates don't support.
12. Escape dollar signs as \$ for Notion compatibility.
13. Flag inferred details. If a profitability number or scope assessment was estimated rather than tracked, mark it [ESTIMATED — verify].

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.