What happens if a firm cannot reach its files before a deadline?

The deadline does not move, which is the entire reason a legal practice needs a continuity plan built around court dates rather than around general convenience. An outage that would cost another business a day's productivity can cost a firm a filing, and courts are not sympathetic to server failures.

That asymmetry should shape the whole arrangement. Most continuity advice is written for businesses where recovery time is a commercial question: how much revenue is lost per hour of downtime. For a firm there is a second category of consequence entirely, where a missed limitation date or filing deadline is a professional and insurance problem rather than a productivity one. The plan has to be built for that case, not the average one.

Start by identifying which dates in the next few months genuinely cannot move, and treat the systems needed to meet them as the critical tier. That is usually the practice management system, document storage and email, and it usually is not everything. Ranking matters because in a real incident you cannot restore everything at once, and deciding the order under pressure is how the wrong thing comes back first.

Then set recovery targets and, more importantly, prove them. Decide how long the firm can be without each critical system and how much recent work it could bear to lose, then insist on a timed test restore that demonstrates the number rather than a provider asserting it. The gap between a promised recovery time and a measured one is the most common unpleasant surprise in this field, and it is only ever discovered at the worst moment.

The plan itself should be short enough to follow under pressure: one to three pages naming who declares an incident, who calls whom, the order systems come back, where backups live, and how the firm operates in the meantime. That last part is the one firms skip and the one that saves a deadline. Can a lawyer work from a printed copy of a brief? Is there a way to file if the document management system is unavailable? Who has the court's contact details if an extension must be sought? None of that is technical and all of it belongs in the plan.

Backups need particular care in a legal setting for two reasons. Retention is longer, since client files and trust records must survive well past a matter's conclusion, so backup coverage has to include the systems holding them and survive migrations and provider changes. And the practice management platform being hosted does not mean it is backed up in the sense you need: vendors protect their platform, which is different from protecting you against deletion, a compromised account or a dispute. Ask what you could actually recover, how far back, and how fast.

The threat most likely to trigger all of this is ransomware, and the legal-specific dimension is that firms hold material clients would very much prefer stayed private, which gives attackers leverage beyond encryption. The defences are the ordinary ones done properly: multi-factor authentication, restricted administrative rights, patched systems, and backups that are protected from the network they protect and have been restored in a test. An immutable copy matters more here than in most businesses.

Test the plan with a conversation rather than waiting for an incident. An hour in a room walking through a scenario out loud, the file server is encrypted on the Tuesday before a Friday filing, what happens now, finds more holes than another month of drafting. What it usually finds is not technical: out-of-date phone numbers, an assumption about who has authority, and nobody knowing where the backups actually are.

The honest caveat is that no plan makes a bad week good; it makes it survivable. Even with everything in place a serious incident during a busy period will be unpleasant, involve difficult client conversations and consume the week. The difference is between disruption and a missed deadline, and that difference is worth the modest work of writing the plan and testing the restore. If you want yours built around the dates that actually matter, call 1800 456 567.

Diarise the restore test the way you would diarise anything else that matters, because a plan reviewed annually and a backup restored annually are the two habits that turn all of this from a document into a capability.