Solution · For solo IT admins
Do the work of a team, without the team.
One person, every system, and a queue that never stops. A solo admin cannot do everything — so the job is choosing well: what matters most today, what can wait, and what must be written down before it is forgotten.
The most important problem worked on first, every day.
Downtime priced, so the business understands the risk.
Records that make sense to someone else, not only to you.
The problem
Why solo IT is a single point of failure
Solo work has a particular risk: everything lives in one person’s head. The systems work because one person knows them — and they stop working the day that person is away.
Everything is urgent at once
The printer, the server and the director’s laptop all need attention, and there is no one to share the load. Without a way to rank the work, the loudest request wins and the important one waits.
No one to ask
A problem you have never seen before, and no colleague to talk it through with. The diagnosis takes longer, the fix is less certain, and the second opinion never arrives.
Patching never quite happens
Patching is always planned for Friday, and Friday is always busy. Months pass, the list of unpatched systems grows, and the risk grows with it — silently.
Knowledge in one head
Passwords, quirks, workarounds and history: all of it known to one person. A holiday, an illness or a resignation turns routine knowledge into a crisis for everyone else.
The process
Five steps, and the itserva page for each
Five steps, in the order a solo day demands.
- 01
Cost the downtime
Work out what an hour of downtime costs the organisation. The number is your argument for the backup, the spare, or the maintenance window — and it is stronger than trust me.
- 02
Prioritise alone
Score urgency against impact before starting work, even when you are the only person scoring. The matrix is your second opinion, and it keeps the loudest request from beating the most important one.
- 03
Find the root cause
When something fails twice, stop restarting it and ask why. Five whys, written down, turn a recurring chore into a fix — and a fix into time you get back every week.
- 04
Patch what you own
Compare patch management tools on coverage, automation and price, and pick one that fits a one-person operation. Automation is not a luxury for a solo admin; it is the extra pair of hands.
- 05
Keep the record straight
Log each incident in one page: what happened, who was affected, and what fixed it. The record is for the person covering your holiday — and for you, six months from now, when the same thing breaks again.
What’s included
Tools, templates and guides for solo it admins
Product
ITSM Toolkit
Eight free calculators for SLA uptime, downtime cost, MTTR, MTBF, staffing and more.
Template
Root Cause Analysis Template
Work through the five whys and the contributing factors behind an incident.
Template
Incident Report Template
Record what happened, who was affected, and what was done — in one page.
Comparison
Best Patch Management Software
Patch management tools compared on coverage, automation and price.
Measure it
The four numbers worth tracking
Four numbers keep a solo admin honest about the workload. They are also the evidence for the next conversation about help, budget or time.
MTTR
How fast you recover when something breaks. When it rises, ask what is slowing you down — usually access, knowledge, or a fix that was never finished.
Downtime cost
What the downtime in the month actually cost. It is the number that turns we need a backup from a request into a business case.
Repeat incidents
Incidents with a cause you have already seen. Every repeat is time spent twice — and the clearest sign a root cause analysis is overdue.
Unpatched systems
Systems that missed the last patch cycle. For a solo admin this is the number that matters most, because it is the risk nobody else is watching.
Frequently asked questions
How do I prioritise when everything is urgent?
Score impact first: what breaks for the most people, or stops the business earning? The matrix turns a room full of urgent requests into an order, and the order is defensible when someone asks why their issue waited.
What should I document first?
The things only you know: passwords and access, the quirks of each system, and what to do when each service fails. Start with the service whose failure would hurt most.
How do I make time for patching?
Give it a fixed slot and treat it like a meeting you cannot move. Better still, automate it: a patching tool that fits a one-person team pays for itself in the Fridays it gives back.
When should a solo admin ask for help?
When the numbers say so: rising MTTR, growing repeat incidents, or a patch backlog that never shrinks. Those numbers are the case for part-time help, a managed service, or a second pair of hands.
Write down what only you know.
Start with the incident report template and the downtime calculator — the two things that make the solo workload visible. A free workspace saves them, so the record survives your next holiday.