Solution · For nonprofits
Reliable IT service, on a budget that has to stretch.
A nonprofit’s IT budget competes with its mission: every pound spent on systems is a pound not spent on the work the organisation exists to do. So the IT has to be reliable, cheap to run, and simple enough for volunteers and part-time staff.
Every pound of IT spend traceable to a real need.
Service levels the team can keep with the staff it has.
Fixes that last, because the cause was addressed.
The problem
Why nonprofit IT is hard to sustain
Nonprofit IT is shaped by scarcity: small budgets, mixed teams of staff and volunteers, and systems inherited from whoever was there before. The answer is discipline, not spending.
Budget competes with the mission
IT spending is judged against frontline work, so it is delayed, reduced, or donated. The result is ageing systems held together by goodwill — until one of them fails at the worst moment.
Volunteers come and go
The person who set up the system leaves, and the knowledge leaves with them. The next volunteer starts from scratch, and the organisation pays for the same learning twice.
Promises made on hope
A service level is promised to staff because it sounds right, not because the team can deliver it with the hours available. When it is missed, trust in the IT team falls with it.
Symptoms fixed, causes kept
The same problem is fixed the same way every month because nobody has time to find the cause. The hours spent on repeats are hours taken from the mission — quietly, every month.
The process
Five steps, and the itserva page for each
Five steps, sized for a small team and a tight budget.
- 01
Make the most of a small budget
Work out what each resolved ticket costs, fully loaded, and where the hours actually go. The number shows which work is worth automating, which is worth documenting, and which should simply stop.
- 02
Agree realistic service levels
Write down what the team can promise with the staff and hours it actually has. A modest target that is kept builds more trust than an ambitious one that is missed every month.
- 03
Log and prioritise
Score urgency against impact before starting work, so the fundraiser’s deadline and the office printer are ranked by what they mean for the mission — not by who asked first.
- 04
Fix root causes, not symptoms
When a problem returns, stop fixing it the same way and ask why — five times, in writing. One permanent fix frees hours every month, and hours are the scarcest resource a nonprofit has.
- 05
Assign clear owners
Record who is responsible, accountable, consulted and informed for each service. In a mixed team of staff and volunteers, a written owner is the difference between a task done and a task assumed.
What’s included
Tools, templates and guides for nonprofits
Template
Root Cause Analysis Template
Work through the five whys and the contributing factors behind an incident.
Template
RACI Matrix Template
Make it clear who is responsible, accountable, consulted and informed.
Product
Service Desk
Log every request and incident in one place, with priority and SLA timers built in.
Measure it
The four numbers worth tracking
Four numbers show whether the IT budget is serving the mission. Review them with the trustees, in plain language, every quarter.
Cost per ticket
What each resolved ticket costs, and where the total goes. It is the number that shows the board the IT spend is controlled — and where a small change would save the most.
SLA met rate
Whether the modest targets the team set were actually met. A kept promise, reported honestly, builds the trust that the next funding request depends on.
Repeat incidents
Incidents with a cause the team has already seen. Every repeat is mission time spent twice — and the clearest sign a root cause analysis would pay for itself.
MTTR
How fast the team recovers when a service fails. For a nonprofit, recovery speed is what protects the working day of people whose time is the mission.
Frequently asked questions
How do we do ITSM with almost no budget?
With free tools and templates, and a little discipline. One shared log, one priority matrix, one written agreement and a regular review cost nothing — and they are the whole foundation.
How do we keep knowledge when volunteers leave?
Write it down as you go: who owns each service, what to do when each one fails, and why the last fix worked. The record is the handover, and it should exist before the volunteer’s last day.
What is a realistic SLA for a small nonprofit?
One the team can keep with the hours it has. A response within one working day for most issues, faster for the service the mission depends on, is a better promise than a same-hour target nobody can meet.
Should we use free software or paid software?
Use what the team can maintain. Free software that nobody maintains is more expensive than paid software that works — count the hours, not only the licence fee.
Spend the budget on the mission, not on repeats.
Run the cost-per-ticket calculator and the root cause template on the problem your team fixes most often. A free workspace saves both, ready for the next board report.