A busy law office and a well-run IT department have more in common than either would admit. Both receive a stream of requests of uneven urgency. Both depend on deadlines that are not all measured the same way. Both lose time when records are out of date, and both get into trouble when somebody makes a quiet change to something other people rely on. The IT version of this daily discipline is called ITOps. This explainer describes it in plain language and borrows examples from legal practice. It is general information on operations and is not legal advice on any matter.

The plain meaning of ITOps

ITOps is the function that keeps an organisation’s technology services running. It answers requests and incidents, finds and removes the causes of repeated failures, controls changes to systems and keeps a reliable record of what exists. The Ops Atlas entry on ITOps adds an important clarification: the function (the people and roles), the practices they follow and the tools that help are three separate things, and confusion between them is behind many failed projects.

For a legal practice, think of the function as the team that keeps the office working: the person who handles the front desk, the one who looks after the case system, the one who watches filing calendars. The practices are the office rules for how a matter is opened, tracked and closed. The tools are the software they use.

Requests, incidents and problems

Three words that sound alike but are used in different ways.

  • A request covers the predictable asks, say access for a new colleague or a fresh copy of a template.
  • An incident is something broken right now, such as the document system refusing to open files an hour before a hearing.
  • A problem is the underlying cause behind incidents that keep returning.

The ordering matters. In a crisis you restore service by any safe means. Later, when the pressure is off, you look for the cause. Teams that skip the second step end up fixing the same fault every month.

Deadlines and clocks

Legal work runs on clocks, so the clock rules in service management will feel familiar. A promise such as “reply within eight working hours” is not a single number. The Atlas works through one eight-hour customer promise and shows it as a relay: the desk’s first look, a diagnosis stage, an outside carrier’s stretch and a closing buffer. Every leg has its own owner and can be checked on its own.

The same page shows a ticket that was open for 92.5 elapsed hours but counted 4.5 against its target, because a weekend and a holiday paused the clock. Anyone who has counted days for a filing knows that how a period is calculated can matter as much as its length. For any real legal deadline, rely on the governing rules and a qualified advocate. The IT lesson is merely that the counting rules should be written down and visible.

Change control without the ceremony

A change is a deliberate alteration to a system. The framework divides changes into three kinds. Standard changes are pre-authorised and low in risk. Normal changes are assessed first. Emergency changes happen immediately, such as fixing a flaw that attackers are already using, and are reviewed afterwards.

A law office can adopt the same thinking. Updating a letter template that has been changed many times without incident might need no sign-off. Moving the entire matter archive to a new storage system certainly does. Having the categories agreed in advance keeps the office from either freezing or being reckless.

On approval, the Atlas relays research suggesting that outside sign-off does not lower failure rates and that peer review works better, though it also points out that certain European financial-sector rules insist on an independent approver and on sign-off after an emergency change has been made. Whether any such rule reaches a particular organisation is for legal counsel to say.

Records: what is in the cabinet

In IT, the register of systems and how they connect is the configuration database. The legal analogue is the matter register: a list of open files, who is responsible for each, which documents belong to them and when someone last confirmed the details. The reference entry warns against two opposite mistakes: keeping too little and trying to keep everything. A register should hold what decisions need.

A small health check in the entry drives this home: in a ten-row sample most rows looked fine at a glance, yet closer inspection found a pair gone stale, an entry with no custodian and a doubled identifier. A matter register decays the same ways, through old contact details, files with no owner and double entries.

Silent failures

The most uncomfortable section of the reference concerns monitoring. If the alert path fails quietly, the outages it should have announced stay hidden. In an office, the equivalent is a reminder system that stopped sending hearing-date alerts without anyone noticing. A monthly test, where someone deliberately triggers a harmless reminder and checks it arrives, costs almost nothing and protects a lot.

Common mistakes

  1. Applying a heavy process to a small office with a single system.
  2. Treating every change as equally risky.
  3. Adding a rule after every error without ever removing one.
  4. Relying on a private spreadsheet that disagrees with the official record.

Each appears on the Atlas list of anti-patterns, and each is easy to recognise in a professional office once pointed out.

Is a framework needed?

No. ITIL is optional guidance. For organisations that want an audited standard there is ISO/IEC 20000-1:2018, and for small teams a free European framework called FitSM exists. Plenty of small practices get by with one inbox for asks, a short ranking rule, a diary of planned system work and a regular look at what keeps going wrong.

More from this blog

For the court-facing side of operations, a walkthrough on tracking an Indian court case on the internet shows how status information is organised, and a separate article on online consultation for a property dispute describes what an intake process looks like from the client’s chair. Both are helpful for seeing why predictable handling matters.

A day in the life: three small scenes

Scene one: at nine in the morning a junior colleague cannot open the shared drive. It is a single incident, so the person on duty restores access first, then writes down what happened. Scene two: at noon the same colleague asks for access to a new case folder. That is a request, handled through the usual route with the owner’s approval. Scene three: at five, the person on duty notices that this is the third drive fault this month and opens a problem record, assigning someone to investigate next week.

Three different handlings for what looked like one complaint. That separation is the main idea of the whole discipline, and it takes no special software.

Who owns what, and what is somebody else’s job?

The reference entry draws clear borders. Running a live major-incident response, designing the service catalogue, building automated delivery pipelines, correlating alerts with analytics, supporting external customers and applying patches to endpoints belong to neighbouring disciplines. For an office, the translation is practical: decide who handles client-facing communication during an outage, who owns system updates and who watches the alarms. Writing three names on a page is a real organisational achievement. Add a fourth line saying who to call when the first three are unreachable, and you have the beginnings of an escalation path that does not depend on anybody’s memory or goodwill on a bad evening.

The practical takeaway

You do not need to become a technologist to benefit from ITOps thinking. Ask three questions of any service you rely on: who owns it, what happens when it fails and how is it allowed to change? If your office cannot answer them quickly, you have found a small, concrete project for next week.

Leave a Reply

Your email address will not be published. Required fields are marked *

Facebook Twitter Instagram Linkedin Youtube