What Is Lead Triage — And Why It Matters for PI Marketing Performance

Lead triage is one of those terms that means different things to different firms. Some use it to describe the initial screening call. Others use it to describe the attorney review before signing. A few use it interchangeably with “qualification.”

For the purposes of marketing performance, lead triage has a precise meaning: the structured process of evaluating an incoming lead and routing it to the appropriate outcome — signed, rejected, referred out, or pending — in a way that captures enough data to evaluate the source that sent it.

That last clause is the part most firms skip. They triage for intake efficiency. They don't triage for marketing intelligence. And as a result, they spend $200K a month on lead generation and have almost no reliable data about which vendors are actually producing cases worth taking.

The Difference Between Triage for Intake and Triage for Marketing

Intake triage is designed to answer one question: should we take this case? Marketing triage is designed to answer a different question: should we keep buying from the source that sent this lead?

In practice, the same conversation produces the data for both — but only if someone on the intake team is capturing the right information in a structured way.

Consider what happens during a typical intake screening call. The specialist asks about the accident date, the type of injury, whether the prospective client has retained another attorney, and whether there is a plausible liability theory. Based on those answers, they either move forward or decline.

From an intake efficiency standpoint, the outcome is binary: yes or no. From a marketing intelligence standpoint, the call produces a data point that belongs in a larger dataset — one that tells you whether Vendor A's leads are predominantly within your case criteria, or whether 55% of them are accidents that happened 3 years ago with no documented injuries.

The difference is whether you are capturing a structured reason for the outcome, and whether that reason is tagged to the lead source.

Why Lead Triage Quality Directly Affects Your Marketing Decisions

Marketing directors at PI firms often talk about “lead quality” as though it is a fixed characteristic of a vendor — something you either accept or don't. In reality, lead quality is a measurement problem before it is a vendor problem. If you're not triaging in a way that generates reliable, source-attributed rejection data, you can't actually measure lead quality. You can only guess at it.

Here's why this matters at scale. A firm spending $500K a month across eight vendors is getting roughly 1,500–3,000 leads per month, depending on average cost per lead. If intake is rejecting 40% of those leads — a realistic number for many aggregator-heavy portfolios — that's 600–1,200 rejected leads per month. Each of those rejections is a data point. Together, they tell you:

• Which vendors have rejection rates above your acceptable threshold
• What the most common reasons for rejection are by vendor
• Whether rejection rates are improving or declining over time for a given vendor
• How your rejection rate correlates with lead cost — sometimes the cheapest leads have the highest rejection rates, producing a misleadingly low cost-per-lead number

None of this intelligence is available if triage is informal. If intake specialists are just declining leads without tagging a reason, or if reason codes exist but aren't vendor-attributed, you're producing noise instead of signal.

Building a Lead Triage System That Generates Marketing Intelligence

The structure of a marketing-grade triage system has four components.

Standardized Outcome Categories

Every lead should resolve to one of a small number of standardized outcomes: signed, rejected, referred out, or follow-up pending. Some firms add a fifth category for leads that become unresponsive after initial contact — a “lost to non-response” designation that is diagnostically different from a rejection. The exact categories matter less than their consistency. If intake specialists are categorizing outcomes differently depending on who handles the call, your data is not comparable.

Structured Rejection Reason Codes

Rejection reason codes should be specific enough to be actionable. A useful taxonomy might include:

• Statute of limitations expired
• Liability unclear or disputed
• Case type outside firm criteria (e.g., property damage only, no injury)
• Prior representation (client already has an attorney)
• Client unresponsive after initial contact
• Injury severity below case threshold
• Geographic jurisdiction not covered

Generic codes like “not qualified” or “bad lead” are not useful. They collapse five or six distinct problems into one bucket that tells you nothing about which vendors to address or how.

Mandatory Source Attribution

The triage outcome and reason code need to be linked to the lead source at the record level — not just filed in a case management system where the source is a free-text field that gets inconsistently populated. Preferably, the source tag is captured at the point of lead entry (via CRM integration with the vendor or ad platform) so that intake specialists don't have to ask where the lead came from and don't have to remember to fill it in.

Regular Review Cadence

Triage data has a short shelf life. A rejection rate spike from a new vendor should be visible within 2–3 weeks, not at the end of the quarter. Building a monthly lead quality review — or ideally a bi-weekly one for high-spend periods — ensures that triage data is actually informing vendor decisions rather than sitting in a database that nobody reads.

Common Triage Failures and What They Cost You

Most of the triage failures we see at PI firms fall into one of three patterns.

The first is inconsistency. Different intake specialists follow different processes. Some use a script; some improvise. Some log rejection reasons; some don't. The result is a dataset that looks like it has information but is too inconsistent to draw conclusions from.

The second is misattribution. Leads come in through multiple channels — direct calls, web forms, live transfers — and the intake system doesn't reliably link them to the originating vendor. A lead from a television campaign that calls in on the firm's main number gets logged as “inbound call” with no vendor attribution. The television spend never gets credit for the case, and the data is structurally incomplete.

The third is delay. Triage data is captured in case management, but the marketing team doesn't have access to it — or has to request a report that takes a week to generate. By the time the data is reviewed, it's two months old and the vendor has already sent another 400 leads.

Each of these failures has a direct cost. Inconsistency means you can't confidently evaluate vendors. Misattribution means your cost-per-case numbers are wrong. Delay means you're overspending on bad vendors for longer than you should.

Lead Triage as a Feedback Loop

The highest-value use of lead triage data is not internal — it's external. When you can share structured rejection data with your vendors, you create a feedback loop that most vendors have never experienced.

Telling an aggregator “34% of your leads last month had statute of limitations issues” is a different conversation than telling them “your lead quality has been poor.” The first gives them something specific to fix. The second starts an argument.

Vendors who receive structured rejection feedback tend to improve over time — not out of goodwill, but because their business model depends on clients who keep buying. If you can show that your rejection-based feedback is reliable, a good vendor will use it to tighten their targeting. A vendor who ignores it or disputes it repeatedly is telling you something important about the relationship.

Lead triage, done well, is not just an intake efficiency tool. It is a marketing intelligence system that pays for itself every time it saves you from renewing a contract with a vendor who was quietly failing for six months before anyone had the data to say so.