Blog · Published May 1, 2026 · 12-minute read

The discovery-scope-creep flag: when a contingency case crosses out of cost-basis and how to know in real time

Q: What does it mean for a contingency case to be 'out of cost-basis'?

A contingency matter is in cost-basis when the cumulative hours invested, valued at the firm's notional billing rate, are less than the expected contingent share of the case — the product of the fee percentage, the expected settlement value, and the probability of recovery, plus any statutory fee-shifting recovery the case is likely to produce. The matter is out of cost-basis when that inequality flips: the lawyer has already worked more than the eventual contingent share will compensate. Past that line, every additional hour worked is uncompensated unless the eventual recovery exceeds expectations or a fee-shifting award supplements the contingent share. The line is computed continuously; the practice that does not capture actual hours per case cannot compute it.

Q: What is the discovery-scope-creep flag, exactly?

It is an internal, firm-side warning signal that fires the first time a configured threshold of expected contingent share is reached on a specific matter. The default threshold is 70%: when cumulative captured hours × notional billing rate reaches 70% of the expected contingent share, the matter is flagged for partner review. The flag does not fire on dollar terms with the client; it fires on the firm's spreadsheet. Its purpose is to surface the conversation about the case's economics while the practice still has options — fee-structure renegotiation, count dropping, early settlement, redirected work — rather than discovering the crossing after the case has resolved at a number below the cost basis.

Q: How does this differ from the lodestar fee petition?

The lodestar fee petition is the post-resolution document filed in fee-shifting cases (§ 1988, Title VII, ADA, FCRA, FDCPA, FMLA, ERISA § 502(g)) that asks the court to award statutory attorney's fees on top of the contingent share. The discovery-scope-creep flag is a pre-resolution internal signal evaluated continuously through the life of the case. Both depend on the same underlying input — captured hours per matter — but they consume the data at different points in the case lifecycle and for different purposes. The flag tells the lawyer whether to keep working at all; the petition tells the court what to award once the work has been done and the case has been won.

Q: Doesn't ABA Model Rule 1.5 limit fee renegotiation mid-case?

Model Rule 1.5(a) requires fees to be reasonable and Rule 1.5(c) requires contingency-fee agreements to be in writing, signed by the client, and stating the percentage. Mid-case fee modifications are not categorically prohibited but are subject to substantially higher scrutiny than original engagements: the lawyer must demonstrate the modification is reasonable, the client gave informed consent in writing, the lawyer disclosed the right to seek independent counsel, and the modification is not the product of overreaching. Comments to Rule 1.5 and a body of state-bar ethics opinions counsel that the cleaner path is generally to stop work or withdraw under Rule 1.16 rather than to renegotiate the fee while continuing to represent. The flag fires before that decision; the conversation it triggers may end in withdrawal, in continued representation at the original fee, in dropping a count to focus on the prevailing claim, or in early settlement. The fee modification path exists but is the option of last resort.

Q: What is the dollar impact of the flag, portfolio-wide?

On a typical five-case contingency book, the cases that cross out of cost-basis are concentrated in two or three matters per year, not five. The expected dollar impact of catching those crossings at 70% of expected contingent share rather than at resolution is the avoided uncompensated work past the crossing point — typically 80 to 250 hours per affected case, valued at the notional billing rate. On the affected cases we have modeled, the recoverable margin per case runs $20,000 to $60,000; portfolio-wide on a five-case book with two crossings, the expected impact runs $40,000 to $120,000 per year. That is the same range the contingency-fee leak post estimates for the broader leak, with the discovery-scope-creep flag responsible for the largest single contribution to it.

Q: Does the flag work for small or simple contingency matters?

It works best for matters with non-trivial discovery exposure: plaintiff-side employment, civil rights, FCRA/FDCPA consumer with class allegations, ERISA benefits with administrative-record disputes, products liability with expert-discovery, qui tam, and complex personal injury with significant medical-records discovery. For straightforward auto-PI matters that resolve in pre-litigation demand or at policy limits, the cost-basis crossing rarely happens because total hours invested are bounded. The flag is a non-event for cases that resolve cleanly inside their initial scope; its value is concentrated in the matters where it would otherwise be a surprise.

The contingency-fee leak post argued that the largest single dollar variable in a plaintiff-side practice is the case that settles or is dropped at or below cumulative cost-basis — and that the practice generally cannot tell when that crossing has happened in real time. The lodestar fee-petition affidavit walkthrough was the post-resolution practical companion: how to draft the affidavit so that the records-quality discount is minimized and the cost-basis crossing is at least partially recovered through statutory fees. This post is the pre-resolution practical companion: the signal-detection mechanism itself, the four shapes the crossing actually takes in discovery, a worked example with month-by-month numbers, and the four options the practice has when the flag fires.

TL;DR

A contingency case is in cost-basis when cumulative captured hours × notional billing rate < fee_pct × E[settlement value × probability of recovery], plus any statutory fee-shifting recovery the case is likely to produce. The case is out of cost-basis the first week that inequality flips. The discovery-scope-creep flag is the internal warning that fires when a configured threshold of the expected contingent share is reached — the default is 70% — so that the conversation about the case's economics happens before the crossing rather than after it. The flag depends on a single input the practice has historically not captured: actual hours per case, week over week. Passive metadata-only capture supplies that input without manual timekeeping. The four shapes the crossing takes in discovery are defendant motion practice, document-production explosion, deposition multiplication, and expert-witness scope creep; each of the four has a recognizable trajectory in the captured-hours data. The four options when the flag fires are: continue (with eyes open), drop a count to focus on the prevailing claim, accept early settlement at a number the practice would otherwise have rejected, or initiate the difficult Rule 1.5 / Rule 1.16 conversation about fee modification or withdrawal. On a typical five-case contingency book, the expected portfolio-wide dollar impact of catching the two or three crossings per year at 70% rather than at resolution runs $40,000–$120,000.

Why the crossing is invisible without the input

The arithmetic of cost-basis is not subtle. The lawyer's investment in a contingency matter is the cumulative hours worked, valued at a notional billing rate that approximates what the lawyer would have charged on an hourly engagement of the same complexity. The lawyer's expected return is the contingency percentage of the expected settlement value, weighted by the probability of recovery, plus any statutory fee-shifting award the case is likely to produce on prevailing claims. The case is in cost-basis when investment is less than expected return. The case is out of cost-basis when investment crosses expected return. The line is computed continuously, every week the case is open, and it moves in two directions over the life of the case: investment moves monotonically up, and expected return moves around as discovery clarifies the actual exposure, the actual liability theory, and the actual probability of recovery.

The lawyer who is keeping clean per-matter hour records can compute the line. The lawyer who is not — and the contingency-heavy solo population is, on every survey we have seen, the population that captures hours least systematically — cannot. The reason is well-rehearsed: hours per contingency matter are not used to bill the client, the manual cost of recording them is non-trivial, and the value of the data is hidden because the most consequential single use of it is the one the practice has historically not been doing (the cost-basis check). The data is exactly as valuable as the analysis run against it. With no analysis, the data is nuisance overhead. With the analysis, the data is the early-warning system on the largest single dollar variable in the year.

The structural ask of this post is small: what would the early-warning system look like, and what data does it require, given that the bottleneck is precisely the one piece of data the practice has not been recording. The implementation question — how to capture the data without imposing the manual-timekeeping cost the practice has rationally refused — is answered in the privilege-preserving metadata-only architecture post. Here we focus on what to do with the input once it exists.

The flag, formally

For each open contingency matter, the firm holds three numbers. (1) The cumulative captured hours, summed weekly from the passive-capture surface — phone calls associated with the matter, document edit time on matter-tagged files, calendar time on matter-tagged events, email-thread participation on matter-coded correspondence, and the fee-petition-grade time entries the lawyer or paralegal has approved into the matter file at the end of each week. (2) The notional billing rate, set per-lawyer at firm onboarding — the rate the lawyer would have charged on an hourly engagement of comparable complexity, typically anchored to State Bar economics survey data and recent fee orders. (3) The expected contingent share, computed from a structured matter file and updated as discovery proceeds: fee_pct × E[settlement value × probability of recovery] + E[fee-shifting award], where each term is the lawyer's working estimate revised at scheduled points in the case (after the answer, after the close of fact discovery, after dispositive motions, after expert disclosures, after settlement-mediation participation).

The cost-basis ratio is the first number times the second number, divided by the third. A ratio below 1.0 means the case is in cost-basis; a ratio at or above 1.0 means the case is out. The flag fires when the ratio crosses a configured warning threshold — the default is 0.7. At that point the matter is added to the partner-review queue and a one-page report is generated: cumulative hours, hours by capture surface, hours by case-phase tag, the trailing-four-week burn rate, the most recent expected-contingent-share estimate, the underlying inputs to that estimate, and the projected ratio at three points (constant burn, accelerated burn matching the trailing four weeks, and decelerated burn matching the prior four-week median).

The flag does not, by design, fire automatically on the client. The information is firm-side intelligence, not client-disclosed. It informs the partner conversation that produces the next decision; the next decision then determines what, if anything, is communicated to the client and in what form. The flag is the conversation's trigger, not the conversation itself.

The four shapes the crossing actually takes

Across the contingency books we have studied, the cost-basis crossing has four recognizable shapes. Each shape leaves a distinct signature in the captured-hours data, which is why the report the flag generates is organized by capture surface and case-phase tag rather than as a single aggregate hours number.

(1) Defendant motion practice. The defendant files, in sequence: motion to dismiss; motion for partial judgment on the pleadings; motion for protective order; motion to compel; motion in limine; motion for reconsideration; cross-motions for summary judgment. Each motion costs the plaintiff's lawyer 25 to 60 hours of brief, declaration, and oral-argument preparation. A case originally scoped at 200 hours of pre-trial work absorbs 400 to 800 hours of motion practice over twelve to eighteen months. The signature in the captured-hours data is a steady-state high-burn rate on document-edit time without a corresponding increase in deposition time — the lawyer is at the keyboard, not at the witness chair.

(2) Document-production explosion. The defendant produces 250,000 documents in response to a request that contemplated 5,000. The plaintiff's lawyer either reviews them or moves to compel a re-production with usable specifications, which itself costs hours and may not succeed. The signature is a sharp uptick in document-edit-and-review time concentrated in a four-to-eight-week window after the production date — a step function in the burn rate, not a steady rise.

(3) Deposition multiplication. The case moves from a planned three-deposition discovery (plaintiff, defendant 30(b)(6), defendant CEO) to a thirteen-deposition discovery as third-party witnesses are noticed. Each deposition costs five to twelve hours of preparation, four to six hours of taking, and three to five hours of post-deposition follow-up — roughly fifteen to twenty-five hours per deposition. The signature is a sustained uptick in calendar time on deposition-tagged events plus a corresponding rise in document-edit time on deposition-prep memos.

(4) Expert-witness scope creep. The case adds a damages expert, then a liability expert, then a rebuttal expert, then a sur-rebuttal in response to defendant's rebuttal. Each expert engagement carries roughly forty to one-hundred hours of attorney time on retention, scope-of-work memos, expert deposition preparation, expert deposition defense, and Daubert briefing. The signature is a slow, irreducible burn over six to nine months that does not respond to motion-practice or deposition-pace changes — the expert work proceeds on its own clock.

A fifth shape — third-party subpoena chains that snowball as each subpoena recipient implicates further custodians — is the most-litigated discovery-scope phenomenon and the hardest to predict in advance. It produces an irregular signature: episodic spikes in document-edit time and motion-to-quash defense, interspersed with quiet weeks. The flag handles it the same way as the others — a ratio crossing 0.7 is a ratio crossing 0.7 regardless of the underlying shape — but the shape diagnosis informs which option the practice picks once the flag fires.

A worked FCRA example

Consider a single-plaintiff Fair Credit Reporting Act case alleging willful 15 U.S.C. § 1681e(b) accuracy violations. The retainer is the standard 40% contingency on net recovery, and the case is filed with full appreciation that the FCRA is a fee-shifting statute under 15 U.S.C. § 1681n(a)(3). The lawyer's notional billing rate is $475 per hour. The expected settlement value, on the lawyer's working estimate at the time of filing, is $90,000 — a midpoint between the realistic floor (statutory damages of $1,000 to $5,000 per violation plus modest actual damages) and a credible willful-violation ceiling that includes punitive exposure. The probability of recovery is 0.55 (slightly favorable, but the defendant has a non-frivolous willfulness defense). The expected contingent share is therefore 0.40 × 0.55 × $90,000 = $19,800. The expected fee-shifting award is conservatively estimated at $40,000 (a fee-shifting solo's working estimate after discounting for the records-quality discount and for the practice's prior fee-order history). The total expected return is $59,800.

The case proceeds. The defendant files a motion to dismiss in month two; the lawyer briefs it. The defendant produces 80,000 documents in month four where the lawyer expected 3,000; the lawyer re-reviews and moves to compel a re-production with metadata. The defendant files a motion for protective order in month six and the lawyer briefs that. By month seven, captured hours stand at 84. Cost-basis ratio: (84 × $475) / $59,800 = 0.667. By month nine, captured hours stand at 110. Cost-basis ratio: 0.873. The 0.7 threshold was crossed in week 38 of month nine, and the flag fires.

Without the flag, the lawyer continues. The defendant files a motion for summary judgment in month eleven (50 additional hours of brief and declaration). The court denies it in part. Mediation is set for month thirteen and the parties settle for $52,000 — substantially below the working estimate, on the strength of a partial summary-judgment ruling that signaled the willfulness count was the weakest. The contingent share is $20,800. The lawyer files a fee-shifting petition for the remaining hours; after a 28% records-quality discount applied at the lodestar paragraph, the awarded fee is $44,500. Total recovery: $65,300. Captured hours at resolution: 187. The cost-basis ratio at resolution was (187 × $475) / $65,300 = 1.36. The case ran 36% past cost-basis. The 36% over-run is approximately 50 hours of uncompensated lawyer work — about $23,750 of value — concentrated in months ten and eleven on the summary-judgment briefing.

With the flag firing in month nine at 0.7, the practice has options that month-thirteen resolution-discovery does not have. The most consequential is dropping the willfulness count to focus on the negligence count, which the partial summary-judgment ruling later validated as the cleaner path; the second is moving for an early settlement conference; the third is simply tightening the scope of summary-judgment opposition to the negligence count alone. Each of those options would have shaved 30 to 60 hours from the back half of the case. On the same case, with the flag, the projected total recovery is similar but the cost basis at resolution drops from $88,825 to roughly $65,000, recovering most of the $23,750 of uncompensated value the unflagged path absorbed.

What the practice does when the flag fires

The flag is a conversation trigger, not a conversation. Four options are on the table. The first is to continue with eyes open: the case is genuinely expected to recover above cost-basis at resolution despite the flag, and the trailing four-week burn rate plus the projected case timeline support that judgment. The flag-firing serves as documentation that the partner reviewed the matter and confirmed continuation; the report goes into the matter file. The second is to drop a count. Bad-archetype cases often masquerade as good-archetype cases until a count fails on dispositive motion; flagged cases can have a count proactively narrowed before the dispositive-motion phase to concentrate effort on the prevailing theory. The third is to accept early settlement at a number the practice would otherwise have rejected: the flag changes the risk-adjusted calculus, and a $42,000 mediation offer that looked rejectable at month seven looks acceptable at month nine when the alternative is another four months of uncompensated motion practice.

The fourth option is the difficult one: ABA Model Rule 1.5 fee-modification or Rule 1.16 withdrawal. Both paths are available in extreme cases — modification with informed written consent and (where the rules of the relevant jurisdiction require) the client's right to seek independent counsel; withdrawal under Rule 1.16(b) where the client has rendered the representation unreasonably difficult, has insisted on a course the lawyer considers imprudent, or where the financial burden has materially worsened. Both paths are also high-risk: the lawyer who modifies a fee mid-engagement under pressure of a flagged matter is exposed to disciplinary review and to client-side fee-dispute proceedings; the lawyer who withdraws is exposed to the procedural costs of motion-to-withdraw and to the client's possible bar complaint. The cleanest version of the conversation is the one that does not invoke either path, and instead concludes in early settlement or count-dropping. The dirty version of the conversation is the one that takes the form of an awkward client meeting in month thirteen after the case has resolved at $42,000 and the lawyer realizes the contingent share does not cover the second associate's salary for the year. The flag's purpose is to force the cleaner conversation while it is still cleanly available.

The portfolio-level dollar impact

On a five-case contingency book — typical for a solo plaintiff's-side employment, civil-rights, or FCRA/FDCPA consumer practice — the cases that cross out of cost-basis are concentrated. In our reading of contingency books we have looked at, between two and three cases per year on a five-case book hit a flag-firing event; the remaining two to three resolve cleanly inside the initial scope and never come close to the threshold. The leak from the flagged cases compounds in two ways: the immediate uncompensated work past the crossing point, and the foregone alternative-matter work the practice could have been doing during the same hours.

The immediate uncompensated work past the crossing point, in the cases we have modeled, runs 80 to 250 hours per affected case, valued at the lawyer's notional billing rate. On a $475 rate, that is $38,000 to $118,750 per affected case in lawyer time alone. The recoverable margin — the share of that uncompensated work that an early-warning conversation could plausibly have prevented — is roughly half: $20,000 to $60,000 per affected case. Portfolio-wide on a five-case book with two crossings, the expected impact runs $40,000 to $120,000 per year. That is the same range the contingency-fee leak post attributes to the broader leak; the discovery-scope-creep flag is responsible for the largest single contribution to it.

The portfolio number compounds further when the second-order effect is included. The hours the lawyer spent past the crossing point on Case A are hours the lawyer was not spending on Case B, on intake screening for Case F, or on the rate paragraph in the next fee-petition affidavit. Each of those is a positive-return alternative use of time that the unflagged path never gets to allocate against. The flag's value is partly in preventing the negative-return work and partly in returning the displaced hours to positive-return alternatives — including the time paid by the eventual fee-shifting award on the cases that do prevail, where the records that pay it are themselves a downstream artifact of the same passive capture.

What this requires

The flag requires three things the practice can build with off-the-shelf tooling and the same passive-capture system that supports fee-petition affidavits and the hourly-leak math. (1) Per-matter hour capture: each unit of captured time tagged to a specific matter, with a sub-tag identifying capture surface (call, email, document, calendar) and case-phase (pleadings, written discovery, document review, depositions, motion practice, expert work, settlement, trial). The metadata-only architecture handles this without surfacing privileged content. (2) An expected-contingent-share working estimate, updated at the case milestones already on the lawyer's calendar (filing, answer, close of fact discovery, dispositive-motion order, mediation outcome). The discipline is the lawyer's; the format is a one-paragraph note in the matter file with the three inputs (fee_pct, E[settlement], P[recovery]) and a one-line rationale for any change. (3) A weekly review pass across the open matter list. The pass takes ten minutes and produces a list of matters whose cost-basis ratio has crossed any of the configured thresholds (0.5, 0.7, 0.9, 1.0). The 0.5 threshold is informational; the 0.7 threshold is a partner-review trigger; the 0.9 threshold is an immediate-action trigger; the 1.0 threshold is a documented continuation decision.

None of this is novel as practice management. Plaintiff's-side firms with active fee-petition practices have, in many forms, been doing variants of this for thirty years. What is new is that a solo who refuses to pay the practice-management tax — the population this blog is for — can now do it without the manual timekeeping that previously made it prohibitive at solo scale. The data exists on the lawyer's devices; the only missing piece was a capture mechanism that would not consume the lawyer's day in entry-by-entry recording. ClaimHour is the capture mechanism. The flag is what comes out of the data.

FAQ

What does it mean for a contingency case to be "out of cost-basis"?

A contingency matter is in cost-basis when the cumulative hours invested, valued at the firm's notional billing rate, are less than the expected contingent share — fee_pct × E[settlement value × probability of recovery], plus any expected statutory fee-shifting award. The matter is out of cost-basis when the inequality flips: the lawyer has already worked more than the eventual contingent share will compensate. Past that line, every additional hour worked is uncompensated unless the eventual recovery exceeds expectations or fee-shifting supplements the contingent share. The line is computed continuously; the practice that does not capture actual hours per case cannot compute it.

What is the discovery-scope-creep flag, exactly?

An internal, firm-side warning signal that fires the first time a configured threshold of expected contingent share is reached on a specific matter. The default threshold is 70%: when cumulative captured hours × notional billing rate reaches 70% of the expected contingent share, the matter is flagged for partner review. The flag does not fire on dollar terms with the client; it fires on the firm's spreadsheet. Its purpose is to surface the conversation about the case's economics while the practice still has options — fee-structure renegotiation, count dropping, early settlement, redirected work — rather than discovering the crossing after the case has resolved at a number below cost basis.

How does this differ from the lodestar fee petition?

The lodestar fee petition is the post-resolution document filed in fee-shifting cases (§ 1988, Title VII, ADA, FCRA, FDCPA, FMLA, ERISA § 502(g)) that asks the court to award statutory attorney's fees on top of the contingent share. The discovery-scope-creep flag is a pre-resolution internal signal evaluated continuously through the life of the case. Both depend on the same underlying input — captured hours per matter — but they consume the data at different points in the case lifecycle and for different purposes. The flag tells the lawyer whether to keep working at all; the petition tells the court what to award once the work has been done and the case has been won.

Doesn't ABA Model Rule 1.5 limit fee renegotiation mid-case?

Model Rule 1.5(a) requires fees to be reasonable and Rule 1.5(c) requires contingency-fee agreements to be in writing, signed by the client, and stating the percentage. Mid-case fee modifications are not categorically prohibited but are subject to substantially higher scrutiny than original engagements: the lawyer must demonstrate the modification is reasonable, the client gave informed consent in writing, the lawyer disclosed the right to seek independent counsel, and the modification is not the product of overreaching. Comments to Rule 1.5 and a body of state-bar ethics opinions counsel that the cleaner path is generally to stop work or withdraw under Rule 1.16 rather than to renegotiate the fee while continuing to represent. The flag fires before that decision; the conversation it triggers may end in withdrawal, in continued representation at the original fee, in dropping a count to focus on the prevailing claim, or in early settlement. The fee modification path exists but is the option of last resort.

What is the dollar impact of the flag, portfolio-wide?

On a typical five-case contingency book, the cases that cross out of cost-basis are concentrated in two or three matters per year, not five. The expected dollar impact of catching those crossings at 70% of expected contingent share rather than at resolution is the avoided uncompensated work past the crossing point — typically 80 to 250 hours per affected case, valued at the notional billing rate. On the affected cases we have modeled, the recoverable margin per case runs $20,000 to $60,000; portfolio-wide on a five-case book with two crossings, the expected impact runs $40,000 to $120,000 per year. That is the same range the contingency-fee leak post estimates for the broader leak, with the discovery-scope-creep flag responsible for the largest single contribution to it.

Does the flag work for small or simple contingency matters?

It works best for matters with non-trivial discovery exposure: plaintiff-side employment, civil rights, FCRA/FDCPA consumer with class allegations, ERISA benefits with administrative-record disputes, products liability with expert-discovery, qui tam, and complex personal injury with significant medical-records discovery. For straightforward auto-PI matters that resolve in pre-litigation demand or at policy limits, the cost-basis crossing rarely happens because total hours invested are bounded. The flag is a non-event for cases that resolve cleanly inside their initial scope; its value is concentrated in the matters where it would otherwise be a surprise.