Managing Motor Accident Claims (MACT) Cases at Scale

Use Case · Litigation Management

Updated for 2026 · Claw Editorial

A single road accident can turn into five, ten, or more separate Motor Accident Claims Tribunal (MACT) petitions, filed by different claimants, in different tribunals, on different timelines. For an insurer’s legal team or a law firm handling a panel of MACT matters, the real difficulty is not any one case. It is keeping track of hundreds of them at once, without missing a hearing, a written statement deadline, or a connected claim that should be defended together. This guide looks at why MACT case management gets hard at volume, and what a workflow built for that volume actually needs to do.

01Why MACT cases are hard to manage at scale

A Motor Accident Claims Tribunal case, on paper, looks like a simple compensation claim. In practice, at any real volume, three things make it hard to manage.

One accident, many claim petitions

A single accident involving injury or death can lead to claim petitions from the injured person, the family of a deceased victim, and sometimes multiple victims in the same vehicle. Each claimant can file a separate petition, sometimes in the same tribunal and sometimes in different ones depending on where they reside or where the cause of action arose. For an insurer or a panel firm defending these matters, that means one road accident can quietly become a cluster of five, ten, or more open files, each with its own number, its own hearing dates, and its own paperwork.

The volume compounds fast

Insurers and their panel counsel are not handling one accident. They are handling every accident reported against every policy, every month, across every district where they have exposure. At scale, this becomes hundreds or thousands of open MACT matters running in parallel, each moving at its own pace through tribunals that are often already backlogged.

Missing one thing is expensive

A missed hearing date, a written statement filed late, or a claim petition that goes unanswered can result in an ex-parte award against the insurer, a default judgment, or a compensation figure that is harder to contest later. Because MACT awards involve real money paid to accident victims and their families, the cost of losing track of a single matter is rarely small.

02What a strong MACT case management workflow looks like

Whether it is run on spreadsheets, a case tracking tool, or a mix of both, a workflow built for MACT volume needs to do four things well.

• Track every hearing, automatically: the workflow should surface the next hearing date and cause list entry for every open file, without someone manually checking each tribunal.
• Group connected claims: claims arising from the same accident should be visible together, so the same set of facts, evidence, and defence strategy is not duplicated or contradicted across files.
• Flag deadlines from court orders: a written statement due date, an evidence date, or a direction to file documents needs to become a reminder the moment the order is passed, not days later when someone reads the order sheet.
• Report on the whole book, not just one file: for an insurer or a firm managing a panel, leadership needs a view of exposure, pending awards, and upcoming hearings across the entire portfolio, not just case by case.

At MACT volume, the real risk is never one difficult case. It is one ordinary case that nobody was watching.

03The MACT claim lifecycle, stage by stage

Most MACT matters move through the same broad stages, constituted under the Motor Vehicles Act, 1988. Knowing where a claim can stall helps explain why tracking matters so much at each step.

Filing and tribunal allocation

After an accident, a claim petition is filed before the tribunal with jurisdiction, typically where the accident occurred, where the claimant resides, or where the respondent resides or carries on business. The insurer, the vehicle owner, and sometimes the driver are made parties. At this stage, the key task is simply catching the filing early and confirming which tribunal and case number apply.

Written statement and issues

The insurer or its counsel must file a written statement contesting liability, quantum, or both, within the time the tribunal allows. This is one of the most common points where matters go wrong at scale: the deadline is short, and if the volume of incoming claims is not tracked centrally, a written statement can simply be missed.

Evidence and hearings

Both sides lead evidence, examine witnesses, and the matter proceeds through a series of hearings that can stretch over months or years, depending on the tribunal’s backlog. Each hearing needs to be tracked, because tribunals do not always send a formal reminder, and cause lists change.

Award and compensation

The tribunal passes an award, deciding liability and the compensation amount. Compensation in MACT matters is calculated using an established structured approach that accounts for the claimant’s age, income, and dependents.

Appeal to the High Court

Either party can appeal the award to the jurisdictional High Court, which adds another matter, another court, and another set of dates to track, often years after the original accident.

04Tracking claims by CNR and party name

Once a claim petition is filed, it gets a Case Number Record (CNR) number, a unique identifier that stays with the case across every hearing and every court system update. For a legal team handling many MACT matters, tracking by CNR number and by party name is the most reliable way to keep tabs on a claim, because case numbers and bench allocations can change, but the CNR generally does not.

The same tracking approach used across other case types in India applies here. If your team already tracks matters this way for other litigation, such as cheque bounce cases under Section 138, the method is the same: search by CNR when you have it, and fall back to party name when you only know who is involved. See our guide on tracking cases by CNR and party name for the mechanics.

For MACT specifically, party-name tracking matters more than usual, because a single insurer or vehicle owner can be a respondent in dozens of separate petitions arising from unrelated accidents. Being able to pull up every open matter against a given party, across tribunals, is often the only practical way to know the true size of an open book.

05Finding connected and related claims

Because one accident can generate multiple claim petitions, from different injured persons or different family members of a deceased victim, a claim rarely exists in isolation. If these connected claims are not identified early, a team can end up filing inconsistent written statements, missing that one tribunal’s findings on liability may affect another, or duplicating investigation work that could have been done once.

Finding related or connected cases, whether they share an accident, a vehicle, a policy, or a set of parties, is a distinct skill from simply tracking a single matter. Our guide on how to find related or connected cases covers the general approach, which applies directly to grouping MACT claims that arise from the same incident.

06Managing volume: alerts, compliance, and reporting

Beyond tracking individual claims, teams handling MACT matters at scale need three things working together.

• Timely alerts: a hearing date change, a fresh order, or a new cause list entry needs to reach the responsible lawyer or paralegal quickly, ideally without anyone having to check each tribunal’s portal by hand.
• Reading and acting on court orders: many delays and defaults happen not because a hearing was missed, but because an order asking for a document or a written statement within a set number of days was not converted into a reminder in time.
• Portfolio-level reporting: insurers and firms managing a large MACT docket need a management view, how many matters are pending, how many hearings are due this week, and where exposure is concentrated, not just a file-by-file view.

Increasingly, Indian legal teams are also using AI to lighten this load, from summarising orders to drafting routine filings. For a broader look at how AI fits into day-to-day litigation work, see how Indian lawyers use AI in 2026.

07How to choose an approach

The right setup depends mostly on volume.

If you handle a handful of MACT matters, a well-kept spreadsheet with hearing dates and a manual court-portal check may still work, though it leaves little margin for error. If you handle dozens to hundreds of matters, as most insurers and panel firms do, a system that tracks hearings automatically, groups connected claims, and alerts on new orders stops being a convenience and becomes a risk-management necessity. If MACT is one part of a wider insurance litigation book, alongside other claim types, it is worth evaluating case management as a category rather than a one-off tool. Our guide to insurance litigation management software in India compares the options built for that broader need.

08Where Claw fits

Claw is an all-in-one legaltech platform for Indian advocates, law firms, and corporate legal teams, combining AI-based case search, an AI legal assistant (Legal GPT), case management, and compliance automation across all Indian courts and tribunals.

For MACT case management specifically, the parts of Claw that matter are on the case management and tracking side rather than case search. Claw tracks matters across 8,200+ courts in India, including tribunals, district courts, High Courts, and the Supreme Court, with automatic case status updates, a shared calendar, and cause list tracking. When a hearing date changes or a new order is passed, alerts go out over WhatsApp and email, and Claw’s AI auto-compliance feature can read a court order and schedule the resulting reminders on its own, which matters most at the written statement and evidence stages described above. For a book of MACT matters, MIS reports give a portfolio-level view of what is pending and coming up, and Claw Notebooks give teams a shared place to keep notes and documents against each claim. None of this replaces sound legal judgment on liability or quantum, but it removes the tracking burden that causes most avoidable defaults at scale.

09Sources and further reading

Background on the statutory framework and court systems referenced in this guide:

• Motor Vehicles Act, 1988 (statutory text): indiacode.nic.in
• National Judicial Data Grid / e-Courts (case status and CNR lookup): ecourts.gov.in
• Claw: clawlaw.in

This guide explains the general workflow for managing MACT matters at volume. It is not legal advice on any specific claim.

10Frequently asked questions