name: stakeholder-alignment-check-runner description: > Executes the full Stakeholder Alignment Check SOP — updating the stakeholder map with observed dynamics, building a structured progress update, and documenting alignment status with flagged risks. Run after the first 3 sessions with a new client. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Stakeholder Alignment Check" category: "Client Onboarding" frequency: "Trigger-Based" estimated-time: "30 min" trigger: "After first 3 sessions with a new client"

Stakeholder Alignment Check — Runner

You are executing the Stakeholder Alignment Check SOP for an independent consultant. Three sessions in, the client's stakeholders have had time to form opinions about the engagement — and those opinions may not have surfaced in the room. This procedure forces a deliberate alignment check before misalignment compounds into a scope conversation or a renewal problem.

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

What you'll have when this is done: An updated stakeholder map, a delivered progress update, and documented alignment status — with any identified risks flagged and an action plan in your project system, a documented list of each stakeholder's success criteria, and a written summary of any misalignments flagged for resolution before the next session.

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.

Original engagement context:

• Client name and engagement scope (1-2 sentences)
• Original stakeholder map from Engagement Kickoff Prep (names, roles, categories, stances)
• Engagement goals as defined at kickoff

Session history (sessions 1-3):

• Session notes from all three sessions (summaries acceptable)
• Action items assigned — which were completed, which were not
• Decisions made in sessions — and any decisions deferred
• Questions raised but left unanswered

Stakeholder observations:

• For each known stakeholder: any shift in engagement level, tone, or involvement since kickoff
• New names that surfaced during sessions 1-3 (even casually mentioned)
• Stakeholders from the original map who have been absent from all three sessions
• Any direct or indirect feedback received about the engagement
• Any observed dynamics between stakeholders (alliances, tensions, surprises)

Quick-win status:

• Quick wins identified during kickoff
• Which quick wins have been completed or are in progress
• Any quick wins that stalled and why

Engagement milestones:

• Original engagement timeline and milestones
• Current status of each milestone (on track, ahead, behind)
• Any blockers or risks to upcoming milestones
• Client dependencies outstanding (data, access, decisions)

Step 2: Review Session Notes for Misalignment Signals

Before updating anything, review the session notes from all three sessions. Produce a misalignment signal inventory:

Patterns to flag:

• Questions raised but left unanswered across sessions
• Decisions deferred more than once
• Action items assigned to the client that were not completed
• Shifts in tone or engagement level from any stakeholder
• Topics that were redirected or shut down
• New priorities introduced that weren't in the original scope
• Stakeholders referenced who haven't been in the room

For each signal, note:

• What happened — the specific observation
• Which session — when it occurred
• Who was involved — the stakeholder(s)
• Possible interpretation — what it might mean for alignment (mark as [INFERRED — verify] if not confirmed)

Rule: Don't over-interpret. A single missed action item isn't a crisis. Look for patterns — the same type of signal appearing more than once, or signals clustering around a specific stakeholder.

Step 3: Update the Stakeholder Map (Stakeholder Map Builder — Condensed)

Run the stakeholder map again with updated information from three sessions of observation. Compare to the original.

3a. Updated Stakeholder Overview Table

Categories:

• Decision Maker — Formal authority to approve, fund, or kill. Look for: budget control, signing authority, "needs to be on board."
• Influencer — Shapes decisions without formal authority. Look for: tenure, trusted advisor status, domain expertise.
• Blocker — Can stall or derail through action or inaction. Look for: controls a resource you need, burned by consultants before, not consulted about hiring you.
• Champion — Actively wants the engagement to succeed. Look for: the person who brought you in, someone whose pain you're solving directly.

One person can occupy multiple categories. Flag these — a Decision Maker who is also a Blocker is your highest-priority stakeholder.

3b. Stakeholder Shift Analysis

For each stakeholder whose stance or engagement level has changed:

• Who: Name and role
• What shifted: From [original stance] to [current stance]
• Evidence: Specific observations from sessions (not assumptions)
• Impact: How this shift affects the engagement
• Recommended action: What to do about it

3c. New Stakeholders

For any names that surfaced during sessions 1-3:

• Name, title, how they were mentioned
• Category and stance (if enough evidence; otherwise "Unknown — needs discovery")
• Why they matter to the engagement
• Recommended engagement approach

3d. Absent Stakeholders

For anyone on the original map who hasn't appeared in any of the three sessions:

• Name and original role/category
• Why their absence matters (or doesn't)
• Whether a direct check-in is needed
• Recommended action

3e. Updated Influence Map

For each stakeholder, document:

• Who they report to (formal) and who they listen to (informal)
• Current stance with evidence from sessions
• Relationships between stakeholders: alliances, tensions, dependencies
• Any shifts in informal power since kickoff

Format: Prose with bold stakeholder names.

3f. Top 3 Stakeholder Risks

Each risk needs:

• The stakeholder(s) involved
• The specific scenario — what goes wrong
• The signal you'd see before it happens
• The mitigation — what you do now

Common patterns: a Decision Maker who hasn't been in the room, a Blocker who controls access you need, a Champion losing organizational authority, an Influencer whose goals conflict with engagement scope.

3g. Updated Engagement Strategy

For each high-priority stakeholder:

• Communication cadence — how often and through what channel
• Key message — the one thing this person needs to hear to stay aligned
• Engagement timing — what to do in the next 1-2 sessions
• Risk if skipped — what happens if you don't engage proactively

3h. Gaps

List what you still don't know and what conversations would fill those gaps. This section is mandatory — there are always gaps after only three sessions.

Stakeholder map rules:

• Every classification must be supported by specific evidence from the inputs — not assumptions.
• If inputs don't give enough information, classify as "Unknown — needs discovery."
• Never invent stakeholders. Only map people explicitly mentioned.
• Always flag when the map is based on limited information. State how many sessions it draws from.
• Label the map with the date and note it should be updated after every significant interaction.

Step 4: Build the Progress Update (Progress Update Builder — Condensed)

Using the engagement goals, completed quick wins, and current status, produce a structured progress update for the primary client contact.

4a. Progress Snapshot

For each milestone or quick win completed:

• What was delivered — name it specifically
• When — date or session number
• Status relative to plan — on time, ahead, or behind (and by how much)

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

4b. 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")

4c. Blockers and Risks

For each blocker:

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

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

4d. Overall Engagement Health

One sentence using 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 delay/scope 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 what the client will quote when their boss asks how the engagement is going. Make it accurate and quotable.

4e. Email Assembly

Write the full progress update email:

Subject: Progress Update: [Engagement Name] — [Date]

1. Opening: Overall engagement health (one sentence from 4d)
2. Completed: From 4a
3. Coming Up: From 4b
4. Blockers: From 4c (omit heading if none)
5. Closing: "Happy to discuss any of this in our next session or sooner if needed."

Progress update rules:

• Never open with "Just wanted to give you a quick update." Open with the status.
• Keep the email under 300 words.
• Always include the overall engagement health sentence.
• Name blockers directly. Don't soften "we're waiting on your data" into "we're looking forward to receiving the data when it's available."
• Never list internal process tasks as completed milestones. "Held planning session" is not a milestone. "Completed the process audit" is.
• Use the client's language for milestones. Reference the SOW or engagement plan wording, not your internal shorthand.

Step 5: Document Stakeholder Success Criteria

For each stakeholder on the updated map, document:

• Name and role
• Their definition of success for this engagement (what outcome matters to them personally)
• Evidence basis — stated directly, inferred from behavior, or unknown
• Alignment with engagement scope — aligned, partially aligned, or misaligned

If a stakeholder's success criteria are unknown, flag it explicitly and recommend a specific conversation to discover them.

Step 6: Document Alignment Status and Flag Risks

Based on the updated stakeholder map, the progress update, and the success criteria:

6a. Alignment Summary

For each stakeholder:

• Name
• Alignment status: Confirmed aligned / Possible misalignment / Confirmed misalignment / Unknown
• Evidence: What supports this assessment
• Action needed: None / Monitor / Direct conversation / Escalate

6b. Misalignment Detail

For each identified misalignment:

• Who — the stakeholder(s)
• What's misaligned — expectations, scope, timeline, success criteria, engagement level
• Severity — low (minor gap), medium (needs attention before it grows), high (threatens engagement)
• Resolution plan — specific actions, owner, and timeline
• What happens if unresolved — the downstream risk

6c. Mid-Engagement Risk Assessment

If stakeholder dynamics suggest mid-engagement risk, flag it clearly:

• Risk description
• Stakeholders involved
• Recommended action — including whether to queue the Mid-Engagement Review SOP

Step 7: Assemble Final Output

Present one unified document containing:

A. Misalignment Signal Inventory

The pattern review from Step 2 — signals from all three sessions with interpretations.

B. Updated Stakeholder Map

The complete updated map from Step 3 (overview table with shift analysis, new stakeholders, absent stakeholders, influence map, top 3 risks, engagement strategies, gaps).

C. Progress Update Email

The client-facing email from Step 4 — ready to send.

D. Stakeholder Success Criteria

The documented success criteria from Step 5 for each stakeholder.

E. Alignment Status Report

The alignment summary and misalignment detail from Step 6 — including risk assessment.

F. Action Plan

G. SOPs to Trigger

• [ ] Mid-Engagement Review — trigger if stakeholder dynamics suggest mid-engagement risk
• [ ] Stakeholder Map Update — schedule next refresh after sessions 6-7
• [ ] Scope Change Protocol — trigger if misalignment requires scope or expectation adjustment

Quality Check

Rules

1. Run the alignment check with decision-makers, not just the day-to-day contact. The person in the room isn't always the one who controls renewal. Map and check in with the people who hold budget and sign-off authority.
2. The progress update is not optional. It's a written record of what you've delivered. If scope expands or a stakeholder changes their mind later, this document is your baseline.
3. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
4. Compare the updated map to the original. The value is in the shift analysis — what changed and why. A map without comparison to the kickoff version misses the point.
5. Don't over-interpret single signals. One missed action item isn't a crisis. Look for patterns — the same type of signal appearing more than once or clustering around a specific stakeholder.
6. Document success criteria even when they seem obvious. "Everyone wants the project to succeed" is not a success criterion. Each stakeholder has a specific outcome that matters to them — name it.
7. Flag absent stakeholders explicitly. Someone on the original map who hasn't appeared in three sessions is either peripheral (fine) or disengaging (problem). Determine which and act accordingly.
8. Name misalignments directly. Don't soften "the VP hasn't attended a single session" into "we're still working on full stakeholder participation." State the gap and the risk.
9. Every misalignment needs a resolution plan with an owner and a timeline. Identifying the problem without assigning the fix is just documentation theater.
10. Queue the Mid-Engagement Review SOP if any high-severity misalignment is identified. Don't wait for it to resolve on its own.
11. Escape dollar signs as \$ for Notion compatibility.
12. Flag inferred details. If a stakeholder's stance or alignment status was inferred rather than stated, mark it [INFERRED — 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.