When to Refer Out a Personal Injury Case — A Decision Framework
Knowing when to refer is a profitability lever most plaintiff firms underuse. Here's a framework for deciding which cases to keep, which to refer, and how to do it without leaving money on the table.
By Valryn Team
Most plaintiff firm owners think about case selection in two categories: cases worth signing and cases worth declining. The third category — cases worth referring — is where many firms quietly leave money on the table.
A well-run referral pipeline can be one of the most profitable activities in a personal injury practice. Done well, you get a meaningful percentage of fees on cases you couldn't profitably handle yourself. Done poorly, you decline cases that should have been referred and refer cases that should have been kept.
Here's a decision framework.
Three reasons to refer
A case should be referred (not declined, not kept) when one of these is true:
1. Outside your practice area. Your firm focuses on auto and slip-and-fall; the case is medical malpractice. Refer to a med-mal specialist who handles those cases all day. The referral fee on a strong med-mal case dwarfs what your firm could have made attempting it.
2. Outside your geographic capacity. The case is in a state where you're not licensed, or the venue is too far for your team to litigate effectively. Refer to a firm based locally that knows the venue, the judges, and the defense bar.
3. Beyond your firm's litigation depth. You're a fast-moving settlement firm; the case is going to require serious discovery, expert witnesses, motions practice, and possibly trial. A trial-ready firm will get a better outcome than your settlement-focused team would, and the referral fee is more than what you'd net after the litigation costs you'd absorb.
Three reasons NOT to refer
Equally important — when to keep:
1. The case is in your sweet spot. You handle this case type in this venue every week. Your team will produce as good or better an outcome than any referral target. Keep it; you're the right firm.
2. The case is small enough that referral overhead doesn't pay. Below a certain case-value threshold (usually $25K–$50K), the percentage you'd get on a referral fee doesn't justify the work of vetting and managing the referral. Either handle it yourself or decline it.
3. The case has marketing value beyond fees. A high-profile case in your local market — even one outside your usual practice — may be worth keeping for the brand visibility, attorney experience, or relationship development.
The intake-stage decision
The hardest part of referrals is making the decision early. Cases that get worked for two months before the firm realizes they should have been referred have already cost more in time than the referral fee will ever recover.
The right time to decide is at intake. That means intake teams need to know:
- Which case types your firm refers out — and to whom (specialist firms with reciprocal relationships)
- The geographic boundary — venues you handle vs venues you refer
- The litigation-depth threshold — facts that signal "this will go to trial" vs "this will settle in mediation"
- The minimum case value for referral — below which you decline rather than refer
If your intake team has to ask a partner about every potential referral, the decision happens too late.
Building the referral relationship
Strong referral pipelines aren't built by sending cases over the transom. They're built by:
Reciprocity. Referrals flow both ways. Firms refer to firms that refer back. Build a small set of trusted relationships rather than scatter-shot referrals.
Quality control. Don't refer junk. The fastest way to kill a referral relationship is to send weak cases that the receiving firm has to decline or work hard for nothing. Refer cases that are genuinely good for the receiving firm's practice.
Clean handoff. A referral is only as valuable as the case file it comes with. Send well-organized facts, contact info, medical records (if obtained), and a clear summary of why you're referring. Saves the receiving firm a week of intake work and signals you're worth referring back to.
Documented agreements. Fee splits, conflict checks, and client consent should all be documented before the case moves. Verbal "we'll work it out" arrangements create disputes later.
A simple at-intake decision tree
Run every signed lead through these questions in order:
- Is the case viable? (liability, damages, SOL, defendant capacity) — No → decline
- Is this a case type we handle? — No → refer to specialist
- Is this within our geographic capacity? — No → refer to local firm
- Will this require litigation depth we don't have? — Yes → refer to trial-ready firm
- Is the case value above our minimum? — No → decline (don't refer; not worth the overhead)
- Otherwise — keep, sign, work
The framework should run in 60 seconds at intake. Tools that systematize it — that load case type, jurisdiction, and damage range automatically and return a recommendation — make the decision faster and more consistent across the team.
How Valryn handles it
Valryn's case scoring engine outputs both a tier (qualified / follow-up / review / rejected) and recommended actions. Cases that score well but fall outside your firm's capacity get flagged for referral. The system tracks referral outcomes so over time, you see which referral relationships are productive and which aren't.
Live Attorney Connect and intake scripts can include explicit referral handling — when the AI determines a case is outside your capacity but worth pursuing, it can route to the referral workflow rather than the live attorney transfer.
See how case intelligence works → SOL Guard for cases you refer out → — the SOL doesn't pause when you refer; tracking continues until the receiving firm accepts and confirms.
The bottom line
A small, profitable referral pipeline beats a large pile of declined cases. Most plaintiff firms could meaningfully increase profitability by being more thoughtful about which cases to refer, who to refer them to, and how to make the decision at intake instead of three months in.
See Valryn in your intake flow
Book a demo and we'll walk through the frameworks from this post using sample data from your practice area.
Request Demo