03 — GOLDEN EXAMPLE: Scope Discipline Kit

A fully populated scope-check document for an anonymized reference client, with annotations explaining why each section is structured as it is. This file teaches the kit by showing a finished output at quality.

The pattern depicted below is extracted from observed advisory engagements — anonymized for vault use, but the shape of triggers, the rhythm of the historical section, the specificity of the scripted responses, and the Review Log cadence are all derived from real evidence of how scope discipline plays out when a client has a chronic vendor-remediation bleed pattern. Names, dollar amounts, and dates are illustrative.

How to Read This File

This document contains two layers:

1. The scope-check doc itself (the parts inside horizontal rules and formatted as the output would appear). This is what the kit produces.
2. Annotations (in italicized indented blocks marked with ANNOTATION). These explain design decisions, what the advisor should notice, and where specific choices came from in observed practice.

When the kit generates a real scope-check doc, annotations are stripped. Only the document structure itself lands in clients/[client-name]/scope-check.md.

The Golden Example Starts Here

Acme Corp — Scope Check

Client: Acme Corp Engagement: HR / Operational Oversight Advisory (monthly, $2,500/mo) Signed SOW: clients/acme-corp/sow-2026-01-15.pdf Last scope review: 2026-04-17 Status flag: ACTIVE BLEED — ~$12,000 logged unpaid Feb–Apr 2026 on vendor remediation work

ANNOTATION — Header

The header is dense by design. Advisors scanning this doc mid-conversation need the SOW reference accessible in one glance. The "Last scope review" field is a staleness indicator — anything more than 45 days old suggests Mode 3 is overdue.

The Status Flag is optional for STABLE engagements but mandatory for ACTIVE BLEED. When the flag is ACTIVE BLEED, the doc's purpose shifts: every section is oriented toward the wind-down conversation, not general scope management. The flag tells the advisor which doc state they're in.

The engagement fee ($2,500/mo in this example) appears because it anchors the bleed calculation — $12,000 of unbilled work is nearly 5 months of monthly retainer, which is the honest structural read.

What's In Scope (Explicit)

• Monthly 90-minute advisory conversation on HR strategy and operational risk
• Written strategic recommendations when requested (vendor comparisons, transition plans, organizational risk assessments) — one per quarter included, additional at hourly rate
• Coaching the primary stakeholder on HR-related decisions when Acme asks for the advisor's view
• Pre-review of HR-related communications before they're sent to employees (drafts reviewed, not drafted)
• One annual HR strategy session (2-hour working session, scheduled in advance)

ANNOTATION — "What's In Scope (Explicit)"

Items here are verb-led and specific. "Monthly 90-minute advisory conversation" not "advisory services." "Pre-review of HR-related communications" not "communications support."

Why specificity matters: Vague scope language absorbs anything. When the client asks for something adjacent to "communications support," the advisor has no reference point to push back. "Pre-review of HR-related communications" bounds the work — the advisor reviews drafts; they don't draft them. This distinction is observed to matter in practice; the drift pattern almost always comes through ambiguous verbs.

The quarterly recommendation count is included as another bounding mechanism. Without it, "written strategic recommendations when requested" becomes infinite-on-demand writing work. The observed pattern in real engagements: scope items without explicit counts or frequencies accumulate silently.

Everything here is sourced directly from the signed SOW. If an item isn't in the SOW, it doesn't go in this section. If the SOW is vague, the scope-check doc should make the SOW more specific than the SOW itself — and the advisor should consider whether the SOW needs a language update at the next renewal.

What's Explicitly Out of Scope

Lane violations ([Firm Name] doesn't do these)

• Payroll processing or payroll data remediation. The firm is HR advisory; payroll execution belongs to the client's payroll vendor or a specialist provider.
• W-2 auditing, correction, or statutory compliance review. Compliance work belongs to a CPA or payroll provider with E&O coverage for tax filings.
• Vendor accountability management. Acme is the customer of its vendors. Vendor underperformance is Acme's vendor relationship to manage, not the advisor's.
• Tax filing research, statutory document tracking, or employee tax remediation advisory.
• Direct management of employee performance issues, terminations, or PIPs. The firm advises; execution belongs to Acme's line managers.

Lever violations (Advisor can't close these)

• Forcing vendor behavior. A third-party vendor not acting correctly is not a problem the advisor's effort can solve — the decision authority is the vendor's. Hours spent here don't convert to outcomes.
• Compelling Acme to switch vendors or take action on vendor dysfunction. The advisor can recommend; the decision is Acme's.
• Driving employees' tax return resolution. The employees, their CPAs, and the statutory authority are the closing parties. The advisor is three steps removed from the result.
• Resolving interdepartmental political conflicts at Acme. The advisor can name dynamics; the conflict resolution lives with the parties involved or their leadership.

This client's historical out-of-scope asks (pattern recognition)

• Vendor selection research prior to engagement (pre-SOW): Advisor recommended a specialist provider (Provider A); Acme chose a cheaper generalist (Provider B) against recommendation. When Provider B failed in month 2, the remediation came to the advisor anyway despite the advisor not having been involved in Provider B's selection.
• Payroll vendor remediation work (Feb–Apr current engagement year): Full 14-of-14 employee compliance audit after Provider B under-reported errors. Logged ~$12,000 unpaid. Advisor's capability made the ask feel legitimate; the structural fact that compliance work needs E&O coverage the firm doesn't carry was never surfaced.
• Vendor leadership escalation meeting (week of 2026-03-24): 8-person meeting with the vendor team and 2 senior vendor leaders, facilitated jointly by advisor and the primary client stakeholder. Advisor's presence used as the accountability lever — the lever Acme wanted the advisor to apply was vendor behavior change, which is not a lever the advisor has.
• Investigating statutory filing status (2026-04-10): Chasing down whether corrected filings were submitted to the statutory authority, to understand downstream employee impact. Pure lever violation — outcome depends entirely on statutory authority action.
• Multi-hour unplanned morning work absorbed on 2026-04-24: ~3 hours of vendor audit work on what was supposed to be a planning day. Not on the advisor's calendar; did not produce a billable outcome. Advisor named it in real time: "let it go practice" — the naming didn't prevent the work.

ANNOTATION — "What's Explicitly Out of Scope"

Three subsections, not one. This is the structural core of the document.

Lane violations are structural: the firm doesn't do these by identity and expertise. The bullets are written in absolutes ("Payroll processing") not capability-based ("We don't specialize in payroll"). Capability framing invites negotiation; identity framing doesn't. This choice is observed to matter — clients who see "we don't specialize in X" will negotiate ("but you're so good at adjacent things, can't you just..."); clients who see "payroll processing belongs to your payroll vendor" accept the structural fact.

Lever violations are strategic: the firm might do these but the effort won't convert to outcomes because the lever is elsewhere. Each bullet names who has the lever. This matters because the advisor's re-scope move is to surface the lever, not to accept or refuse the whole ask. Lever violations are the sneakiest bleed category — they look in-scope because they're in-lane.

Historical out-of-scope asks are empirical: this is what has actually happened with this client. Each entry is dated, specific, and includes the scope category (lane vs. lever) that the ask violated. This section is the load-bearing evidence — when the advisor sees the pattern about to repeat, the doc confirms "yes, this is the pattern, I've seen it before."

In this example, five MISSED events in 3 months with zero HELD events tells a specific story: the advisor has been fully absorbing the pattern. The Review Log will show the same. The advisor reading this doc needs to see that story to make the wind-down decision.

Speculation has no place here. If the client has never asked for something, it doesn't get listed as out of scope, even if the advisor suspects they might. Mode 3 adds new entries as patterns emerge; Mode 1 documents only what's been demonstrated.

Scope Triggers (Watch For)

These are the specific signals from Acme's side that a new out-of-scope ask is incoming:

• Primary stakeholder emails or calls with subject line "quick question," "got a minute," or "when you have a second." The subject line rarely names the vendor or the scope category. The ask that follows is vendor management or statutory research. (Pattern first documented 2026-02-14; fired 7x through 2026-04-24.)
• An employee sends a tax-related question to the stakeholder, who forwards it to the advisor for "thoughts." The "thoughts" turn into audit work. (Pattern first documented 2026-02-28; fired 3x through 2026-04-24.)
• Quarterly or year-end statutory filing deadlines approach. Vendor issues surface right before deadlines, creating urgency that compresses the scope check. (Predicted; first occurrence 2026-03-15.)
• The stakeholder mentions the vendor's new person, team, or policy change. Vendor staffing changes trigger new rounds of advisor-as-liaison work. The stakeholder often doesn't realize they're positioning the advisor as liaison; they're just venting. (Pattern first documented 2026-03-24.)
• The word "audit" appears in any client email. Unless the firm has explicitly been retained for an audit engagement with defined scope and pricing, this word means unscoped work is being requested. (Pattern observed 3x in Q1.)
• End-of-day Friday urgency. The stakeholder sends urgent vendor-related asks right before the weekend, creating pressure to respond without the normal scope check. The urgency is usually real; the scope violation is the structural problem, not the urgency. (Pattern first documented 2026-04-17; observed concentration in the 3-6 pm Friday window.)
• The stakeholder uses the phrase "we're leaving them anyway." This framing is observed to precede requests for remediation work on the failing vendor — the logic being that since Acme is exiting the vendor, the work is "one-time." It isn't; it's bleed. (Pattern first documented 2026-04-10.)

ANNOTATION — "Scope Triggers"

Each trigger names a specific signal. Not "when things get tense" — "when the stakeholder mentions the vendor's new person." The signal has to be concrete enough that the advisor can recognize it in real time, not retrospectively.

Each trigger names the likely ask. The pattern is: signal → predicted ask → scope category. This lets the advisor short-circuit the usual "maybe this is different this time" rationalization. The doc says: "No, this is the pattern. Here's what they're about to ask for."

Dated pattern observations give the doc credibility. When the advisor returns to this doc in month four and sees a trigger with a "first documented" date from month two and a fire count of 7, they know the pattern holds. It's not the advisor's bias — it's observed behavior.

A trigger like "end-of-day Friday urgency" is legitimate even if it sounds soft. What matters is specificity (time of day + behavior pattern + likely ask), not whether it maps to a person or topic. The test: can the advisor, mid-interaction, recognize this signal firing?

The "we're leaving them anyway" trigger is the subtlest — it's a framing that the client uses sincerely, but it's also structurally predictive of future asks. Triggers like this one require the advisor to trust the doc even when the framing sounds reasonable in the moment.

Scripted Responses (The Consultant Layer)

When the ask is a small favor and the relationship warrants it

Hi [Stakeholder] — happy to take a look. I can give you 30 minutes on this, then I'll need to step back. If there's more to untangle, let's set up a scoped conversation.

Use when: The ask is clearly under an hour, the relationship is warm, and the work won't cascade. Include the time cap explicitly. Do not use this if there's any pattern of the same issue recurring — that's bleed, not a favor. For Acme specifically: any ask related to the vendor situation is recurring, which rules this template out for vendor-flavored asks.

When the ask is outside the firm's lane

Hi [Stakeholder] — this one isn't something I'm the right person for. You need a CPA with tax-filing E&O coverage on this. I can stay with you on how this affects employee comms and the HR-strategy frame — but the technical compliance belongs with the CPA.

Use when: The ask is operational execution, tax filing, vendor accountability, or specialist work the firm doesn't carry. For Acme: this is the template for most vendor-compliance asks going forward.

When the ask is inside the lane but the advisor has no lever

Hi [Stakeholder] — I can tell you how I'd approach this, but I want to be direct: the outcome depends on the vendor acting. I'll be most useful giving you the framework and letting you drive the follow-up, rather than me chasing them for results I can't produce. Here's how I'd think about it...

Use when: The ask is strategic (in lane) but execution requires a third party the advisor can't compel. For Acme: this covers the vendor-accountability framing asks where Acme wants the advisor to "help hold the vendor accountable" — the lever is Acme's, not the advisor's.

When the ask is a genuine scope expansion worth doing

Hi [Stakeholder] — this is bigger than what we scoped for the monthly advisory. I want to do it right, which means a separate scope of work. Let me put together a short proposal — likely 15-20 hours at my hourly rate — and send it over this week.

Use when: The ask is real, billable, within the firm's lane, and has a closable outcome. Formalize before starting.

When the bleed is already active

Hi [Stakeholder] — I need to be direct about something. Since early February I've logged roughly $12,000 of work on the vendor situation. That's outside our monthly advisory, and I haven't invoiced because the situation kept evolving. Before we go any further, I need us to agree on how we close this out — either as a scoped project with pricing, or as a wind-down where I step back after confirming the three remaining statutory corrections. Can we get 15 minutes on the calendar this week to align?

Use when: There's already significant unpaid work, a pattern of continued bleed, and the relationship can absorb a direct conversation. For Acme: Template E is the planned response to the next vendor-related trigger. This is the hardest conversation; consult file 06's "Wind-Down Conversation" advisory play before sending.

ANNOTATION — "Scripted Responses"

Five templates, not one, because the 2x2 matrix has four quadrants plus the ACTIVE BLEED case. Each template is keyed to a specific decision outcome.

Each template has a "Use when" note. This is non-negotiable. Without it, the advisor grabs the wrong template in the moment and damages the relationship.

The templates are voice-shaped by observed hold language, not invented. Phrasings like "I want to be direct," "I'll be most useful," "I want to do it right" are observed markers of advisor language that actually worked in real scope-hold conversations. The kit preserves these patterns while keeping the content anonymized.

For Acme specifically, the templates are tuned: Template B names the specific specialist (CPA with tax-filing E&O coverage) rather than leaving it generic. Template C names the specific third party (the vendor) rather than leaving it abstract. Template E cites the factual $12,000 and the specific remaining items (three statutory corrections) rather than vague language. This tuning is what makes the templates land in a real moment instead of reading as generic.

Template E (Active Bleed) is used sparingly. It's the hardest conversation to have. If Template E applies, the advisor should also read file 06's "Wind-Down Conversation" advisory play before sending.

Current Status

• Active unbilled: ~$12,000 logged on vendor remediation work, February–April current engagement year. Not expected to be recoverable given the client is leaving the vendor; the remediation path is vendor-exit, not invoice.
• Open items: Three statutory corrections still outstanding as of 2026-04-24. Filing status unclear.
• Re-scope conversation: Not yet had. Recommended before any additional vendor-related hours are logged.
• Next expected trigger: Primary stakeholder's follow-up on the three outstanding corrections — likely within 7 days. Template E is the planned response.
• Engagement health read: Relationship strong; structural scope clarity weak. The wind-down conversation is expected to hold the relationship while resetting the structure.

ANNOTATION — "Current Status"

This section is the operational read of where the engagement is right now. If STABLE, it's one line ("No active out-of-scope items. Scope clean as of [date].").

For ACTIVE BLEED, it gets five lines: what's unbilled, what's open, what conversation is pending, what's the next expected trigger, and the engagement health read.

The "engagement health read" line is worth including in ACTIVE BLEED states because it separates relational health from structural health. They're not the same. An engagement can have a strong relationship and a weak structural-scope discipline, which is the most common failure pattern — and the wind-down conversation exists precisely to hold the relationship while resetting the structure.

Cap Tracking

ANNOTATION — "Cap Tracking"

If the table has rows, each row must have a "Trigger at Cap." A cap without a trigger is a soft limit that gets absorbed into bleed. The trigger names the next action: wind-down, re-scope, hand-off, or stop.

This row illustrates the bleed state — the "No cap was set" note is an honest naming of what went wrong structurally. Future Mode 3 updates should show caps being set prospectively on new favors, with trigger actions defined in advance.

If there are no active favors with caps, the table still appears with a single row: "No active favors with caps at this time." Don't delete the table — its presence is a standing reminder that favors must be capped.

Review Log

ANNOTATION — "Review Log"

Reverse chronological — most recent event at the top.

Every event uses a locked event type from file 02: CREATED, HELD, MISSED, EXPANDED, CAP HIT, REVIEWED. The event type carries meaning; "ask came in" isn't an event type.

The Review Log is the engagement's scope-discipline history in one glance. Patterns emerge: in this example, six MISSED events and zero HELD events in Q1 — this is a client where the advisor needs to shift the structural conversation, not just refine tactics. That diagnostic comes from the log, not from memory.

The entries get specific where it matters: named dollar amounts, named triggers, named reasons the event fired. "Template A would have been appropriate; no template used" in the 2026-02-14 entry captures what the advisor now knows in retrospect. These honest retrospectives are what let Mode 2 improve the kit — if an advisor keeps seeing "no template used," the kit's templates need to get more accessible at the decision moment.

If the advisor starts holding scope, Mode 3 adds HELD entries that balance the historical MISSED entries over time. The log becomes a measure of engagement health. A Review Log that shows a flip from all-MISSED to mixed over 3-6 months is the pattern of a kit doing its job.

This document gets reviewed at every monthly advisory session with Acme and updated whenever a new out-of-scope ask surfaces or scope gets held. Mode 3 of the kit handles these updates.

The Golden Example Ends Here

What This Golden Example Teaches

ANNOTATION — Overall Design Lessons

Reading this example end-to-end, the following design choices are worth preserving when the kit generates real scope-check docs:

1. Dense headers with the status flag prominent. Advisors pull this doc mid-conversation; density is a feature. The engagement fee appears because it anchors the bleed calculation structurally.
2. Three-subsection structure for out-of-scope (Lane / Lever / Historical). Each subsection answers a different question. Collapsing them into one list hides the distinction and weakens the decision framework.
3. Historical section names the scope category for each incident (lane vs. lever). This trains the advisor to recognize not just that an incident happened, but why it was out of scope — which makes future trigger recognition sharper.
4. Triggers with fire counts. "Pattern first documented [date]; fired 7x through [date]" is more useful than just a first-documented date. Fire counts tell the advisor whether a trigger is fresh or chronic.
5. Five scripted responses, tuned per client. The templates are anonymized in the vault; in the real doc, they name the specific specialist, the specific third party, the specific dollar amount, the specific remaining items. Generic templates don't land in real moments.
6. Review Log with locked event types AND retrospective commentary. "Template A would have been appropriate; no template used" is the kind of honest retrospective that lets Mode 2 improve the kit. Without this level of honesty, the log is just a diary.
7. ACTIVE BLEED status flag orients the whole doc. A scope-check doc in ACTIVE BLEED state looks different from a STABLE one — the Current Status section expands to include engagement health read, the Cap Tracking has a flagged row, the Review Log is referenced in conversations.

The worst version of a scope-check doc is a generic one: vague "in scope" items, missing historical patterns, unspecific triggers, template-voiced scripted responses. That version sits in the advisor's folder unused. This version gets opened.

What This Golden Example Is Not

ANNOTATION — Scope of the Example

• Not a real client. "Acme Corp" is fictional. The pattern (vendor remediation bleeding into scope) is extracted from observed advisory engagements where this exact shape of bleed has been documented.
• Not a complete engagement picture. This doc is one of several the advisor maintains per client (master plan, project plans, blueprints). It doesn't try to cover engagement strategy — just scope discipline.
• Not client-facing. The candor in this doc would read poorly to Acme. The kit assumes advisor-internal audience.
• Not prescriptive about tone. Templates use a warm-direct voice extracted from observed hold language. Specific advisors tune the voice further per file 02's voice requirements.