Index / Agency & Vendor Oversight
PB-039

Vendor Fall-Out Analysis

Traces where cases from each vendor die after signing, what the file says the reason was, and how late you caught it.

The spec — copy this

Set up a new bot for me that runs monthly per tort. Walk me through connecting my case management system and wherever lead source is recorded, then configure it: for the signed cases sourced from each vendor, trace what happened after the retainer — cleared review and proceeding, failed medical records review, no qualifying injury, no documented treatment, exposure or product not confirmed, statute problem discovered late, prior representation discovered late, client unreachable after signing, client withdrew, firm declined to file — and report the fall-out rate by stage and by reason for each vendor, comparing only within the same tort and the same cohort vintage. For every fall-out, record how far into the file the disqualifier was discovered and what would have surfaced it at intake, because a disqualifier found in month four is a screening failure on my side as much as a lead quality problem on theirs, and I want those two separated. Give me the cost of the fall-out by vendor: what I advanced on cases that never survived. Report reasons exactly as they are recorded in my file and never infer a reason that is not documented. Ask me which vendors and torts to include, my stage definitions, what counts as fall-out versus a normal decline, my minimum sample, and my cohort windows, run it on a tort I have already worked through so I can check its reasons against my own, then save it.
Paste into an assistant that can connect to your systems.◆ Ethics note below — read before you run it

Connect first

The spec asks for these as it goes — however you normally connect them works. Nothing needs to be set up in advance, and a system named here is usually an example rather than a requirement. If yours has an API or an export, the spec generally adapts.

What it never does
  • Attribute a fall-out to vendor misconduct — it reports the reason recorded in your own file
  • Infer a reason that is not documented in the matter
  • Compare vendors across different torts or cohort vintages
  • Close, reclassify, or alter any matter
Agency & Vendor Oversight — category rule

These specs are written to establish facts, not to build a case. Every one reports observed gaps and the mechanism behind them, and none concludes that a vendor or agency acted in bad faith — because the most common answer is a definitional mismatch or a gap in your own intake, and the second most common is something a contract already addresses. Before you put a finding in writing to a counterparty, read your agreement and have counsel look at it.

Before you run this

Fall-out has two authors and this spec is built to separate them. Before you take a number to a vendor, look at how late your own process caught the disqualifier — the answer is frequently a screening fix, not a vendor problem.

Category
Agency & Vendor Oversight
Contributed by
Jacob Malherbe @jacobmalherbeMass Tort Ad Agency
Approval gate
A named human approves before anything sends, files, or publishes.
Last verified
2026-08-19

More in Agency & Vendor Oversight