“Don’t worry, we’ve got an SLA.”
For charities and nonprofits
In charities and nonprofits, SLAs often feel like a safety net. When digital work goes beyond your usual role, like handling donation forms, supporter journeys, volunteer signups, or finance integrations, the SLA can seem like the only thing keeping everything together.
It can feel like the contract alone will keep your website running during an appeal or prevent a form from failing.
But SLAs don’t work like that. They aren’t a shield. Instead, they outline what happens after something goes wrong. An SLA explains who will respond, how quickly, and what compensation you might receive (if any)! It won’t tell you why the problem happened or how to prevent it in the future.
Most issues in the charity sector aren’t because suppliers miss their SLAs. They usually come from everyday challenges like small teams, outdated systems, rushed content updates, old CMS versions, forgotten integrations, or a sudden spike in supporters after media coverage. These problems aren’t covered by a contract. They depend on how you manage your digital work.
The SLA answers one question:
“How quickly will someone start working on this?”
It doesn’t answer the questions that keep charity teams awake at night:
Why did the donation page fail?
Did we lose Gift Aid declarations?
Will this affect funder reporting?
How many supporters bailed before completing their donation?
That gap is important. Even a 99.9% uptime SLA means almost nine hours of downtime each year, and those hours rarely happen when nothing is going on. They usually happen during appeals, campaigns, crisis responses, and funding deadlines. These are the times when digital failures can hurt your reputation and donation inflows, not just your technology.
This is where real-world operations matter more than what’s in the contract. UK guidance on online services reminds organisations that, even when using cloud services, they remain responsible for their own data, risks, and incidents. Put simply, you can outsource hosting, but you can’t outsource accountability.
SLAs are still important. You definitely want clear response times, escalation paths, and someone who will respond. But if you rely on the SLA for peace of mind, thinking “it’s fine, we’re covered,” think again. Risk usually comes from knowledge gaps, technical debt, and unclear ownership, not from the response-time guarantee.
SLAs help you react. Your operating model helps you prevent.
Don’t forget to check what your SLAs really cover and where your organisation might have gaps. I’m happy to help.
Adam
UK‑based. In person, where possible.