The most avoidable embarrassment in a commercial dispute is not a weak argument. It is standing up to explain why the six months of correspondence that would have settled the point no longer exists, because a retention policy nobody in the legal team had ever read deleted it while the dispute was already brewing. India has no US-style discovery machinery, and one consequence has been that most Indian companies never developed a preservation reflex. That gap is now expensive, because the documents that decide modern commercial disputes live in systems built to delete them.
Ask an Indian general counsel what happens when a serious dispute becomes likely and you will hear a sensible account of strategy: brief senior counsel, assess the claim, work out the commercial appetite, decide whether to make the first move. Ask the same person what instruction went out to the business about not deleting anything, and to whom, and whether anyone confirmed receipt, and the conversation usually gets shorter. The instinct that preservation is somebody else's jurisdiction, an American problem imported by American lawyers, is understandable and it is out of date.
This article sets out what Indian law actually expects on preservation, why the practical trigger is still the moment a dispute becomes reasonably foreseeable, the genuinely hard collision between preservation and the deletion obligations that data protection law creates, the mechanics of a hold notice that works, and the step everybody forgets, which is releasing it. It is general commentary for practitioners rather than legal advice, and how any of it applies to a specific dispute turns on the facts and on the law as it stands when you act.
The argument in one line
Preservation discipline is the cheapest insurance a legal function can buy. It costs a memo, a mailbox setting and an afternoon; the alternative is explaining a gap in the record to a judge, in a forum where the principle that a party withholding evidence is presumed to be withholding something unhelpful is very much alive.
What Indian Law Actually Expects
Start with the honest position, because overstating it is how this subject loses credibility with Indian practitioners. There is no general, automatic, party-driven discovery obligation in Indian civil procedure of the kind an American litigator would recognise. There is no rule requiring you to volunteer every document in your possession that touches the subject matter to your opponent as a matter of course, no deposition machinery attached to it, and no developed body of sanctions jurisprudence for spoliation. Anybody who tells an Indian board that failing to issue a hold notice exposes it to American-style consequences is selling something.
What exists instead is narrower, and still enough to make preservation matter a great deal. Three strands are worth separating.
Disclosure in commercial suits
The Commercial Courts Act, 2015 changed the disclosure regime for commercial disputes above the specified threshold. A party is required to disclose documents in its power, possession, control or custody, filed along with the plaint, and that disclosure is supported by a statement of truth. This is a real obligation with a personal edge to it: someone signs. A company that has allowed the relevant material to be destroyed after the dispute was foreseeable is in the uncomfortable position of making a truthful statement about a record it degraded itself. The precise scope, thresholds and the consequences of non-disclosure should be confirmed against the statute and the procedure as they stand, but the direction of travel is clear enough to plan around.
Adverse inference
The older and broader strand is the presumption courts have long drawn about withheld evidence. The principle familiar from illustration (g) to Section 114 of the Indian Evidence Act, 1872, that evidence which could be produced and is not produced would, if produced, be unfavourable to the party withholding it, has been carried into the Bharatiya Sakshya Adhiniyam, 2023, which replaced the Evidence Act. It is a discretionary tool rather than an automatic penalty, and it is applied with judgement. But it is the reason a missing document is not neutral. A gap where the contemporaneous record should be invites the least charitable available explanation, and the party with the gap has to argue against gravity.
Production, orders and regulators
Courts can direct discovery, inspection and production on application. Investigating agencies can require the production of documents. Arbitral tribunals routinely order disclosure, and in institutional arbitration the practice is often closer to international norms than to Indian civil procedure. Regulators in supervised sectors can call for records under their own powers. None of these need your consent, and all of them arrive as a demand for material you are assumed to still have. The obligation is a demand for records, not an inquiry into whether your retention policy was reasonable.
India will rarely punish you for failing to issue a hold notice. It will simply assume the worst about the document you no longer have.
The Trigger: When a Dispute Becomes Reasonably Foreseeable
Because the Indian obligation is not framed as a preservation duty attaching at a defined moment, there is no bright line to point to. That is exactly why the sensible operating standard remains the one developed elsewhere: preserve from the point at which litigation or a formal proceeding becomes reasonably foreseeable. Not certain, not commenced, not served. Foreseeable to a reasonable person inside the business who is paying attention.
This is a judgement, and it should be made deliberately rather than allowed to drift. In practice a small number of events almost always meet the standard, and building a list of them into your policy converts a philosophical question into an operational one.
- A legal notice, statutory demand or notice invoking arbitration is received, or one is issued by you.
- A counterparty formally alleges breach, repudiates, or stops performing while asserting a claim.
- A regulator opens an inquiry, issues a show cause notice, or requests information in a way that signals more than routine supervision.
- A whistleblower complaint or internal investigation raises conduct that could plausibly become a proceeding.
- A serious workplace incident, a safety event, or a data breach with identifiable affected individuals.
- The business itself decides to sue, which is the trigger companies most reliably overlook because the exposure feels one-directional.
Two failure modes bracket this. The first is triggering too late, which is the common one and produces the gap. The second is triggering on everything, which produces hold fatigue: an organisation under forty overlapping holds, none of them released, where the instruction has stopped meaning anything because it always applies. Both are governance failures rather than legal ones, and both are fixed by making the decision to issue a hold a named person's job with a written rationale.
The Collision With Data Protection, Which Is Genuinely Hard
Here is the problem nobody has solved cleanly, and it deserves to be named rather than glossed over. Modern data protection thinking pushes hard in the opposite direction to preservation. It asks organisations to collect less, keep it for no longer than the purpose requires, and delete it when the purpose is exhausted. The Digital Personal Data Protection Act, 2023 is built around that architecture: a data fiduciary processes personal data of a data principal for a specified purpose, on a notice and on consent that must be free, specific, informed, unconditional and unambiguous, and the framework contemplates erasure when the basis for holding the data falls away. The commencement of the Act, the rules made under it and the operational position of the Data Protection Board have moved over time, and what is actually in force must be confirmed against what is currently notified.
A litigation hold is, functionally, an instruction to stop deleting personal data. The people whose data sits in the preserved mailboxes are employees, customers, counterparty staff and sometimes complete strangers who were copied on a thread. Frameworks of this kind generally recognise that retention required for compliance with law, or for the establishment or defence of legal claims, is a different case from retention by inertia. But recognising the category does not do the work for you. It means you have to be able to show which category a given retention decision falls into, which is a documentation problem, and documentation is where most Indian holds are thinnest.
The two ways this goes wrong
The first is a company that keeps deleting on schedule through a live dispute because nobody told the systems team to stop, and then explains the gap to a judge. The second is a company that issues a permanent, unbounded hold over entire mailboxes and shared drives, never reviews it, and quietly becomes an organisation retaining personal data indefinitely with no articulable purpose. Both are failures of the same missing discipline: a scoped, reasoned, documented and time-bound decision. A hold that is narrow, written down and released when the reason expires answers both problems at once. A hold that is either absent or infinite answers neither.
The practical resolution is scope and record. Preserve what is relevant to the anticipated dispute rather than everything belonging to everyone who touched it, write down why the retention is necessary and what proceeding it relates to, keep the preserved material access-controlled rather than generally readable, and diarise a review. If your data protection officer and your litigation lead have never discussed the standing conflict between the retention schedule and the hold register, that conversation is overdue and it is short.
Auto-Deletion Is the Single Biggest Modern Risk
If you take one operational point from this article, take this one. The greatest threat to the evidence in a modern Indian commercial dispute is not a person shredding documents. It is a default setting. Messaging platforms with disappearing messages turned on at the workspace level, email retention policies that purge after a fixed period, chat histories that expire, ticketing systems that archive and then delete, call recording retained for a short window, CCTV overwritten on a rolling cycle, cloud storage lifecycle rules that transition and then expunge. Every one of these was configured for good reasons, usually storage cost or privacy hygiene, by people who were never told that a dispute was brewing.
The commercial reality makes it worse. A great deal of Indian deal-making, project management and vendor coordination happens on consumer and workplace messaging apps. The conversation that actually explains why a milestone slipped is frequently not in email at all. It is in a group chat, on a personal handset, subject to a disappearing-message timer that the participants set without a thought, and it is gone in seven days.
The counter-measure is mechanical rather than clever. When a hold is issued, someone with administrative authority over each relevant system suspends the deletion mechanism in that system, and confirms in writing that they have done it. A hold notice that reaches custodians but not administrators preserves intentions while the machinery keeps deleting.
Personal Devices, and the Limits of Your Reach
Bring-your-own-device is the norm across large parts of Indian industry, and it creates a preservation problem that no policy fully closes. Material relevant to a dispute sits on a handset the company does not own, in an app the company does not administer, belonging to an employee with privacy interests of their own that are constitutionally recognised and now reinforced by data protection expectations. You cannot simply image it, and you should not pretend the question is easy.
What you can do is act early and proportionately. Identify at the outset which custodians are likely to have used personal devices for work on this matter. Instruct them specifically, in writing, not to delete relevant material and not to reset or replace the device while the hold is in force. Where the material is genuinely important, arrange targeted collection with consent, limited to the relevant conversations and time period rather than the whole device, conducted by someone who can attest to the method. Then record what was preserved, what was not, and why. Departure is the pressure point: an employee who leaves mid-dispute takes their handset with them, and the window to ask cooperatively closes the day they hand in their laptop.
The Mechanics of a Hold Notice That Actually Works
A hold notice is a short document that does an unglamorous job, and almost all of its failures are failures of specificity. The version that circulates in most companies is a paragraph asking people to retain all documents relating to the matter. That instruction is unfollowable. It does not tell a recipient what the matter is in terms they recognise, what a document means in their working life, which of their systems it covers, what they must actively stop doing, or whom to ask. The table below sets out what each element is for and how it fails when it is done loosely.
| Element | What good looks like | How it fails in practice |
|---|---|---|
| Who issues it | The general counsel or a named senior legal officer, with visible authority to bind the business and to override a system policy. | Sent by a junior associate or a paralegal, so a systems team treats it as a request rather than an instruction and defers it behind other work. |
| Scope | Described by subject, counterparty, project and date range in language the recipient recognises from their own work. | Framed as all documents relating to the dispute, which recipients cannot map onto anything and therefore quietly ignore. |
| Custodians | Named individuals, identified by asking who actually worked on this, including finance, procurement and site staff, not only the deal team. | Circulated to a distribution list or the whole department, so nobody feels personally addressed and nobody is accountable. |
| Systems | Listed explicitly: email, the messaging platforms in use, shared drives, the ERP, ticketing, CCTV, call recordings, physical files. | Left implicit, so custodians think about email only and the material that decides the case sits untouched in a chat archive. |
| Suspension of deletion | A separate, specific instruction to administrators to suspend retention, purge and lifecycle rules on the identified systems, confirmed in writing. | Never sent, because the notice addressed people rather than machinery, and the machinery is what does the deleting. |
| Acknowledgement | Each recipient confirms receipt and understanding, and the confirmations are tracked to completion, not merely requested. | No acknowledgement sought, so months later you cannot show that anyone was ever told anything. |
| Reminders | Periodic reissue on a fixed cycle, and immediate reissue when a new custodian joins or a departing custodian is identified. | One-off notice at the start of a matter that runs for four years, by which time half the recipients have changed roles. |
| Release | A written release when the matter and any appeal or limitation window has genuinely closed, restoring normal retention. | Never issued, so holds accumulate, retention drifts indefinitely, and the register stops being credible. |
Note how much of that table is about authority and follow-through rather than drafting. The notice is a short document. The work is in who signs it, who receives it, who confirms, and who checks.
Running a Hold, End to End
Make and record the trigger decision
A named person decides that a dispute is reasonably foreseeable, and writes down the date and the reason in two lines. This entry is what later demonstrates that preservation was a considered decision rather than an accident, and it also disciplines the opposite error of issuing holds reflexively.
Map custodians and systems before you draft anything
Ask who actually worked on this, and follow the answer past the obvious team into finance, procurement, operations and site staff. Then list the systems those people use, including the messaging platforms nobody puts in a policy document. The map determines the quality of everything downstream.
Issue the notice from someone with authority
Send a specific, readable instruction from the general counsel or an equivalent, naming the scope, the custodians, the systems, what must not be deleted and what behaviour must stop. Include a named contact for the inevitable question about whether a particular thing is covered, and answer those questions generously.
Suspend the deletion machinery in parallel
Separately instruct the administrators of each identified system to suspend retention, purge, archive and lifecycle rules, and to place the relevant accounts and repositories under preservation. Require written confirmation that it has been done, per system. This is the step whose absence causes the loss.
Collect acknowledgements and chase them to completion
Track who has confirmed and who has not, and escalate the stragglers. Partial acknowledgement is the state most holds settle into, and it is precisely the custodian who never replied whose material later turns out to have gone.
Preserve the important material properly, not just in place
For material that is likely to be produced or relied on, take a defensible copy rather than trusting that a live system will remain unchanged. Record who collected it, when, from where, by what method, and with what integrity check, and keep the copy access-controlled.
Refresh on a cycle and on every change of people
Reissue the notice periodically for as long as the matter runs. Add new joiners who inherit the work, and capture the accounts and devices of anyone leaving before the offboarding process deprovisions them. Long matters lose material through attrition, not through drama.
Release deliberately, in writing, when it is truly over
When the matter, and any appeal or limitation window that could revive it, has closed, issue a written release restoring normal retention, and remove the entry from the register. Teams almost always forget this, and the cost is an organisation retaining personal data forever with no purpose it can articulate.
Chain of Custody and Getting Electronic Evidence Admitted
Preserving material and being able to use it are different achievements, and Indian practice has been unforgiving about the gap. Electronic records require certification to be adduced, a requirement long familiar as the Section 65B certificate under the Indian Evidence Act, 1872, and carried over into the Bharatiya Sakshya Adhiniyam, 2023. The leading authority on the requirement is Arjun Panditrao Khotkar v Kailash Kushanrao Gorantyal (2020), and anyone intending to rely on electronic material should work through what it requires with counsel well before trial rather than in the week the documents are tendered.
The operational consequence for a preservation programme is that the certificate must come from a person in a position to give it, in relation to a device or system that still exists and whose operation they can speak to. That has an uncomfortable implication for a company that has migrated platforms, decommissioned a server, or lost the administrator who ran it. Preserving the data while destroying the ability to certify how it was produced is a real and common outcome.
Preserve the ability to certify, not only the bytes
When you preserve electronic material, record at the same time who operated the system, what the system was, that it was working normally in the relevant period, and how the copy was produced. Keep hash values and a simple custody log showing every transfer. A pristine copy that nobody can competently speak to is a document you may not be able to use. Decide early, with counsel, who your certifying witness will be, and check that this person will still be reachable when the matter comes to trial, which in India may be a considerable time from now.
Cross-Border and Cloud-Hosted Data
Most of the material a hold covers is no longer in a building you can walk into. It is in a cloud tenancy, possibly in another jurisdiction, administered by a vendor under a contract negotiated by procurement. Three practical points follow. First, your ability to preserve depends on the vendor's tooling and on your subscription tier, and legal-hold features are commonly gated behind a licence nobody bought. Find that out before the dispute, not during it.
Second, the vendor's own deletion behaviour is contractual. What happens to your data on account suspension, on termination, or after a deletion request, is a clause, and it is worth reading before you rely on the assumption that anything you deleted is retrievable. Third, group companies complicate everything: material held by an overseas affiliate, on infrastructure it controls, may be within your power, possession, control or custody for disclosure purposes while sitting outside the systems your Indian team administers, and moving it may engage local restrictions of its own. Sort that with counsel rather than by asking an affiliate's IT manager to export a mailbox as a favour.
Where CourtMesh Fits
To be precise about the claim: CourtMesh is not an archiving product and does not preserve your mailboxes. Preservation happens in the systems that hold the data, using their own controls. What CourtMesh addresses is the surrounding legal workflow, the part that decides whether a hold is issued in time and against the right dispute.
Contract obligations kept where you can find them
My Agreements, the CourtMesh contract lifecycle app, holds contracts with their obligations and dates captured as structured data. When a relationship starts to sour, the notice provisions, records clauses and audit rights that shape a hold are a lookup rather than a search through a shared drive.
Early warning that a dispute is real
A private, organisation-scoped watchlist surfaces new matters involving a party you are monitoring. Learning that a counterparty has filed, or that a creditor has moved against it, is exactly the kind of event that should trigger a preservation decision rather than a surprise.
Counterparty behaviour before you commit
Counterparty litigation and insolvency screening shows how a party has actually behaved when relationships failed. A counterparty with a pattern of aggressive litigation is one whose matters you should expect to fight, which is a reason to preserve early rather than optimistically.
Research on how these questions are treated
Unified search across the Supreme Court, 25 High Courts, District Courts and Tribunals over roughly 310 million cases from official government portals, with AI case analysis, for working through how courts have handled adverse inference, disclosure and electronic evidence in comparable situations.
None of that issues your hold notice for you, and CourtMesh does not give legal advice. It shortens the distance between the moment a dispute becomes foreseeable and the moment somebody in legal knows about it, which is where most preservation failures actually begin.
Decide the preservation question before it decides itself
India will not fine you for failing to issue a hold notice. It will simply let the missing document speak for itself, and the presumption that runs against a party withholding evidence is old, familiar and entirely alive in the Bharatiya Sakshya Adhiniyam, 2023. Write down what triggers a hold, give one named person the authority to issue it, send it to administrators as well as custodians, collect the acknowledgements, and release it when the matter is genuinely over. The whole discipline costs an afternoon and a register. CourtMesh keeps contract obligations, counterparty exposure and case law research behind one login, with My Agreements for the contracts and a private watchlist so a new filing against a party you care about reaches you when it appears rather than when it is served.
Explore CourtMesh
