This clause requires you to have a detailed plan to restore your systems and data after a major disaster, and often requires you to test it regularly and provide proof. It matters because it's more specific and demanding than business continuity—it's about actually recovering from catastrophic failure, not just keeping going. For example, you might need to prove you can restore all customer data within 24 hours of a fire destroying your building. Legally, this is a strict obligation: if disaster strikes and you can't recover, you're liable for damages even if you did your best.
Get expert advice before committing to specific recovery timescales—don't guess. Negotiate a clause that says "recovery time objective" (RTO) and "recovery point objective" (RPO) based on what's actually realistic for your business size (e.g., "restore within 48 hours, with data no older than 24 hours"). Include a clause that limits your liability if recovery takes longer due to the scale of the disaster, and make sure they understand this will cost money—you may need to pass some costs to them or charge a premium for this service. ---
Frequently Asked Questions
What does this clause mean in simple terms?
This clause requires you to have a detailed plan to restore your systems and data after a major disaster, and often requires you to test it regularly and provide proof.
Why should I care about this clause?
It matters because it's more specific and demanding than business continuity—it's about actually recovering from catastrophic failure, not just keeping going.
What are my options?
For example, you might need to prove you can restore all customer data within 24 hours of a fire destroying your building.
How does this affect small businesses?
Legally, this is a strict obligation: if disaster strikes and you can't recover, you're liable for damages even if you did your best.