Representative & mass litigation · 10 Editorial guide
Representative & mass litigation
Representative actions and multi-claimant civil/securities proceedings.
First job Identify claimant class, common issue and procedural mechanism before aggregation.
Start here
Key considerations
The first questions are about urgency, governance and preservation — before collection expands or interviews begin.
- Scope — Representative actions and multi-claimant civil/securities proceedings.
- Immediate task — Identify claimant class, common issue and procedural mechanism before aggregation.
- Boundary — If another practice owns a distinct issue, use Related topics below rather than duplicating that analysis here.
Direct answer
What this page decides
02
A multi-claimant matter needs a controlled claimant record before procedural aggregation can be evaluated. Identify the common event and legal questions, but keep each claimant's identity, authority, exposure, loss, evidence and deadlines separate. Common issues do not eliminate individual proof. Intake, communications, privacy, funding and settlement allocation also need governance. This page organises the file and the questions for counsel; it does not determine whether a representative, joint, coordinated or test-case mechanism is available.
At a glance
Which fact changes the next route
Use the fact that changes ownership or urgency to decide the next move.
| Question | Why it matters | Next route |
|---|---|---|
| What is genuinely common? | Shared conduct may coexist with different causation, loss and defences. | Create separate common-issue and individual-issue lists. |
| Who is authorised to act? | Identity, consent and representation cannot be inferred from group membership. | Record each claimant and authority document. |
| Are deadlines uniform? | Events, knowledge and prior steps may differ by claimant. | Maintain claimant-level dates and procedural status. |
| Can the dataset be audited? | Inconsistent intake undermines proof, notices and settlement allocation. | Use one evidence schema while preserving original documents. |
Scope
What this page owns — and what it does not
Practical workflow
Action, evidence, legal gate, output
| Action | Documents / evidence | Legal gate | Output |
|---|---|---|---|
| Define the common event | Product, transaction, disclosure, incident or conduct records | Separate shared facts from claimant-specific facts | Common-issue matrix |
| Control claimant intake | Identity, authority, contact, chronology and source evidence | Verify consent, duplicates and data handling | Claimant register |
| Test procedural options | Forum status, claimant differences, related cases and deadline data | Obtain advice on the available mechanism | Procedure decision brief |
| Govern communications and resolution | Notices, updates, funding terms and allocation method | Keep messages accurate and claimant records current | Communication and resolution protocol |
Documents
What to gather before the next call
These items help clarify the file; they are not a legal requirement list.
| Item | Why needed | Who holds it | Risk if missing |
|---|---|---|---|
| Verified claimant register | Links identity, authority, dates and evidence | Claimants and case team | Duplicates or unauthorised instructions distort the group |
| Common and individual issue matrix | Shows what may be managed together | Case team and experts | Individual proof is hidden by the group narrative |
| Source evidence inventory | Preserves originals and provenance | Each claimant and common custodians | The dataset cannot support pleaded facts |
| Communication and consent log | Records notices, choices and current authority | Case team | Claimants receive inconsistent information |
Common failure points
Where files usually break
Counting expressions of interest as verified claimants.
Using one narrative for everyone without preserving claimant-specific causation and loss.
Allowing spreadsheets, communications and evidence folders to diverge without version control.
Decision map
Keep the question bounded.
- Define the claimant group and common eventIdentify who is affected, the shared conduct or product, common legal questions and individual differences in causation, loss and limitation periods.
- Build a controlled claimant datasetUse consistent intake, consent and evidence protocols to record identity, exposure, injury, transactions and deadlines without obscuring individual proof.
- Choose aggregation and case managementAssess representative, joint, coordinated or test-case procedures and plan notice, funding, expert evidence, settlement allocation and claimant communications.
Curated resources
Open the asset that matches this job.
Helpful to prepare
Facts that make the next conversation clearer.
These items are orientation aids, not a legal requirement list.
Counsel hand-off
What to bring when you instruct
Bring the common-event summary, claimant register, authority records, issue matrix, evidence inventory, deadline data, related-proceeding information and proposed communication or funding arrangements.
Local context
Add the forum city only when procedure changes.
Add city or province context only when the responsible authority, court, registration practice, permit process or local implementation changes after the national route is identified.
Open city and province guidesCounsel hand-off
Need disputes counsel?
This hub maps proceeding stage, evidence and forum. It does not decide claims, strategy or outcome on your facts.
Find disputes counselLegal review
Who reviewed this guide
Subject to editorial/legal review. No reviewer is assigned to this route.
Need qualified counsel?
Move carefully. Move with a record.
Use the portal to identify counsel for this practice and related China-side issues.