What a Legal Hold Means for Your Project Files

Most of the time, deleting old files is good hygiene. Working copies of finished jobs pile up, storage costs money, and a sensible retention schedule trims what nobody needs anymore. Then a claim letter arrives, or a lawsuit is filed, or an insurer opens a dispute, and that same routine deletion turns from hygiene into a liability. The moment a matter becomes reasonably foreseeable, the files tied to it are supposed to stop moving — and a schedule that keeps quietly clearing them out is now working against you.

A legal hold is the mechanism that stops the clearing. It is worth understanding before you need one, because the whole value of a hold is that it was in place in time. This is the part of keeping a durable record of your files that most firms never think about until the day it is too late to apply retroactively.

What a legal hold actually is

A legal hold — sometimes called a litigation hold — is a decision to preserve specific records because they may be relevant to a legal matter. It suspends the ordinary retention and deletion that would otherwise apply to those records, for as long as the matter is live. It is not a filing format or a special archive; it is an override. The everyday rules keep running for everything else, and the held records are simply exempt from them until someone lifts the hold.

The obligation to preserve can attach well before a case is formally underway. Once litigation or a claim is reasonably anticipated, the expectation is that relevant records are kept, and the failure to do so — letting a routine process destroy them — is what gets firms into trouble, separate from the merits of the underlying dispute.

Why retention and holds have to coexist

Firms need both routine deletion and the ability to freeze it, and the two pull in opposite directions. Retention exists so that data does not accumulate forever; a good schedule is a feature, not a gap. A legal hold exists so that, for a defined set of records, the schedule pauses. A system that only offers one of these is incomplete: keep everything forever and storage and risk balloon; delete on schedule with no way to freeze and you cannot honor a preservation duty when it lands.

In RoverDrop the everyday behavior is that a filed packet's working copy can age out on your firm's own schedule, while the sealed write-once archive copy is always kept. A legal hold changes the calculation for the packets it covers: their working copies are kept too, not just the archive copy, until the hold is released. The routine keeps running everywhere else.

Putting a hold on the files that matter

A hold is only useful if it is easy enough to apply the moment you need it, and specific enough not to freeze your entire firm. Two levels cover the common cases:

• On a single packet. When one submission is tied to a dispute, an office or admin user places a hold on that packet, and its working copies are preserved regardless of the retention setting.
• On a whole job. When an entire project is in question, an admin can hold the job, and every packet under it is covered — including packets submitted after the hold goes on, so work that keeps coming in during the matter is preserved automatically.
• Recorded, and reversible. Placing and releasing a hold are written to the audit trail, so there is a record of when preservation started and stopped. Releasing a packet-level hold is limited to an admin, because lifting it is a management decision, not a routine one.

Why the record of the hold matters too

Preserving the files is half of it; being able to show you preserved them, and when, is the other half. Because a hold is logged as an event on the packet, the same audit trail that records every other action also shows the hold going on and coming off. If anyone later asks whether the records were protected during the matter, the answer is not a verbal assurance — it is a dated entry in the trail. This is especially pointed in insurance restoration and other claim-driven work, where the files behind a contested claim are exactly the ones a routine cleanup would otherwise reach.

The quiet feature you hope to never use

A legal hold is one of those capabilities whose value is almost entirely insurance. Most packets will never be held, and most firms will go long stretches without placing one. But the cost of not having it is asymmetric: a single matter where relevant files were deleted on schedule, because there was no way to freeze them, can dwarf the cost of a decade of careful retention. Set your retention to keep storage sane, know that a hold can override it in a click when it has to, and the day a claim lands becomes a matter of flipping a switch instead of explaining a deletion.