
Where crash data comes from can matter as much as what it says. The data-lineage questions PI firms and counsel should ask any MVA program.
Most conversations about MVA marketing focus on what happens on the phone: who calls, what they say, and whether consent is captured. Those questions matter. But there is an earlier question that many firms never ask, and it can carry just as much risk: where did the data that started the outreach come from, and was it permitted to be used that way?
That question is about data lineage, the documented chain from an original source to the record your firm receives. For a plaintiff firm, a weak link anywhere in that chain becomes the firm’s problem, not the vendor’s.
Accident information can pass through many hands before it reaches a marketer. Some of it may originate in state motor vehicle records, which are protected by the federal Driver’s Privacy Protection Act and by state law. In Maracich v. Spears, the Supreme Court held that soliciting prospective clients is not a permissible use of motor vehicle record data under the DPPA’s litigation exception. A program that buys accident data and uses it to solicit claimants can expose the firms that rely on it.
The practical lesson is that a firm should know not only what is in a record, but how the record was obtained, what authority the provider had, and which elements were used to find and contact the claimant.
Nexus Crash is built so that each link in the chain can be described and reviewed:
■ Source. Crash report data is obtained through an exclusive arrangement with a law-enforcement-owned data provider.
■ Authority. The provider’s written statutory authority is verified before any record is used.
■ Exclusions at import. Any element that may derive from a state motor vehicle record is excluded at import, and clinical content is stripped.
■ Independent contact data. Outreach address and telephone data are sourced independently of the crash report data.
■ No DPPA permissible-use theory. The program does not rely on a DPPA permissible use at all, and no state motor vehicle record data is used to source, contact, or qualify a claimant.
■ No firm-supplied reports. Nexus does not request records from a governmental entity itself and does not accept report data from a firm.
Contact aimed at a specific firm occurs only after the claimant’s own express request for legal information and consent naming that firm.
A documented lineage is not only a defensive measure. It also makes the program easier to approve and easier to run. When counsel can review the source, the authority, and the exclusions before launch, the firm avoids the stop-and-start that comes from discovering a data problem after deliveries have begun. Partners can approve the program with a clear view of how it works. Intake staff can focus on the claimant rather than wondering whether the contact was appropriate in the first place.
It also helps when someone outside the firm asks questions. If a claimant, opposing counsel, or regulator ever asks how the firm learned of an accident or why the claimant was contacted, the answer can be traced step by step.
Crash report data does more than start the process. Involved-party identity, injury indicators, and liability facts are extracted from it, and commercial-vehicle involvement is flagged with carrier and USDOT detail. During intake, the claimant’s account is cross-checked against the report on file. That gives your firm a matter whose core facts rest on documents rather than self-reporting, and an incident summary based on crash report data travels with every delivery.
Before your firm relies on any program that uses accident data, consider asking for written answers to the following:
■ Who is the original source of the accident data, and what authority does that source have to provide it?
■ Is the provider’s authority verified in writing before records are used?
■ Does any element of the record derive from a state motor vehicle record, and if so, how is it handled?
■ Where does the address and telephone data used for outreach come from?
■ Does the program rely on a DPPA permissible use, and if so, which one?
■ When, and how, is my firm first identified to the claimant?
A vendor that cannot answer these questions clearly is asking your firm to take its word for it. A program built around documented lineage should be able to answer every one.
Data lineage does not replace state-by-state review. Report access, post-accident waiting periods, and permitted contact channels vary by state, and Nexus Crash campaigns are set up by crash state. Nexus welcomes your counsel confirming the analysis for each jurisdiction before launch, and makes the outreach scripts, consent artifacts, and state scoping available for that review.
Nexus Crash connects your firm with recent, record-verified MVA claimants who asked for legal help. Take them as a live call to your intake team, or as a complete file with your engagement documents already signed. Funding is also available for firms that qualify, and we can connect you with our funding source: nexuslegal.group/programs/attorney-funding. To see how it would work in your state, book a 20-minute call at calendly.com/nexuslegalgroup, call 855-925-1035, or email team@nexuslegal.group.
Program availability and outreach methods depend on source terms, jurisdiction-specific review, and approved scope. Nonprofit participation is not a blanket compliance exemption. Nexus is not a law firm and does not provide legal advice. This article is general information for law firms and is not legal advice.