Personal Injury · Guide · Published Aug 28, 2026

Contingency Cash-Flow Ops: Task Cadences When Revenue Is Lumpy

Contingency practice has a rhythm every PI owner knows in their stomach: long dry stretches of work with no revenue, then several cases settle at once and the account swings the other way. You cannot make cases settle on a schedule, so the lumpiness itself is not going away. But operations control two things that make it far more manageable: how visible the lumpiness is in advance, and how fast revenue is realized once a case resolves. This is a guide to the operational levers, not financial advice, which is the owner's domain and their accountant's.

Contingency revenue is lumpy because payment arrives only when cases resolve, on timelines the firm cannot fully control. Operations cannot make settlements arrive on schedule, but they can make revenue more predictable and faster to realize. Three operational levers do most of the work: pipeline visibility turns surprise into forecast so lean stretches are seen coming; disbursement velocity shortens the gap between a case settling and revenue being realized; and steady case progression keeps cases moving to resolution rather than stalling in bunches, so settlements arrive more regularly. This is operations, task cadences and visibility, not financial, accounting, or tax advice, which are the owner's and their accountant's. Each system supplements, never replaces, the firm's own processes and financial decisions.

The feast-and-famine cash rhythm is treated by most PI owners as an unavoidable fact of contingency life, and half of that belief is correct: you genuinely cannot make a case settle on a date you choose. But the belief hides an important distinction. Lumpy revenue has two separate problems: the surprise of it, not knowing a lean stretch is coming until you are in it, and the lag of it, money you have earned sitting unrealized because settled cases are slow to pay out. Neither of those is actually about the timing of settlements, and both are squarely operational. A firm that sees its lumpiness coming and realizes its revenue fast experiences the same underlying settlement pattern very differently from a firm that is repeatedly surprised and slow, even though neither controls when cases settle. This guide is about those operational levers, kept strictly to operations, because the financial decisions that sit on top of the revenue picture belong to the owner and a qualified accountant, not to us.

The nature of the lumpiness

It is worth being precise about what operations can and cannot touch, because overclaiming here would be both wrong and irresponsible. Operations cannot change the fundamental fact that contingency revenue arrives when cases resolve, and cases resolve on timelines shaped by medical treatment, opposing parties, courts, and negotiation, most of which the firm does not control. So the lumpiness in principle is not going away, and any promise to smooth it into a steady salary-like flow would be false. What operations can genuinely affect is narrower but powerful: the visibility of the pattern before it happens, the speed at which earned revenue is realized, and the regularity with which cases reach resolution over time. Those three do not eliminate lumpiness; they make it predictable, fast-realized, and less bunched, which is most of what a firm actually needs to plan and operate calmly. Holding that distinction honestly is what keeps this operations and not a financial promise.

Lever 1: pipeline visibility

The first lever addresses the surprise problem: a firm that can see its pipeline can forecast its revenue rhythm instead of being ambushed by it. When the firm knows how many cases are in treatment, how many are in demand or negotiation, and how many are near resolution, it has a rough forward picture of when revenue is and is not likely to arrive, which turns a lean stretch from a shock into an anticipated season the firm can plan around. This is not financial forecasting in the accounting sense; it is operational pipeline visibility, reading the shape of the caseload from the same pipeline metadata the firm already tracks, described in the PI KPIs guide. The owner and their accountant do the financial planning; operations simply make the pipeline visible enough that the planning has something to work with. A firm that watches its pipeline is rarely surprised by its own cash rhythm, and being unsurprised is half the battle with lumpy revenue.

Lever 2: disbursement velocity

The second lever addresses the lag problem, and it is often the highest-leverage of the three: a settled case that has not yet paid out is revenue the firm has earned but not realized, and shortening the gap between settlement and realization directly improves the cash picture without any case settling faster. Settled cases commonly stall in the lien-and-disbursement phase, liens to resolve, statements to prepare, approvals to obtain, and every week they sit is a week of earned money not realized, as detailed in the lien and disbursement guide. Running that phase as a tracked cadence, so liens are chased persistently and disbursement moves in order, pulls realized revenue forward, which for a firm with several settled-but-unpaid cases can be a meaningful and fast improvement. This is purely operational, it is about the speed of a task cadence, not about the money itself, which the firm handles in its own compliant trust accounting, and it happens to be the lever a firm can most directly control, because it depends on the firm's own follow-through rather than on outside parties settling.

Lever 3: steady progression

The third lever addresses the bunching problem over the longer term: cases that move steadily through the pipeline reach resolution more regularly than cases that stall and then clear in clumps. When intake is fast and cases progress without long stalls, on records, on follow-up, on the operational steps that keep a matter moving, the flow of cases reaching resolution smooths out somewhat over time, simply because a steadily-moving pipeline produces more regular outputs than a stop-start one. This does not override the inherent unpredictability of any single case, but across a caseload it reduces the extreme bunching that comes from many cases stalling and then all clearing at once. The relevant operations are the ones that keep cases moving: fast intake as in the intake speed guide, unstalled records and progression, and prompt handling at each stage, all of which serve the case and the client first and happen to regularize the revenue rhythm as a byproduct.

Put the three together and the underlying settlement pattern, which you never controlled, is experienced completely differently: the pipeline is visible so lean stretches are anticipated, earned revenue is realized fast so less money sits in limbo, and cases resolve more regularly so the swings are less violent. None of that is a financial strategy or a promise about the firm's finances; it is operations, the visibility and task cadences that shape the timing of revenue, and the financial decisions that sit on top, budgeting, reserves, financing, distributions, belong entirely to the owner and a qualified accountant. What operations offer is a clearer, faster, more regular revenue picture for those decisions to work from, which connects to the whole-firm view in the settlement phase and the numbers in the KPIs guide. That is the honest and useful role of ops in a lumpy-revenue practice: not to defy the nature of contingency work, but to take the manageable parts and manage them well.

Where to go next

• PI Firm KPIs

  The pipeline visibility numbers.

• Lien & Disbursement Cadences

  The disbursement-velocity lever.

• PI Intake Speed

  Keeping the pipeline moving.

• Settlement Communication

  The client side of the resolution phase.

Frequently asked questions