Operations · Re-Screening Cadence · Risk Teams
How Often Should You Re-Screen Counterparties for Litigation (2026)
A litigation check is accurate only for the moment you ran it. The day after, a new case can be filed against a counterparty, and your clean result is already out of date. Re-screening is how you keep the picture current, and the real question is not whether to re-screen but how often. Re-screen too rarely and you miss the filing that mattered; re-screen everything daily and you drown in noise and cost. The answer is a cadence matched to risk. This page explains how to set that cadence for an Indian risk, credit or procurement team, and which events should trigger an immediate re-check. Last verified October 2026.
- The question: not whether to re-screen, but how often, because a check is accurate only for the day you ran it.
- Avoid a flat cadence: one frequency for all is too slow for big exposures and wasteful for the long tail.
- Use tiers: high exposure daily or weekly, medium monthly, low quarterly, with continuous monitoring for the top tier.
- Add event triggers: re-check on a credit increase, a renewal, a missed payment, adverse news, or a change of control, whatever the schedule says.
01Why re-screening matters
Most counterparty risk is not present on day one. A borrower that passed its credit check can be dragged into an insolvency petition months later. A supplier you onboarded cleanly can be hit with a fraud complaint. A guarantor can face recovery action. None of that shows up in the check you ran at the start, and the gap between what you know and what is true widens every day you do not look again.
Re-screening closes that gap. It also protects you: if a counterparty goes bad, being able to show you were re-screening on a sensible cadence is the difference between a managed risk and a missed one.
02The wrong way: one cadence for all
The common mistake is picking a single frequency, say once a year, and applying it to every counterparty. It fails in both directions:
- It is too slow for your biggest exposures. A year is a long time for a major borrower or a critical supplier to be in trouble without you knowing.
- It is wasteful for the long tail. Re-screening a tiny, low-risk vendor as often as your largest borrower spends attention where there is little to find.
A flat cadence feels tidy but it mis-allocates the one thing a risk team is short of, which is attention.
03A risk-based cadence
Tier your counterparties by exposure and match the frequency to the tier. A workable starting frame:
| Tier | Who | Suggested cadence |
|---|---|---|
| High | Large borrowers, critical suppliers, key channel partners | Daily or weekly scan |
| Medium | Mid-size counterparties with real but limited exposure | Monthly |
| Low | Small or short-term counterparties, the long tail | Quarterly, plus event triggers |
Set the tiers from the exposure you actually carry: the size of the credit, how hard the counterparty is to replace, and how fast a problem would hit you. Continuous monitoring turns the high tier into an always-on watch rather than a periodic scan. For the wider design, see how to build a litigation-monitoring process.
04Events that trigger an out-of-cycle check
Cadence handles the routine. Some events should trigger an immediate re-check whatever the schedule says:
- A credit increase or a renewal, because you are about to take more exposure.
- A new large order or contract with an existing counterparty.
- A missed payment or a performance failure, which is often the first visible sign of trouble.
- Adverse news or a market rumour about the counterparty or its group.
- A change of control or key management at the counterparty.
Cadence catches the slow drift. Event triggers catch the sudden turn. You need both, because risk arrives on both timelines.
05Keeping it honest
However often you re-screen, read the results with the same caveats:
- "Nothing on record" is not a clean chit. It means nothing was found in the registries searched, on the date searched, under the names searched.
- A new hit needs a confidence check. A match on a common name is not yet the counterparty's matter.
- A pending case is not a verdict. Note it, weigh it, but do not treat an allegation as a finding.
Re-screening tells you what changed; judgement tells you what it means.
06Where 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.
ClawScore (at clawscore.clawlaw.in) is Claw's litigation and criminal-risk intelligence service, and its Constant Monitoring is how you run a risk-based cadence without doing it by hand. Put your counterparties, and their directors, promoters and guarantors, on a watch list and ClawScore scans them across 9,102 courts, benches and forums on a daily, weekly or monthly schedule, reporting New filings, Changed movement and Closed disposals so you see only what moved since the last cycle. You can pull any name as a scored Excel workbook with a Summary and a ClawScore risk band (Clean, Low, Moderate or High), a Matters sheet, a Related parties sheet and a Coverage sheet, and every finding carries a match confidence so a common-name hit is flagged for a human check. Results return in under 5 seconds, judgment search spans 30 crore+ judgments with Supreme Court decisions from 1950 and High Court decisions from 1990, and Claw does not use your searched names or documents to train its AI models. The output is a risk input, not a verdict: "nothing on record" means nothing was found in these registries on the date searched under the names searched, a pending or criminal matter is not proof of guilt, and the workbook is not legal advice and not a credit score.
For an out-of-cycle re-check on a single counterparty, run a case search across Indian courts by party name across every forum at once.
07Sources and further reading
- eCourts (district and High Court case status): ecourts.gov.in
- National Judicial Data Grid (official pendency data): njdg.ecourts.gov.in
- Insolvency and Bankruptcy Board of India: ibbi.gov.in
- Claw: clawlaw.in
This page is general information for an Indian B2B audience, not legal advice. A re-screening cadence supports a risk decision; it does not replace counsel on any specific matter.
08Frequently asked questions
How often should I re-screen my counterparties for litigation?
Match the frequency to the exposure. A workable frame is to scan high-exposure relationships daily or weekly, medium exposure monthly, and the long tail quarterly, with continuous monitoring for the top tier. Set the tiers from the size of the exposure, how hard the counterparty is to replace, and how fast a problem would hit you.
Why not just re-screen everyone once a year?
A single annual cadence fails both ways. A year is too slow for a major borrower or a critical supplier, who could be in serious trouble for months without you knowing, and it wastes attention on tiny, low-risk vendors. A flat cadence mis-allocates the one resource a risk team is short of, which is attention.
What events should trigger an immediate re-check?
A credit increase or renewal, a new large order or contract, a missed payment or performance failure, adverse news or a market rumour about the counterparty or its group, and a change of control or key management. These should prompt an out-of-cycle check whatever the routine schedule says.
Does a clean re-screen mean the counterparty is safe?
No. "Nothing on record" means nothing was found in the registries searched, on the date searched, under the names searched. A matter under a group entity, a namesake confusion, or a forum you did not cover can still exist. Re-screening tells you what changed; it does not certify that a counterparty is risk-free.
How do I re-screen a large book without it becoming a full-time job?
Use continuous monitoring rather than manual re-checks. A monitoring service scans a watch list on a set cadence and reports only what is new, changed or closed since the last cycle, so your team reviews movements rather than re-running searches. Keep a confidence check at triage so common-name hits are verified before they are treated as fact.