Every public High Court number comes from one published aggregate snapshot.

What this page covers

This page tracks High Court of Tripura across Tripura. Aggregate observability only: pending load, last-month institution and disposal, age buckets, and published trend points.

It is a High Court module inside NyaayWatch, not a district ranking page and not a case-search surface.

What it does not do

It does not predict outcomes, judge judges, or imply cross-tier comparability with district or Supreme Court surfaces.

When the source does not expose a trustworthy source snapshot timestamp, the page says so directly and shows capture time instead.

Explicit court-first coverage

Current coverage on this page: Tripura.

The public schema carries this boundary explicitly through coveredGeographies[], so a High Court page can represent one court across multiple geographies without pretending it is a single-state surface.

Separate from lower-court geography pages

A lower-court state page is a different scope from a High Court page. NyaayWatch does not reuse district-layer language to describe a High Court publication.

That keeps the hierarchy honest: district and subordinate courts sit under High Courts, but this page still reports one High Court aggregate publication.

Court-first coverage

Some High Courts cover more than one state or Union Territory. The page names the court first and carries the coverage boundary through coveredGeographies[].

Reference date fallback

When HC NJDG does not expose a trustworthy source snapshot date, NyaayWatch uses the captured page timestamp and labels it as captured_at.

Directly sourced

Pending civil, pending criminal, pending total, instituted last month, disposed last month, and age buckets come directly from the official HC NJDG High Court dashboard.

NyaayWatch framing

NyaayWatch adds publication timestamps, freshness, methodology versioning, and an explicit rule for which date to show so the snapshot is citeable and auditable.

Backlog movement as share of pending load

Calculated as cases filed last month minus cases cleared last month, divided by pending cases. It gives a scale-aware view of whether the pending pile grew or shrank.

Break-even clearances

The number of extra clearances needed last month to keep the High Court backlog from growing. It is zero when clearances matched or exceeded filings.

10% reduction scenario

A scenario metric, not a prediction. It estimates the extra monthly clearances needed to reduce the pending load by 10% over 12 months while covering last month's filing-clearance gap.

Civil-criminal imbalance

Compares the criminal share of pending cases with the criminal share of last-month clearances. The result is a docket signal for inspection, not a cause or blame claim.

Case-type concentration

When the source exposes case-type rows, NyaayWatch shows how much of the pending load sits in the five largest case types. It is omitted when the source does not provide a defensible case-type breakdown.

When HC NJDG exposes a source date

The page can show a source snapshot date directly.

When HC NJDG does not expose one

The page uses the captured page timestamp as referenceDateAt and labels it as captured_at instead of inventing a source date.

This is the current posture for the live public High Court pages.