We use a session cookie and first-party analytics to run this site — no third-party trackers, no ads. Details in our Privacy Policy.
RESEARCH From the Research Desk — The sub-₹100 crore acquisition market, sized. Read it →
Methodology

How we know what we publish

India's insolvency record is public — and messy. Registers contradict themselves, order PDFs bury fee amounts next to claim amounts, and aggregators misattribute cases between similarly-named companies. This page explains how stressed.in turns that raw record into data you can act on: where every number comes from, how conflicts get settled, and what happens when we're wrong.

Operating rule: sell only what's true today
9,052
CIRP case records
4,663
IP profiles tracked
38,085
Tribunal orders indexed
24,872
Case events · 30 days
01 · The source hierarchy

Not all public data is equal — so we rank it

Every field we publish is traceable to a source, and every source sits in a trust tier. A fact is publishable only when a Tier-A or Tier-B document has been opened and read by us — a listing, a tag, or a search result is a claim, never proof.

A

Primary record — settles a fact outright

Tribunal order PDFs, IBBI per-case process pages (public announcement, claims lists, Form-G rounds, appointed professionals), MCA master data, regulator orders on the regulator's own domain. When Tier A speaks, the question is closed.

B

Venue & agency documents — authoritative in their domain

Rating-agency rationales, auction notices on lender domains, tribunal cause lists. These settle facts inside their own domain — a reserve price is a price marker, never a valuation.

C

Registry aggregators — usable, attributed, never load-bearing

Third-party registry mirrors are used only for narrow facts like directorships and charges, always with the aggregator named. They never establish that a proceeding exists — we have caught rupee-identical figures attributed to two "different" companies that were one case, misfiled.

D

Press — colour and leads only

Financial press points us at documents; it is never itself the source of a figure. A tribunal PDF hosted by a news site is the document itself — we cite the PDF and note the host.

02 · When sources disagree

The record contradicts itself. We adjudicate — with rules, not guesses

Public insolvency data doesn't just have gaps; it has active contradictions. Two professionals listed against the same case. A register saying one thing and the case file another. Our resolution rules are fixed in advance and applied the same way every time:

Per-case pages outrank the register

IBBI's per-case process pages record who was actually appointed to a case, with commencement dates. Per-professional register pages are partly self-reported and can double-list. When they conflict, the case page wins — and the contradiction itself is logged as a finding.

An independent corroboration layer

Every case-to-professional link in our spine is checked against a separately scraped layer built only from per-case appointment records. A link that no source supports doesn't stay in the data — it goes to review.

Identity by registration number, never name

India has many professionals sharing a name. We match by IBBI registration serial. Companies are matched by their CIN registration number, which survives renames, conversions and state changes.

The fee-trap rule

Rupee amounts inside tribunal order PDFs are almost always fees, costs or bid figures — not claim amounts. We never fill admitted claims or liquidation values from an order PDF. Claim figures come only from claims-list filings.

Case study · a defect we found before you did

The expired-registration pollution class

In 2016-17, IBBI issued a cohort of provisional registrations that all expired by mid-2017. Their register pages, however, stayed online — and over the years, those dead pages silently accumulated the case mandates of later, unrelated professionals.

The result: a professional's public register page could show dozens of cases that were never theirs. Anyone scraping the register at face value inherits this pollution and reports inflated, misattributed track records without knowing it.

We found this class by cross-examining our own data — duplicate-appointment audits surfaced impossible patterns, per-case records disproved them, and we purged roughly 4,900 phantom case links across 528 expired registrations. Those expired records are now flagged, excluded from every directory and ranking, and where the professional re-registered, their page points to the current registration. A standing weekly guard prevents the pollution from re-entering on any future refresh.

03 · Standing safeguards

Accuracy isn't an event here — it's a schedule

Clean-once data rots. Ours is defended by recurring, automated checks with defined pass conditions:

Verbatim storage. We store what the source printed and format at display. If IBBI prints a contradiction, our database faithfully contains that contradiction — labelled, not silently "fixed".
Missing is not zero. A blank in a source is stored as unknown and shown as a dash — never as ₹0, never as "No". A professional whose accreditation status isn't published shows "not published", not "lapsed".
No derived numbers where the source prints one. We don't sum, infer or extrapolate figures the primary record states directly. Where it states nothing, we say nothing.
Weekly refresh with lifecycle guards. The IBBI refresh runs weekly: concluded cases are never overwritten by stale feeds, existing records are updated in place, and the expired-registration guard runs at the end of every cycle.
Monthly zero-rows audits. A battery of cross-source consistency checks — duplicate appointment slots, multi-claimed roles, spine links unsupported by any source, unflagged expired registrations — runs monthly. The pass condition for the critical checks is zero rows, and the counts are logged.
Honest metrics. Our headline measure of a professional's performance is recovery versus liquidation value — what was realised against the floor value of the assets they were handed. Creditor haircut is a property of the distressed company's condition, so we don't pin it on the professional who administered it.
04 · When we're wrong

Every page has a door for corrections — and someone behind it

With 9,052+ case records compiled from imperfect public sources, errors will exist. What separates a data platform from a data dump is what happens next:

STEP 1

Report it

Every professional profile carries a "Report an error" form, and any case record can be challenged through our contact page. One paragraph and, optionally, your email.

STEP 2

It queues for review

Reports land in a review queue — they are read by a person, not auto-applied and not auto-discarded.

STEP 3

Source decides

The correction is checked against the tier-A record. The document decides — not the report, and not our existing data.

STEP 4

Fixed at the root

Verified corrections are applied to the underlying record, so every page, ranking and metric that touches it updates together.

Professionals can go further: claiming your profile (free) lets you flag mandate-level issues directly, and verified corrections are prioritised.

05 · Freshness

Dated intelligence is misinformation with a citation

A distressed-asset record is only as useful as its recency — an EoI deadline that passed last week is worse than no data. Tribunal orders are indexed on a rolling basis, the IBBI pipeline refreshes weekly, and case events feed member alerts daily. We publish our own freshness status openly at /freshness — the same page we use internally to hold ourselves to it.

Judge the data, not the pitch

The first six entries in every directory and the case pages we feature are open. Read them against the primary record — that's what we do all day.

Browse ongoing cases → RP tracker