
Mass tort intake
Mass Tort Intake vs. Personal Injury Intake: Operational Differences
A practical comparison of the data structures and controls that distinguish campaign-based mass tort intake from personal injury intake.
The main difference between mass tort and personal injury intake is the coordination unit. Personal injury intake usually structures one prospective client's event, injuries, parties, deadlines, and evidence for individual review. Mass tort intake must do that same person-level work while also applying a shared, versioned campaign model across many inquiries. The campaign adds common criteria, recurring evidence requests, duplicate pressure, and exception queues. It does not replace individual facts or authorized legal review.
Mass tort vs. personal injury intake at a glance
Neither intake model is inherently simple or low volume. A personal injury practice may receive many inquiries, and a mass tort campaign may begin with a small cohort. The operational distinction is whether the firm must coordinate a common campaign definition across many separate claimant records.
| Operating dimension | Personal injury intake | Mass tort intake |
|---|---|---|
| Primary control record | Case-type configuration plus one prospective-client record | Versioned campaign record plus one record for each prospective claimant |
| Question design | Event-specific branching based on the incident and parties | Shared campaign questions with claimant-specific branches and exceptions |
| Evidence pattern | Records tied to a particular event, treatment history, parties, and claimed loss | Repeated evidence categories for product, exposure, use, treatment, diagnosis, or other firm-approved criteria |
| Change management | Updates can affect a case type or an individual file | A change may affect every open intake under a named campaign version |
| Duplicate pressure | Repeat contacts, referrals, household details, and channel changes | The same risks plus repeated campaign acquisition across sources and partner lists |
| Exception handling | Matter-specific follow-up and escalation | Reusable exception classes with campaign-level queues and individual resolution |
| Review boundary | Authorized review of the individual matter | Authorized review of each person, informed by campaign rules but never replaced by them |
| Handoff | One accepted intake becomes or feeds one matter record | Each accepted claimant record feeds its own matter while retaining the campaign and criteria history |
The campaign record is the defining extra layer
A general legal intake system needs a case-type definition. It identifies the questions, required parties, evidence requests, statuses, and review paths that apply to a kind of matter. A mass tort intake program needs an additional campaign record that is narrower and more actively governed.
That campaign record should identify the approved criteria version, effective dates, question set, evidence plan, exception rules, consent language, owner, approver, and change history. Each claimant record should point to the version actually used. If the firm changes a date range, product identifier, injury category, or required document, the system should not silently apply the new rule to an earlier interview.
Personal injury intake also needs version control. Forms, case-type rules, and notices change there too. The difference is the blast radius. In a campaign, one revision can affect a large set of open records that were collected through the same operating model. The team needs to know which records require no action, which need a new question, and which should enter an authorized re-review queue.
External requirements can also change. The Judicial Panel on Multidistrict Litigation publishes its governing statutes, current Panel Rules, and filing material. An intake team should not translate a court rule into intake logic on its own. Firm lawyers or other authorized staff determine whether a change affects the campaign, then approve the corresponding workflow version.
Shared questions still need individual answer states
Mass tort intake often repeats the same core questions across a campaign. Repetition makes precise answer states more important, not less important. Unknown, not remembered, not asked, declined, and no should not collapse into an empty field when they lead to different follow-up work.
An unanswered field says the workflow does not yet have a response. An unknown answer says the question was presented and the person could not supply the fact at that time. That difference can determine whether the next action is a reminder, a records request, a source check, or authorized review of an exception.
Personal injury intake benefits from the same distinction. The difference is that a mass tort team must use the states consistently across a repeated campaign. Otherwise, aggregate queue counts and file-readiness reports mix missing work with facts the claimant cannot presently provide.
Conditional logic should remain tied to the approved case type or campaign. A response about product use may open date, location, provider, or evidence questions in one campaign. An incident answer in a personal injury workflow may open vehicle, property, employer, witness, or treatment branches. Those branches structure collection. They do not determine liability, causation, representation, or case value.
Evidence repeats by category but remains person-specific
The Federal Judicial Center's products-liability MDL guide describes discovery as having two dimensions, one concerning defendants' conduct and another concerning each plaintiff's conduct, causation, and injuries. It also discusses standard plaintiff fact sheets used to collect information relevant to settlement and trial. The FJC guide is about judicial case management, not law-firm intake design. Still, it illustrates the operational tension clearly. Common structure can organize recurring questions, but it does not erase the individual record.
For mass tort intake, an evidence plan can define recurring categories and acceptable source types. Each received item still needs a claimant link, source, received date, document type, extraction status, correction history, and access control. A document that supports one person's timeline cannot be treated as support for another person's facts.
Personal injury evidence tends to follow the event and its consequences. The actual categories depend on the matter and the firm's approved procedure. Mass tort evidence often repeats around a shared product, exposure, use, procedure, treatment, or diagnosis theory, but the claimant's dates, providers, records, and gaps remain distinct.
Medical-record collection also needs an approved process. HHS explains that the HIPAA right of access covers protected health information in designated record sets and that covered entities may verify the identity of a requester without imposing unreasonable barriers. Its right-of-access guidance also distinguishes an individual's access request from a HIPAA authorization. Firm counsel should determine which method, notices, permissions, and safeguards apply. The intake system should preserve the chosen request or authorization, its scope, its status, and the records received.
Volume changes the duplicate and exception design
Duplicate control is not unique to mass torts. Any plaintiff firm may receive a web submission after a phone call or two referrals for the same person. Mass tort campaigns add more repeated routes into the same intake, including campaign pages, calls, referrals, imports, and resumed interviews.
A duplicate check should produce candidates, not an automatic identity decision. Names, phone numbers, email addresses, birth dates, addresses, source identifiers, and campaign history can support comparison. Shared contact information and minor spelling differences can also create false matches. A named reviewer should decide whether to merge, link, or preserve separate records, and the system should retain the original source values.
Exception handling must scale in the same way. A personal injury intake team may resolve an unusual date, party, or document issue inside one file. A mass tort team needs named exception classes so recurring problems do not disappear into notes. Useful operational classes include conflicting dates, product uncertainty, incomplete provider history, unreadable evidence, possible duplicate, expired permission, and criteria-version mismatch.
The queue should identify the record, exception type, source, owner, age, and permitted resolution. It should not label the claimant legally qualified or unqualified. That judgment remains with a lawyer or authorized firm reviewer under the firm's approved process.
Common proceedings do not turn claimants into one matter
Title 28, section 1407 permits civil actions with common factual questions in different federal districts to be transferred for coordinated or consolidated pretrial proceedings. The statute also addresses remand of transferred actions. This federal MDL framework does not mean every mass tort campaign will enter an MDL, and an intake platform should not predict that outcome.
The useful operational lesson is narrower. Shared questions can justify shared structure, yet each prospective claimant still needs a separate identity, facts, sources, conflicts state, communications, permissions, evidence, review history, and matter disposition. Campaign membership is a relationship on the person-level record. It is not a substitute for that record.
At handoff, a personal injury intake should pass the approved facts, parties, evidence, open gaps, communications, and review history into the matter system. A mass tort handoff should pass the same individual record plus the campaign ID, criteria version, campaign exceptions, and any authorized review result. Neither handoff should require staff to retype a narrative into a disconnected case file.
Human review has the same boundary in both models
The intake system may validate formats, classify documents, identify missing items, compare possible duplicates, and show how a record maps to firm-approved criteria. It should not make legal, conflict, engagement, or representation decisions.
This boundary starts at first contact. The comment to ABA Model Rule 1.18 notes that an invited submission can create a consultation depending on the circumstances. It also says a lawyer considering a matter should limit the initial consultation to information that reasonably appears necessary for deciding whether to undertake it. Applicable duties vary by jurisdiction and circumstance. The firm's lawyers should approve the notices, collection stages, conflict procedure, review roles, and engagement boundary for both intake models.
Operational automation is most useful before that decision. It can give the reviewer a file that exposes sources, discrepancies, unknowns, unanswered questions, criteria versions, and evidence gaps. The reviewer then applies professional judgment under firm policy.
Choose the model by asking what must stay consistent
Before configuring either workflow, the team should answer five questions:
- Which rules belong to the general case type, and which belong to a named campaign?
- Which changes require versioning, follow-up, or re-review of open records?
- Which evidence categories repeat, and which facts must remain claimant-specific?
- Who may resolve duplicates and operational exceptions, and who may make legal or engagement decisions?
- What exact record must move into case management after acceptance?
Mass tort intake is not a larger copy of personal injury intake. It is individual intake operating inside an additional campaign control layer. The right architecture preserves both levels so the firm can coordinate repeated work without flattening the person, the evidence, or the judgment each file requires.
Start with one case type