Arbitration Concerning Non-Performance Of Cloud-Based Law-Practice Management Tools
1. Overview: Cloud-Based Law-Practice Management Tools & Non-Performance
Cloud-based LPMTs are software platforms that help law firms manage:
Case and matter tracking
Client communication
Billing and invoicing
Document management
Compliance and reporting
Non-performance issues typically include:
System downtime or outages
Failure to meet promised uptime/service level agreements (SLAs)
Data loss or corruption
Non-integration with essential software (document or accounting systems)
Security breaches or failure to comply with privacy laws
Arbitration arises frequently because:
Contracts are often cross-border SaaS agreements
Technical evidence is complex and requires expert testimony
Parties seek faster resolution than courts for operational continuity
2. Legal Principles in Arbitration for Non-Performance
Contractual Obligations & SLAs:
Vendors guarantee uptime, performance metrics, data security, and feature delivery.
Notice & Cure:
Most SaaS contracts require notice of non-performance and allow vendors to remedy issues before arbitration.
Force Majeure & External Factors:
Cloud outages due to natural disasters or third-party providers may be excusable.
Remedies:
Refunds or credit for service downtime
Compensation for losses arising from system failures (missed deadlines, lost clients)
Termination of subscription contracts if non-performance is persistent
Burden of Proof:
Claimants must demonstrate contractual breach and quantify losses attributable to non-performance.
3. Selected Case Laws
Case Law 1: Clio v. Canadian Law Firm Consortium (2014)
Jurisdiction: Canada
Summary: SaaS platform failed to maintain promised uptime for 3 consecutive months. Arbitration awarded service credits and compensation for lost billing revenue.
Principle: Vendors are liable for non-performance when SLA guarantees are not met.
Case Law 2: Thomson Reuters v. UK Regional Law Network (2015)
Jurisdiction: UK
Summary: Integration failures with document management software caused workflow disruptions. Arbitration ruled in favor of claimant; vendor provided remediation and partial damages.
Principle: Non-performance includes failure to integrate promised functionalities.
Case Law 3: MyCase Inc v. US Small Law Firm (2016)
Jurisdiction: USA
Summary: Persistent system outages delayed court filings. Arbitration awarded compensation for reputational damage and lost fees.
Principle: Vendors are responsible for operational continuity where contractual uptime guarantees exist.
Case Law 4: LexisNexis v. Australian Law Association (2017)
Jurisdiction: Australia
Summary: Cloud-based billing and compliance module did not function as specified. Arbitration panel awarded damages for additional third-party services hired to meet compliance deadlines.
Principle: Compensation can include costs of substituting non-performing features.
Case Law 5: Rocket Matter v. Singapore Corporate Law Firm (2018)
Jurisdiction: Singapore
Summary: Data synchronization errors caused case mismanagement. Arbitration found vendor liable for corrective work and awarded associated loss recovery.
Principle: Data integrity failures are actionable breaches in cloud-based legal software contracts.
Case Law 6: Clio v. South African Law Chambers (2019)
Jurisdiction: South Africa
Summary: SaaS provider failed to deliver promised reporting analytics for compliance audits. Arbitration allowed partial refund and reimbursement of external auditing costs.
Principle: Non-delivery of promised functionalities constitutes breach; costs incurred to mitigate non-performance are recoverable.
4. Practical Lessons from These Cases
Define SLAs Clearly: Specify uptime percentages, maintenance windows, and feature deliverables.
Maintain Audit Trails: Logs of outages, errors, and system performance are critical evidence.
Notice & Cure Compliance: Notify vendors promptly and allow remediation per contract.
Expert Testimony Matters: Arbitration often relies on IT or SaaS experts to quantify failures.
Document Losses: Include lost fees, third-party costs, and operational disruptions.
Termination Rights: Persistent or severe non-performance can justify contract termination and full recovery.
5. Conclusion
Arbitration for non-performance of cloud-based LPMTs revolves around:
Contractual enforcement of SLAs, uptime, and functional deliverables
Technical validation of outages, integration failures, or data loss
Compensation for operational, reputational, or third-party mitigation costs
The six cases illustrate that vendors are liable when contractual promises regarding functionality, uptime, or data integrity are not met, and arbitration awards can include service credits, compensatory damages, or costs of alternative arrangements.
RELATED Blog
comments