Discharge Packet

RX 05 · DISCHARGE FRI 6 NOV '26 · MONTH 16 · 12-LOCATION GROUP · ISSUED ONCE, AT EXIT · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X

A system your team runs without us. The front desk owns its feedback loop, finance owns the readout, your people own the gains. This document ends our revenue from this account, and it is the last thing we owe you.

HOW WE GOT HERE

Rx 01 exam Jul '25 (247-B) → diagnosis (247-D) → 16 months of Rx 03 → retest Sep '26 (247-P) → Q3 recommitment Oct '26: CONCLUDE, elected by you.

WHAT TRANSFERS

12 recurring forms · 14 systems · 9 runbooks · 12 desks. A named owner and a verification date for each, or an honest "not yet".

ADMEN ACCESS

Revoked 6 Nov '26 across 11 systems. Two read-only accounts survive to the 90-day check-in and die 5 Feb '27.

WHAT THIS IS NOT

There is no proposal in this packet and no pricing. Sheet 7 names five things worth re-hiring for and six you should never buy again.

01 · DISCHARGE CRITERIA — SET IN THE DIAGNOSIS (FORM 247-D), SCORED HONESTLY

THESE SIX CONDITIONS WERE WRITTEN INTO THE DIAGNOSIS IN AUGUST '25, BEFORE ANYONE KNEW WHETHER THEY WOULD BE MET · THEY WERE NOT REWRITTEN AFTERWARDS
CONDITIONEVIDENCESTATUS
The retest reads on the Day-0 instruments, and your team can re-run itForm 247-P issued 10 Sep '26; your controller pulled the extract and re-derived two Day-0 vitals from sourcemet
Every recurring document has a named internal owner who has produced it solo at least once9 of 12 forms verified solo — see the matrix on sheet 2 for the three that are notmet, 3 gaps
Attribution coverage of at least 8 channels, traceable in systems you own10 of 13 channels in the census, end-to-end, in accounts held in your name (Form 247-P)met
The weekly desk loop runs three consecutive months with ADMEN out of the roomAug, Sep, Oct '26 — Form 247-K produced at all 12 desks; we attended none of themmet
A monitor fires when something breaks, and a named person answers itThe WATCH monitor runs on ADMEN infrastructure and you have nowhere to run it today. Recipe and thresholds transfer as runbook R-09; unrehomed, it stops on 6 Novnot met
Media buying and budget reallocation have an internal ownerNo one at the group does this work. Settings freeze on 6 Nov. Remediation and a decision date are on sheet 6not met

HOW TO READ THIS PACKET — AND WHEN

SHEET 2Ownership transfer. Twelve forms, who owns each one now, what training they had, and the date competency was verified. Read it this week.
SHEET 3Access and credentials. Every system, and the date our access ends. Verify it yourself; do not take our word for a revocation.
SHEET 4What keeps running, what stops on 6 November, and the costs that move onto your P&L. Give this one to your controller.
SHEET 5Known fragilities. What breaks first without us, in the order we expect it. Read this page in February, not today.
SHEET 6What your team is not yet ready to own, with remediation and dates — and the 90-day check-in.
SHEET 7What to re-hire for, and what never to pay an agency for again. The page we would most like you to keep.

Ownership Transfer

02 · EVERY RECURRING FORM · ITS OWNER · ITS TRAINING · ITS VERIFICATION DATE · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X
VERIFICATION MEANS THE OWNER PRODUCED IT WITHOUT US IN THE ROOM AND THE OUTPUT RECONCILED · ATTENDING A TRAINING SESSION IS NOT COMPETENCE AND IS NOT SCORED AS ANY
FORMOWNER, BY ROLETRAINING RECEIVEDCOMPETENCY VERIFIED
247-B Baseline readingCFOArchive record. Re-runnable by any competent team from the frozen definitions documentn/a — record, not a process
247-D DiagnosisCEOArchive record. Superseded in part by 247-P; both retainedn/a — record, not a process
247-P Post-op vitals · annual retestCFO + controllerRan the Sep '26 extract under observation; re-derived two Day-0 vitals from source; holds the same-store rule in writing10 Sep '26 · next due Sep '27
247-C Operating cadence calendarDirector of opsTwo sessions, then two full cycles run unassisted2 Oct '26
247-K Desk readout · weekly, per deskDesk managers ×12, coordinated by director of opsRubric certification; double-scored against our scorer to ≥ 90% agreement18 Sep '26 · 10 of 12 desks certified; 2 new hires pending, due 15 Dec
247-L Desk ↔ media loop · monthlyDirector of ops + marketing coordinatorThree cycles observed, then run without us in Sep and Octpartial — desk half verified 16 Oct '26; the media half has no owner (sheet 6)
610-R Monthly readout · one pageMarketing coordinator, countersigned by controllerTwo assisted assemblies, one solo; solo output reconciled to ours within 0.3%2 Oct '26
610-M Monthly board packCFO + controllerTwo assisted, one solo. Controller signs the marketing → P&L tie-out, as they already did during the engagement4 Nov '26 · channel-economics page carries the media caveat
610-Q Quarterly recommitmentCEO + CFOOne facilitated cycle (Oct '26) — the one that produced this dischargenot yet — observed once, never self-run. First self-run Q1 '27
302-G Brand system, in daily useMarketing coordinatorTemplates and guardrails; three approvals run solo, including one rejection25 Sep '26
302-S Shot list + per-location asset libraryMarketing coordinatorPlanned and ran one shoot end to end without us; library indexed by location, all 1216 Oct '26 · annual refresh cadence documented in 247-C
118-M Demand vs. capacity mapCFO + director of opsRead it, can interpret it, cannot rebuild it. The refresh needs a data pull and a model we builtnot owned — annual refresh is a re-hire item, and we say so on sheet 7

Nine of twelve, honestly. Two are archive records that need no owner. Seven transfer clean. One transfers half. One has been run once, by us, with your CEO in the room. One does not transfer at all. That is nine of twelve in working order at discharge, and the three exceptions are named here rather than discovered by you in February.
On the two uncertified desks. Both are new hires who joined in October. Their certification is a scheduled task with a date (15 Dec) and an owner (director of ops), and it is the model for every desk hire from here: rubric certification belongs in the job description and the onboarding checklist, not in an agency's scope.

Access & Credentials

03 · REVOCATION SCHEDULE · EVERY SYSTEM, EVERY DATE · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X

Every account was opened in your name on the day it was created, so there is nothing to transfer — only our access to remove. Here is the list, and the dates.

ACCOUNTS WERE HELD IN THE CLIENT'S LEGAL ENTITY THROUGHOUT THE ENGAGEMENT · ADMEN NEVER HELD BILLING OWNERSHIP OF AN AD ACCOUNT, A DOMAIN, OR A DATA STORE · THE ONLY THING BEING TRANSFERRED IS THE ABSENCE OF US
SYSTEMCLIENT OWNER, BY ROLEADMEN ACCESSEFFECTIVE
Google Ads — 12-location structureMarketing coordinator (admin)revoked · manager-account link severed6 Nov '26
Microsoft AdsMarketing coordinator (admin)revoked · manager-account link severed6 Nov '26
Meta business managerMarketing coordinator (admin)revoked · partner access removed6 Nov '26
Google Tag Manager containerWeb vendor (publish) + coordinatorrevoked · publish rights reassigned to vendor first, then our seat removed6 Nov '26
Call tracking platform · 12 DNI numbersDirector of ops (admin)revoked · billing already client-direct6 Nov '26
Call recording & transcription store · PHIDirector of ops + compliance officerrevoked · BAA terminated · ADMEN-held copies destroyed, certificate issued 13 Nov6 Nov '26
PMS read-only export user · PHIControllerrevoked · extract copies destroyed, certificate issued 13 Nov6 Nov '26
Scheduling / booking widget adminDirector of opsrevoked6 Nov '26
Website CMSWeb vendorrevoked6 Nov '26
Google Business Profiles ×12Director of opsrevoked · agency link removed at each location6 Nov '26
Shared credential vault (engagement)deleted · deletion evidence emailed to CFO6 Nov '26
Google Analytics 4 propertyCoordinator + controllerone named ADMEN account, read-only, for the 90-day check-inrevoked 5 Feb '27
BI dashboard / data warehouseControllerone named ADMEN account, read-only, for the 90-day check-inrevoked 5 Feb '27
DNS / domain registrarClient ITnever held — we have never had access to this and did not ask for itn/a

You hold the switch, not us. Nothing on this list needs our cooperation to remove. If you decide on 7 November that the two read-only accounts should go early, remove them and tell us afterwards; the check-in still happens, we just read what you show us instead. An agency that has to be asked twice to leave an account was never really handing it over.
Sequencing, because order matters more than speed. Two of these revocations are dependent: Tag Manager publish rights were reassigned to your web vendor before our seat was removed, and the ad-account conversion imports were re-pointed to your coordinator's credentials before the manager link was severed. Revoke in the wrong order and a live integration orphans silently. If you ever remove an agency again, do it in this order and test the integrations afterwards.
Verify it yourself. Every line above can be checked in the platform's own user list in under ten minutes. Do that rather than trusting this table. We would.

What Keeps Running

04 · CONTINUITY · WHAT STOPS ON 6 NOVEMBER · WHAT MOVES ONTO YOUR P&L · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X

KEEPS RUNNING — NO ADMEN INVOLVEMENT REQUIRED

  • Call tracking and dynamic number insertion across all 12 locations
  • Form, booking and call events; first-click-to-chair attribution
  • Nightly PMS → warehouse export (client IT owns the job · runbook R-04)
  • Offline conversion import to the ad platforms — until a schema change (F-02)
  • The weekly desk huddle at 12 desks (247-K), client-run since August
  • Monthly readout (610-R) and board pack (610-M), assembled by your team
  • Location page template, brand system (302-G), asset library (302-S)
  • Ad accounts continue to spend, on settings frozen 6 Nov
  • The same-store reporting rule: Parkway-11 stays on its own line

STOPS — SAME DAY, WITHOUT A WIND-DOWN PERIOD

  • ADMEN media management: bids, budget reallocation, geo and keyword work, creative rotation
  • ADMEN assembly and QA of 610-R and 610-M
  • ADMEN attendance at the desk huddles and the monthly desk↔media loop (247-L)
  • Creative production and the shoot cadence
  • The WATCH threshold monitor. It runs on our infrastructure. Recipe, thresholds and alert routing transfer as runbook R-09 — but if you have nowhere to run it, it stops on 6 Nov and nothing fires when something breaks
  • Our reading of your board decks
COSTS THAT MOVE ONTO YOUR P&L AT DISCHARGE · THESE SAT INSIDE THE RETAINER AND NOW BILL DIRECT — A TRANSFER OF A COST, NOT A NEW ONE. THE RETAINER ITSELF ENDS, AND IT WAS THE LARGEST OF THE THREE LINES
LINEGLPER MONTHNOTE
Call tracking + DNI + transcription, 12 locations6210$840annual contract, renews Mar '27 — reassign before then
Scheduling / booking widget6210$220per-location tier
BI dashboard — 2 seats6210$190controller + coordinator
Data warehouse + nightly export compute6210$145usage-based; grows as you add locations
Tag manager, analytics, ad platform accounts6210$0no licence cost
TOOLING SUBTOTAL6210$1,395$16,740 / yr
Internal labor to run the cadence — coordinator 16 hrs, controller 6, director of ops 4602026 hrs / moalready being spent; now the whole of it
Media spend6200unchangedalways your money · ~$42K / mo

The honest arithmetic your controller will do anyway, so we have done it here. Discharge removes the retainer and adds $1,395 a month of tooling that was previously invoiced through us, plus 26 hours a month of internal time that was already partly being spent. The net is strongly in your favour and we are not going to pretend otherwise to make leaving feel expensive. What you are buying back with that money is the requirement to actually run it — and the fragility page is the honest account of what happens if you don't.

Known Fragilities

05 · WHAT BREAKS FIRST WITHOUT US · SYMPTOM · TIME TO BREAK · WHO FIXES IT · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X

Every system we have ever built has broken somewhere. Here is where this one will, in the order we expect it, with the runbook for each. Read this page in February, not today.

TIME-TO-BREAK IS OUR OWN OBSERVATION ACROSS PRIOR DISCHARGES, NOT A PUBLISHED FIGURE — NOBODY PUBLISHES DECAY RATES FOR CLIENT-RUN MARKETING INSTRUMENTS AND WE ARE NOT GOING TO INVENT ONE
IDWHAT BREAKSFIRST SYMPTOM · TIME TO BREAKWHO FIXES ITRUNBOOK
F-01Tracking numbers stripped from location pages by a template editAttribution coverage falls; paid search appears to "stop working" on the readout while the calls keep arriving. First site edit — usually inside 90 daysWeb vendor + coordinatorR-02 · DNI smoke test is a line item on the 247-C monthly checklist; restore snippet, verify 3 numbers by test call
F-02Offline conversion import fails after a PMS schema changePlatform bidding degrades silently over 2–3 weeks; cost per new patient rises with no visible cause. At each PMS upgrade — about twice a yearClient IT + coordinatorR-05 · re-map columns, re-upload trailing 30 days, confirm row counts match the PMS
F-03The desk huddle dies when a desk manager leavesBooking rate at that desk drifts back toward its Day-0 reading within a quarter. On the first departureDirector of opsR-03 · rubric certification written into the desk-manager job description and onboarding; 247-K continues with an interim owner
F-04The monthly readout gets skippedSkipped twice it does not return, and the group goes back to steering on the ad platforms' own numbers. First month with a close crunchControllerR-06 · 247-C puts 610-R inside the financial-close block. If it slips, it slips with the close, never instead of it
F-05Definitions driftA location starts coding late cancels as no-shows again and next year's retest is no longer comparable. 6–12 months, silentlyControllerR-07 · the frozen definitions document has a change log; any change needs a written entry and a restatement of both readings, as 247-P §02 did
F-06Spend defaults to last month's allocationBudget stops following capacity; ads keep running into pods at 94% utilisation, buying waitlist instead of production. Within 60 daysnobody, todayR-08 · capacity throttles hard-coded at Central-01 and North-04 as an interim. See sheet 6
F-07The quarterly recommitment is never scheduledNobody books a meeting whose purpose is to consider stopping. First quarterCEOR-01 · 610-Q is a standing calendar item with the case for concluding pre-filled. If it is not on the Q1 '27 calendar by 15 Dec, it will not happen
F-08The WATCH monitor has nowhere to runNothing fires when something breaks, so F-01 through F-04 all become silent failures found weeks later in a monthly readout. Immediately at dischargeclient IT, if they take itR-09 · thresholds, alert routing and schedule, written to run anywhere that can execute a scheduled job

THE HONEST SHAPE OF THIS PAGE

Six of these eight have an owner and a runbook, and a competent team should handle them. Two do not, and they are the same two conditions this discharge failed on sheet 1. The dangerous ones are not the loud failures — a site that loses its tracking numbers is obvious within a month. The dangerous one is F-05: definitions drifting quietly until next September's retest compares two things that are no longer the same measurement. That failure is invisible for a year and then it invalidates the only instrument you have for judging anyone who works on this account after us — including us, if you ever hire us back.

Not Yet Yours

06 · WHAT YOUR TEAM CANNOT YET OWN, WITH REMEDIATION AND DATES · THE 90-DAY CHECK-IN · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X

NAMED, NOT SOFTENED · A DISCHARGE PACKET CLAIMING PERFECT READINESS IS NOT A DISCHARGE PACKET, IT IS AN INVOICE WITH A NICE COVER

① MEDIA BUYING AND BUDGET REALLOCATION — NO INTERNAL OWNER EXISTS Nobody at the group does this work, and a quarter of training did not produce someone who does. Frozen settings hold for roughly one quarter, then decay as auctions, seasonality and your own chair capacity move underneath them. The specific exposure is on your own capacity page: two pods run at 94% utilisation, and spend pointed there buys waitlist, not production. Interim, at no charge, live 6 Nov and expiring 15 Dec: settings frozen, daily caps 10% below current spend, capacity throttles hard-coded at Central-01 and North-04, written escalation path to the coordinator. Three routes. Decision due 15 Dec '26:
  1. Hire it in. About half an FTE at this spend level, 60–90 days to productive. Cheapest over twelve months, slowest to start. Our recommendation if you intend to keep opening locations.
  2. An arm's-length media vendor on a scope you control. Hand them 610-R as the scorecard and 118-M as the geographic constraint, cap the engagement at execution, and never let the people buying the media also grade the media.
  3. ADMEN on a quarterly retainer at our standard rate. Listed because it is real, flagged because we are the one party here who is not neutral about it. Same rate we would quote a company that had never met us.
② ATTRIBUTION-STACK REBUILD — YOUR TEAM CAN KEEP IT ALIVE, NOT REBUILD IT Runbooks R-02 and R-05 cover maintenance and your coordinator has run both. Neither covers reconstruction. A website migration or a PMS change breaks the stack in ways a runbook cannot anticipate, and the failure is silent: the reports keep rendering, they just stop being true. Remediation: any site or PMS project carries a re-instrumentation line in its budget before it starts, and Form 247-B's definitions are re-validated after it ships. This is a re-hire item and it is on sheet 7. Do not let a web vendor tell you they will "handle the tracking."
③ READING PARKWAY-11 — YOUR TWELFTH SITE HAS NO BASELINE, AND NOBODY THERE HAS YET CALLED IT ALONE Eleven of your twelve locations carry a Day-0 reading. Parkway-11 does not and never will — it opened in March '26, inside the engagement. Every comparison in Form 247-P is same-store across the eleven with Parkway on its own line, and your team has reproduced that split correctly twice in 610-M. What they have not had to do is judge it: at month eight of a ramp, a loaded cost per new patient of $773 against a same-store $221 is either an ordinary ramp curve or a site that will not clear, and on a monthly report those look identical. We have been making that call. Remediation — a rule, not a skill: Parkway keeps its budget on an explicit clock. If loaded cost per new patient is not under $450 at the December close, the site moves to organic and referral only, and that is the CFO's decision taken on the number without a meeting about narrative. The same rule attaches to every location you open from here: reported on its own line from the day it opens, never blended into a growth rate, and carrying a written kill-or-scale threshold and a date before its first dollar of media is spent. Write the threshold when you sign the lease, while nobody is invested in the answer.

07 · 90-DAY CHECK-IN — BOOKED NOW, THU 4 FEB '27 · 90 MINUTES · NO CHARGE

The check-in exists because three of the eight fragilities on sheet 5 are expected inside 90 days. It is scheduled at the point of maximum usefulness, not the point of maximum sales pressure.

What to Buy Again

08 · THE RE-HIRE LIST AND THE NEVER-AGAIN LIST · THE PAGE WE MOST WANT YOU TO KEEP · SPECIMEN

CONFIDENTIAL · RX 05FORM 247-X

WORTH RE-HIRING FOR — OURS OR ANYONE'S

  • A re-baseline after a structural change — three or more locations acquired, a PMS change, or a payer renegotiation. The instruments must be re-frozen (247-B) or your trend line becomes fiction.
  • A market read before you sign a lease — demand vs. capacity (118-M). Cheap next to a bad site, and the only analysis in this file whose job is to say don't.
  • Site rebuild or migration — with a re-instrumentation line in the budget. Non-negotiable.
  • Media execution — if you decline to hire it internally. Scope it to execution and keep the scorecard.
  • Pre-exit — an instrumented growth narrative and a diligence index, 12–18 months before a transaction. Everything in this packet is already the raw material, which is why that work is cheap for you and expensive for a group that never instrumented anything.

NEVER PAY AN AGENCY FOR THIS AGAIN

  • Monthly reporting. Your coordinator assembles 610-R in about two and a half hours and your controller signs the tie-out. Nobody should invoice you for a document you already produce.
  • Call scoring and desk coaching. It is the desk manager's job. An outsider doing it converts coaching into policing — which is why we stopped attending in August.
  • Re-instrumenting what is already instrumented. When a vendor proposes rebuilding your tracking, ask which row of Form 247-B it moves. If they cannot name one, it moves none.
  • A brand refresh as a standalone project. 302-G is in daily use; refresh the assets on the 302-S cadence instead.
  • Content sold by the unit. No number in this file moves on a post count.
  • Any retainer that cannot name the instrument it moves and the P&L line that instrument touches. That is the whole test — and you now own every instrument that would pass it.

The failure I have actually seen most often is none of the eight on sheet 5. It is that the readout keeps getting produced, correctly, every month — and stops being read. Watch the open rate on 610-R the way we did. If nobody opens it twice running, change it or stop sending it. A report nobody reads is worse than no report: it trains the room to ignore the instrument, and then somebody cites it in a board meeting and the whole thing collapses at once.

— MARGIN NOTE, DISCHARGING PARTNER, AT EXIT

THIS PACKET CONTAINS NO PROPOSAL, NO RENEWAL OPTION, AND NO PRICING. IT ENDS OUR REVENUE FROM THIS ACCOUNT ON 6 NOVEMBER. IF ANY SENTENCE IN IT READS AS A PITCH, THAT IS A DEFECT — REPORT IT AND WE WILL STRIKE IT.

— specimen —

DISCHARGING PARTNER, ADMEN

— specimen —

CLIENT CFO — ACCESS REVOCATION CONFIRMED · DATE

— specimen —

CLIENT CEO — DISCHARGE ACCEPTED · DATE