Picture an office manager at a small advocate’s practice, a made-up composite, on a Monday morning. Three clients have rung to say the online appointment form “did nothing” over the weekend, and a fourth says the document upload page timed out twice. Nobody lost a case, but trust took a small knock. The manager wonders whether there is a systematic way to keep the practice’s online services dependable without hiring an engineering department. There is, and it comes from software operations: SRE, or site reliability engineering. This checklist adapts it for an advocate’s office, a legal information site, or any practice with a web presence. It is general information about running online services, not legal advice.
The ideas below follow the summary in the Ops Atlas page on SRE, translated into office language. Work through it with a notebook, a pen and an hour of quiet time.
Checklist item 1: write down what clients must be able to do
List the three or four online actions that matter most. Booking a consultation, sending a document, checking when the next appointment is, reading a published guide. For each one, define “worked” from the client’s perspective. The discipline expresses this as good attempts divided by valid attempts, measured as close to the client as possible. An honest tally of form submissions that reached your inbox, divided by submissions people started, tells you far more than a hosting company’s cheerful uptime badge.
Readers of our guide on how to look up court case status online in India will recognise the point: people judge a service by whether the thing they came to do actually happened.
Checklist item 2: choose a target that is honest, not perfect
It is tempting to promise that the site will never go down. The Atlas explains why that is a trap: each additional step of reliability can cost around a hundred times more than the one before, and visitors rarely notice. For a small practice, a target such as 99.5 or 99.9 percent of attempts succeeding across four weeks is typically realistic. A 99.9 percent goal permits roughly forty minutes of trouble in 28 days, according to the entry.
Checklist item 3: keep a simple allowance ledger
The permitted failure is called an error budget. Keep it in a plain ledger: total attempts this month, failed attempts, allowance, share used. In the source’s example, 50 million attempts with a 99.9 percent goal would allow 50,000 failures. Your figures will be tiny by comparison, yet the sums work the same way. Check the ledger weekly. If most of the allowance is gone by mid-month, treat it as a signal to pause non-essential changes.
Checklist item 4: agree on a house rule, in writing
This item separates practices that benefit from the idea from those that merely admire it. Write a short paragraph spelling out the consequence once the allowance is nearly spent, for example, no redesigns, plugin changes or new forms until the numbers recover, apart from urgent fixes. Have the senior partner initial it. The Atlas calls an unsigned target an anti-pattern for good reason; a rule that nobody senior accepted will be dropped the first time a deadline looms.
Checklist item 5: decide who gets woken, and when
An advocate’s office does not need a night rota, but it needs to know who looks at an alert and how fast. Avoid notifications for every small wobble. The recommended approach is to alert when the allowance is draining faster than it should: a sharp drop is worth an immediate message to one named person, while a slow leak can be a note for the next working day. Test this once. Deliberately break a test form and check that the right person is told within the time you promised yourselves.
Checklist item 6: count the repetitive chores
Every office has them: re-sending the same confirmation by hand, copying form entries into a register, resetting the same password. The discipline calls that toil and suggests keeping it below half of anyone’s working time, though a survey cited in the Atlas found medians nearer a third. Keep a tally for two weeks. If, for example, 190 of 480 staff hours across six people went to repetitive tasks, that is almost 40 percent, and the biggest item should be automated first.
Checklist item 7: hold a calm review after a bad day
When the booking form fails for an afternoon, resist the urge to find a person to blame. Write a short account of what happened, what made the failure possible and what will change. Give each action an owner and a date. The Atlas notes that blamelessness is about people, not about follow-through, and lists reviews whose actions never close as a common failing. If you want a prompt for which facts to gather, our guidance on the information worth sharing before posting a legal query offers a similar mindset: be specific, ordered and complete.
Checklist item 8: review your own claims about reliability
If your website describes the practice’s services, make sure those words match what you can deliver. A page promising “instant online replies” sets a target by implication. Compare each promise with the numbers in your ledger. For readers assessing professionals online, the piece on what a genuine lawyer profile should reveal notes that clear, checkable statements build confidence.
A note on keeping it light
None of this should become a second job. Fifteen minutes on Friday afternoon is enough for most small practices: open the ledger, glance at the week’s failed attempts, note anything odd and move on. The value comes from regularity rather than volume. If a month passes without a surprise, congratulate yourselves and keep the same rhythm. If three weeks in a row show trouble in the same place, that is the thing to fix before anything else, and the notes you have kept will show exactly where to look.
Scoring yourself
- Seven or eight ticks: your online services are run with real discipline.
- Four to six ticks: sound instincts, but gaps in governance. Start with the signed house rule.
- Three or fewer: you are relying on luck. Begin with item 1 today and add one item a week.
The Monday morning, revisited
Our office manager runs the checklist over a month. She discovers that the appointment form failed on one weekend because of a plugin update, that her ledger shows over half the month’s allowance gone, and that nobody had been told. With a target, a ledger, a house rule and a named contact, the next incident takes twenty minutes instead of two days. Nothing about this is exotic. It is the same careful habit a good practice applies to files and deadlines, aimed at the screen clients actually see.