Monitoring, Drawdown Gates, and Early-Warning Signals

Intake underwriting is a snapshot; the case is not static

Most litigation finance underwriting effort concentrates at intake and drops off sharply afterward, with the next serious re-evaluation happening only when the next capital call or a settlement offer forces the question. Between those points, the case is generating signal continuously: motions filed and their outcomes, deposition testimony, expert disclosures, scheduling order amendments, and changes in the defendant's litigation posture (change of counsel, insurer reservation-of-rights letters, public statements about the litigation). Almost none of this is systematically captured and compared against the intake assumptions in most funds' operating processes — it lives in outside counsel's status updates, read and then not structured into anything comparable to the original underwriting model.

A monitoring framework closes that gap by defining, at intake, the specific events that would move the case's probability or duration assessment materially, and then tracking for those events as the case develops — rather than waiting for a scheduled review date to ask whether anything has changed.

What an early-warning signal actually looks like

Useful early-warning signals are specific and falsifiable, not vague ("case is not going well"). Examples: an adverse ruling on a dispositive motion that was underwritten as low-probability at intake; a scheduling order slipping by more than a defined threshold relative to the case's duration model, indicating drift toward the tail of the duration distribution; a change in defense counsel to a firm with a documented pattern of aggressive litigation rather than early settlement; an insurer issuing a reservation-of-rights letter, which signals the carrier may be building toward a coverage dispute that reduces the practically collectable recovery even if the underlying liability case succeeds; or a co-defendant settling out on terms that shift the allocation of remaining liability onto the defendant your position depends on.

Each of these should map to a defined response in the monitoring framework — not necessarily a stop-funding decision, but at minimum a required re-underwriting event before the next capital tranche is released.

Structuring drawdown gates around monitored signals

Multi-tranche funding structures should tie subsequent drawdowns to specific, pre-defined milestones and the monitoring signals attached to them — survival of a dispositive motion, a favorable claim construction or class certification ruling, or completion of a discovery phase without a materially adverse development — rather than releasing capital on a fixed calendar schedule regardless of how the case has developed. A gate structured this way gives the funder a natural point to reduce, pause, or reprice exposure when monitoring signals move against the original underwriting thesis, without requiring a full unwind of an already-funded position. It also creates a disciplined record: each gate decision documents what was known at that point, which sharpens future underwriting by making it possible to check, after the fact, which early-warning signals actually predicted the eventual outcome and which did not.

Who owns monitoring matters as much as what gets monitored

A monitoring framework is only as reliable as the incentives of whoever is running it, and the person best positioned to notice an adverse development in a funded case — the originator who sourced it, or the case manager who has been tracking it since intake — is frequently the same person whose performance metrics reward continued funding rather than flagging deterioration. Funds that assign monitoring and drawdown-gate decisions to the same team responsible for origination volume are structurally set up to under-report early warning signals, not because anyone is acting in bad faith, but because the incentive to keep a funded case moving forward is real and rarely made explicit.

Separating the monitoring function from the origination function — even informally, through a required independent sign-off at each drawdown gate — removes that structural conflict and creates a natural point where a second set of eyes, without a stake in the original funding decision, reviews whether the case still matches its intake thesis before more capital goes out.

Where a fund is too small to fully separate the two functions into different individuals, the same discipline can be approximated with a documented, mandatory checklist review at each gate — a fixed set of questions about case status that must be answered and recorded before capital is released, regardless of who is answering them. The value is in making the review structured and recorded rather than informal and undocumented, so that a pattern of consistently optimistic answers becomes visible in the record over time even without a fully independent reviewer in place.

What to ask for from an intelligence provider

• 01A monitoring framework defined at intake, specifying which events would materially move the probability or duration assessment — not a generic quarterly check-in.
• 02Structured tracking of docket activity against the original duration model, so drift toward the tail is visible before the case fully resolves.
• 03Drawdown gates tied to defined case milestones rather than a fixed disbursement calendar.
• 04A post-resolution review process that checks which monitored signals actually predicted the outcome, feeding back into the next underwriting cycle.
• 05A documented separation — organizational, or at minimum procedural — between whoever originated a position and whoever signs off on releasing the next funding tranche against it, recorded well enough to be reviewed later.