Litigation Tracking for Government and PSU Legal Departments

Government & PSU Legal · Litigation Tracking

Updated for 2026 · Claw Editorial

The Union of India and its ministries, departments, and public sector undertakings are collectively among the largest litigants in the country, with cases spread across the Supreme Court, every High Court, tribunals like the Central Administrative Tribunal, and thousands of district courts. Tracking that litigation is a different problem from tracking a private company's cases: the structure is more layered, the accountability is public, and much of the day-to-day work still happens outside any central system. This page explains why litigation tracking is uniquely hard for government and PSU legal departments, what the government's own LIMBS platform does and does not solve, and what a working system looks like.

01The scale of government litigation

Government litigation in India is not one portfolio, it is hundreds of portfolios sitting inside one another. Every ministry has its own legal cell, every attached department has its own cases, and every public sector undertaking runs its litigation largely on its own, even though all of it ultimately touches the same taxpayer and the same public accountability.

One department can carry tens of thousands of matters

Large PSUs and civic authorities routinely carry litigation portfolios in the tens of thousands, spanning land acquisition disputes, service matters, contract and procurement disputes, consumer complaints, and writ petitions, often managed by a legal cell of a few dozen law officers. That ratio, thousands of matters to a handful of officers, is the central operational fact that any tracking system has to work around. It is the same underlying challenge described in our guide on how to manage a large litigation portfolio, but with a public accountability layer added on top.

The caseload is spread across every level of the court system

A single ministry or PSU can have matters running simultaneously before the Supreme Court, several High Courts, the Central Administrative Tribunal for service disputes, income tax and GST tribunals, consumer forums, and hundreds of district courts. There is no single court where government litigation "lives". Any system that tracks only the higher courts will miss the bulk of the actual caseload.

Empanelled counsel, not an in-house bar

Government departments and PSUs mostly do not employ the advocates who appear in their matters. They rely on empanelled counsel, government law officers, and Central Government Standing Counsel, engaged city by city and court by court. Coordinating updates from a large, geographically spread panel of external advocates is a harder problem than coordinating an in-house litigation team, and it is one every government legal cell shares.

02Why litigation tracking is uniquely hard for government and PSU legal departments

Four features of government litigation make it structurally harder to track than a typical corporate portfolio.

Decentralised ownership

A ministry, its attached offices, and the PSUs under its administrative control each run their own legal function, often with their own record-keeping habits. There is rarely one legal head who can see everything at once. When a Parliament question or a CAG audit asks for the full litigation picture, someone has to assemble it department by department, which takes time the answer usually does not allow for.

Public accountability, not just financial exposure

A private company tracks litigation mainly to manage financial and reputational risk. A government legal cell has that same concern, plus the extra layer of parliamentary questions, RTI requests, CAG audit paragraphs, and vigilance scrutiny. A matter that has gone quiet is not just a risk, it is a potential answer the department cannot give if asked. That raises the bar for how current the tracking has to be.

Frequent transfers and institutional memory loss

Law officers and nodal officers in government service are transferred more often than lawyers move jobs in a private firm. When an officer handling a matter is transferred, the handover depends entirely on whether the case history is written down somewhere the next officer can find it. If it lived mainly in that officer's inbox or personal notes, the incoming officer starts from close to zero.

Procurement rules shape what tools are even possible

Unlike a private company, a government department or PSU cannot simply buy software. Purchases typically go through tendering or the Government e-Marketplace (GeM), with their own timelines and approval layers. This affects how quickly a legal cell can adopt a proper tracking system, and it is a real constraint that any recommendation for government litigation tracking has to account for, not ignore.

03LIMBS, and its limits at department level

The Government of India already has a national answer to part of this problem. The Legal Information Management and Briefing System, LIMBS, is a centralised, web-based platform run by the Department of Legal Affairs, Ministry of Law and Justice, launched in 2016 under the Digital India programme. It is built to let ministries, departments, and PSUs upload details of cases involving the Union of India, and to let empanelled counsel and law officers update those records from a single portal.

LIMBS has real scale. As of April 2025, more than 12.33 lakh court cases had been uploaded to the platform, covering 55 ministries and departments and more than 7,207 empanelled advocates. That makes it, on paper, the biggest single litigation register in the country.

What LIMBS is built to do

LIMBS is primarily a monitoring and reporting mandate. It gives the Department of Legal Affairs and, in turn, Parliament and oversight bodies, a consolidated view of Union of India litigation, and it pushes ministries and PSUs to keep case data current so that view stays accurate. For central-level visibility and compliance, it is the system of record.

Where the gap still sits

What LIMBS was not built to be is a day-to-day litigation management tool for an individual legal cell. Feeding LIMBS accurately still depends on someone inside each department or PSU knowing the current status of every matter in the first place, and that internal, operational layer, hearing alerts, document storage, task reminders, MIS reports formatted for that department's own leadership, is largely left to each department to build for itself. In practice, that means many legal cells are running a spreadsheet or a register underneath their LIMBS reporting, which is exactly the fragile setup this page is about fixing.

The practical framing, then, is not "LIMBS or a tracking system", it is "LIMBS as the compliance layer, and a proper operational system underneath it that makes LIMBS reporting easy instead of a scramble."

04What good litigation tracking looks like for a government or PSU legal department

For a government or PSU legal department, a good tracking system has to satisfy both the operational need and the accountability need at the same time.

• Coverage across the full court hierarchy: the Supreme Court, every High Court, the Central Administrative Tribunal and other tribunals, and the district courts, since that is where the bulk of service, land, and contract matters actually run.
• Role-based, multi-department visibility: a nodal officer should see their department's matters, and a legal head or Secretary should be able to see a consolidated picture across attached offices, without either view getting in the other's way.
• An audit-ready trail: every update, every document, every change of status logged with who did it and when, so that an RTI query or a CAG audit para can be answered from the system rather than from memory.
• An empanelled counsel workflow: a way for external advocates across cities to log updates directly, rather than the department chasing each one by phone or email.
• Data that is easy to hand over: when an officer is transferred, the next person should be able to open the matter file and understand it, without relying on the outgoing officer's notes.

For a government legal cell, a missed update is not just a risk to manage. It is a question the department cannot answer if Parliament, the CAG, or an RTI applicant asks it.

05Key features to look for

Beyond the general criteria above, these are the specific features that matter most in a government or PSU context.

Automatic updates across all relevant courts, not just High Courts

A large share of government litigation, service disputes, land acquisition references, local contract disputes, sits in tribunals and district courts, not only in the High Courts and Supreme Court. A system that covers only the higher courts will leave the largest part of the caseload untracked.

Multi-channel alerts to both the officer and the counsel

Alerts by WhatsApp and email, sent to the nodal officer as well as the empanelled counsel, reduce the single point of failure that exists when only the advocate is reminded of a hearing. Government offices also see more staff turnover through transfers, so alerts should route to a role or desk, not only to one person's inbox.

MIS reports formatted for oversight, not just for the legal team

Reports need to answer the kind of questions a Secretary, a board, or an auditor actually asks: how many matters are pending by category, how many have had no update in the last quarter, and what the department's aggregate exposure looks like. A system that can produce that without a manual compilation exercise saves the legal cell real time at reporting season.

AI-assisted compliance on orders

A system that reads a court order and automatically extracts the deadlines and actions it creates, then schedules reminders for them, removes the step where a busy officer has to read every order line by line and remember to act. Given how thin government legal cells often are relative to their caseload, this kind of automation matters more here than in a well-staffed private legal department.

A searchable institutional memory

Because officers transfer frequently, the system itself becomes the institutional memory for a matter, not any one person. As the matter files build up, they also become a genuine knowledge asset: precedents the department has relied on, arguments that have worked before, and patterns across similar disputes. See our explainer on knowledge management systems for legal teams for how that layer works.

06Where commercial platforms fit alongside LIMBS

Since LIMBS is a compliance and reporting mandate rather than a full operational tool, several Indian commercial platforms are used by government bodies and PSUs to fill the day-to-day tracking layer underneath it. Two with a track record specifically in this space are worth describing fairly.

Legistify offers an enterprise legal management suite, LegisTrak, that covers litigation, contracts, notices, and compliance in one connected platform. Its litigation module tracks matters across a large network of Indian courts and sends real-time alerts on new filings, and the company is used by a number of large Indian enterprises. For a department evaluating it, the fit question is the same as for any enterprise suite: it is built for large, connected legal operations, so it is worth checking how its litigation module maps to the specific mix of tribunals and district courts your department's matters actually sit in.

Provakil is a cloud-based litigation and legal practice management platform with a specific track record in the government space, including a documented deployment with the Delhi Development Authority to manage a very large pending caseload spread across many sub-departments, and a listing on the Government e-Marketplace (GeM), which is directly relevant to how PSUs are able to procure it. Its litigation management product tracks matters across a large number of Indian courts with configurable workflows and an external counsel interface. As with any vendor, the specific coverage, pricing, and deployment model (cloud or on-premise) for a given department should be confirmed directly.

Neither of these is a case-law research tool, and neither replaces the LIMBS reporting obligation itself. Both are examples of the operational layer described above: something that sits underneath LIMBS and makes the department's own day-to-day tracking, and its LIMBS reporting, easier to keep current.

07How to choose and roll out

A government or PSU legal department moving from spreadsheets and registers to a proper system should treat it as a phased project, not a single switch.

Step 1: Map the current portfolio and where the gaps are

Before comparing tools, list every live matter, the court it sits in, the assigned officer or counsel, and the last confirmed update date. This exercise on its own usually surfaces matters that have gone quiet, and it gives you the baseline to migrate from.

Step 2: Decide how the system relates to LIMBS

Treat LIMBS as the compliance layer you must keep feeding, and choose an operational system that makes that feed easier rather than one that duplicates the effort. Confirm with the department's LIMBS nodal officer how data should flow between the two.

Step 3: Check the procurement route early

Because government purchases usually go through GeM or a formal tender, confirm whether a vendor is listed and what the approval path looks like, before you get attached to a particular product. This step often takes longer than the technical evaluation itself, so start it early.

Step 4: Pilot in one department or division first

Rolling out across every attached office and PSU at once is where most government technology projects lose momentum. A single-department pilot, with a clear 90-day review, lets you fix the empanelled counsel onboarding process and the reporting format before a wider rollout.

For a general framework on evaluating matter management software, see our guide on how to choose matter management software in India.

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. It is positioned as India’s first all-in-one platform of this kind.

For a government or PSU legal department, the operational gap this page describes, the layer that sits underneath LIMBS reporting, is the part Claw's case management is built for. Its tracking covers 8,200 plus courts across India, including all states, tribunals, and district courts, alongside the Supreme Court, so matters are not limited to the higher courts where most government litigation does not actually sit. Auto case updates, cause lists, and reminders reach both the responsible officer and empanelled counsel by WhatsApp and email, and the AI auto-compliance feature reads a court order and schedules the resulting deadlines automatically, which matters when a small legal cell is carrying a caseload sized for a much larger team. MIS reports give a department or PSU a consolidated exposure and status picture on demand, which is the same picture an RTI query, a CAG para, or a Parliament question would otherwise force the legal cell to assemble by hand.

Claw also supports translation across ten Indian languages including Hindi, which is relevant for departments that work across regional courts and correspondence. On data, Claw does not use customer case documents to train AI models, a point worth confirming directly with any vendor before a government body shares sensitive matter records with it.

Claw does not replace LIMBS, and it is not a substitute for the reporting obligation to the Department of Legal Affairs. What it can do is give an individual ministry, department, or PSU legal cell the day-to-day tracking, alerting, and reporting layer that makes keeping LIMBS current a byproduct of normal work, rather than a separate exercise. For teams that also need case-law research alongside tracking, Claw's AI-based case search and Legal GPT sit in the same platform. For a closer look at how Claw compares with the commercial platforms named above, see Claw vs Legistify and Claw vs Provakil.

09Frequently asked questions