Do You Need After-Hours Cover at All? Ask the Tickets First

Monday, 09:05, at Meridian Parts. Dana runs a desk of three and has a one-line e-mail from Gareth, the operations director, sent at 07:50: "After Saturday, we need 24/7 IT support. Please propose a rota by Friday." Saturday was the warehouse. The handheld scanners stopped talking to the stock system at 06:40. The dispatch shift stood about for two hours, and the shift supervisor, Len, phoned the four numbers on a laminated card pinned by the loading bay. Two numbers belonged to people who had left. One was the fax. The fourth was Dana's old mobile, which she answered at 09:15 from a supermarket car park. The scanners were back by ten. Nobody enjoyed the morning, and now there is a sentence with "24/7" in it on its way to the budget.

After-hours cover is a promise that someone from IT will respond to a problem outside the desk's published hours. It is a promise about people, which is what makes it expensive. It is usually asked for in a sentence that confuses it with two other things. One is whether the systems stay up at night. The other is whether anyone will fix them if they do not. This article is part of our After-Hours & On-Call Support series. It is about the question that belongs before any rota is drawn: what, specifically, would the person on the phone be for?

It covers the question nobody asks first and why availability is not support. Next comes how to read what actually breaks at night from a desk's own tickets, with a worked example. Then come the expectation that nobody set and what the organisation actually needs. That is usually a number for a fire rather than a desk at midnight. The three honest answers and how to choose between them follow. The scope of the night, a short war story, and the after-hours need assessment to copy come last, in that order.

The Question Nobody Asks First

"We need 24/7 support" is almost never a requirement. It is a reaction, usually to one bad morning. It arrives with the force of a decision because the person saying it has just watched work stop. Gareth is not wrong that Saturday was bad. He is wrong about what would have fixed it, because the sentence he reached for is the biggest available one. The biggest sentence is rarely the right size.

The question before the rota is "what for?", asked twice. The first time it means: which work actually happens outside the desk's hours, and what stops when the technology under it fails? At Meridian Parts the answer is the warehouse, which runs a Saturday morning dispatch shift and nothing else outside nine to six. The second time it means: when that work stops, what does the organisation need to happen in the next hour? Not "IT support", which is a department, but a specific thing: someone who can get scanners talking to the stock system again, reachable by a number that works.

Asked that way, the requirement shrinks from "a desk at midnight" to "a number Len can ring on Saturday morning that reaches a person who can fix the scanners". That is still a real requirement with a real cost. It is just a different one, and it can be met without three people losing one weekend in three. Directors say "we need 24/7" the way people say "we should get lunch sometime". It is a sincere sentence with no diary entry attached.

Availability Is Not Support

Availability is whether the systems are up; support is whether a person answers when they are not. The two are confused constantly, because from the outside they feel the same. "Is IT there at night?" means "will my stuff work at night?" to the person asking. But the mail service runs all night without a technician in the building. So does the stock system, the file service and the phone system. A server does not need a technician to stay up. It needs a technician to come back up, which is a different sentence and a much rarer event.

Most of what people mean by "24/7 IT" is availability. Availability is bought with design and monitoring rather than with a rota. A service that must not fail at night gets a watcher, which is a monitor. This is a program that checks the service every few minutes and raises a flag when the check fails. Whether that flag should wake a human, and how it becomes a ticket, is the subject of Why Alerts Should Become Tickets, Sometimes. The point here is narrower. If the organisation's real need is "the stock system must work on Saturday", the first purchase is a monitor on the stock system and a scanner spare in a cupboard. It is not a person awake at three in the morning in case.

Support, the person answering, is needed when a human has to make a decision or do a thing that no monitor can. The scanners on Saturday needed a person. That was because the fix was to restart a service and re-pair six devices. Nobody on the dispatch shift had the access or the knowledge. That is a genuine after-hours support need. It is one need, on one shift, on one morning a week, and it should be written down at exactly that size.

Read What Actually Breaks at Night

The desk already holds most of the answer, because every ticket carries the time it was opened. Pull every ticket from the last ninety days whose opened time falls outside the desk's hours. Read each one, and sort them into piles by what the organisation needed at the moment it was raised. This takes an afternoon for a small desk. It is the single most persuasive document you will bring to the director, because it replaces the director's sentence with a count. If you run QuerySolv, every request from the web form, the mailbox, chat and the API lands in one queue with the time it arrived. In that setup, the night read is a filter on the queue rather than a hunt through four mailboxes. In any tool, the export with an opened-time column is enough.

Dana did this for Meridian Parts. In ninety days the desk opened 1,140 tickets, and 96 of them were opened outside 08:00 to 18:00 on a weekday. She read all 96 and sorted them as the table shows. The counts are from one fictional desk and will not be yours; the shape of the piles very often is.

Four tickets in ninety days needed a person within the hour. Five more needed a monitor and someone to act on it. The remaining eighty-seven needed the desk to open on time. That is the whole case, and it fits on one side of paper, which is more than can be said for the proposal Gareth was expecting.

The tickets have one blind spot, and you must name it before the director does. They only show what was raised. Len did not open a ticket on Saturday; he phoned a laminated card. The people who gave up and went home are not in the export either. So the read has a second half, which is to ask the people who work outside hours directly. Ask the dispatch supervisor, the night cleaners' manager, the finance person who runs month-end on a Sunday. One question does it: "In the last three months, what happened outside office hours that you could not get help with?" Write the answers down as if they were tickets, add them to the piles, and the count is honest.

The Expectation Nobody Set

Meridian Parts had no published support hours, which meant it had an expectation instead. The expectation was set by accident. Three years earlier Dana had answered her mobile at nine on a weeknight and fixed something. From that night the warehouse believed IT was reachable at any hour. The laminated card was the physical form of that belief. Nobody had promised anything. Nobody had declined to, either, and in the absence of a promise people assume the most convenient one.

An unset expectation is a promise the organisation thinks it has been given and the desk does not know it has made. It is the most expensive kind, because it is only discovered when it is broken. Saturday was not a failure of after-hours cover. Meridian Parts had no after-hours cover to fail. Saturday was the morning the unset expectation met reality, and reality, as usual, had the fax number.

The fix for an unset expectation is a set one: published hours, a published route for the exception, and a plain statement of what the exception is for. Which promises a desk should make and which it should refuse is the subject of What to Promise and What Never To. After-hours is the clearest case in it. A desk that says "we are open 08:00 to 18:00, and outside those hours this number reaches a person for work that has stopped" has made a small promise it can keep. A desk that says nothing has made a large promise it cannot.

What the Organisation Actually Needs

Strip the director's sentence down to the needs under it and there are four, and none of them is a desk at midnight. The organisation needs a number that reaches a person when work has stopped. It needs a way to log everything else so that the morning starts with it rather than discovers it. It needs the promise written where people can find it. And it needs the services that must not fail watched by a machine that tells someone when they do. Each of these is cheaper than a rota, and together they cover almost every ticket in Dana's table.

The number for stopped work is the heart of it. One published number, answered by a person with access, used for the four-in-ninety-days kind of problem and nothing else. For a desk of three this is usually the lead's phone, or a phone that passes between two senior people. It rings a handful of times a quarter. The coverage models that make this real, from the single number up to a full rota, are drawn as week grids in the coverage models for a small team. The choice between them starts from the count you have just made.

The logging route is the cheap half that nobody budgets for. The forty-one evening e-mails in the table were already handled well, because they arrived in the queue and were answered at nine. The dispatch shift's six lockouts were not, because the dispatch shift did not know the queue existed. A form on the portal, a mailbox address and a line on the laminated card's replacement turn the night's non-emergencies into the morning's first tickets. The line says "for anything that can wait, raise it here and it will be first in the morning". Nobody is woken. Nothing is lost. The desk opens at eight with a list rather than a rumour.

The monitor covers the five alert tickets, and it is the only item on the list that costs money rather than agreement. A service that must not fail at night, at Meridian Parts the stock system and the order import, gets a check and a route for the check to reach a human. Whether that human is woken or finds it at eight is a decision you make per service. The mechanics live in the monitoring series. For the need assessment it is enough to list the services and decide, for each, whether anyone should be woken for it. Most of the answers are no. That is not a failure of ambition. It is a Saturday.

The Three Honest Answers

Once the count is made, the answer to "do we need after-hours cover?" is one of three. The table gives the signal in the data that points to each. The first answer is no: business hours only, published, with a logging route and a monitor on the services that matter. This is the right answer for a desk whose night read shows nothing in the bottom row of the table. It is a more common answer than directors expect. The second is a number only, which the next article calls the escalation-only model. This is a single published route that reaches a senior person, for work that has stopped and nothing else. The third is a rota, where someone carries a phone for a week at a time. A rota is justified when the bottom two rows of the table fill up faster than one person's goodwill can cover.

The honest answer can change, and should be re-read once a year or whenever the business adds a shift. Meridian Parts' count pointed firmly at the second row. A number for Len, a monitor on the stock system and the order import, a logging route for the dispatch shift's lockouts, and no rota. If the warehouse adds a Sunday shift next year, the count is run again and the answer may move down a row. Nothing about the decision is permanent except the habit of counting before deciding.

The Scope of the Night

Whatever the answer, the night's scope is narrower than the day's. It has to be written down or it will grow to fill the available goodwill. The day desk supports everything on the published list. The night number supports work that has stopped, for people whose work is scheduled at that hour. It does not reset the password of an office worker who decided to catch up at eleven at night. It does reset the password of the dispatch supervisor whose shift cannot start without it. The difference is not the person's importance. It is whether the organisation scheduled the work.

The scope question is the same one the desk answered for its daytime catalogue. The method is in Scope Boundaries: say what is in, say what is out, and say what the person should do instead. The after-hours version is shorter, because the "in" list is tiny. The "instead" is the logging route, and it carries most of the night's traffic. What counts as an after-hours call, with examples and the awkward cases, has its own article later in this series. For the need assessment, write one sentence: "The after-hours number is for work that has stopped for a scheduled shift or a service the business depends on overnight." Then list the shifts and the services. If the list is empty, you have your answer.

What a Rota Costs, in People

If the count does point at a rota, the proposal to the director has to carry the cost in the currency that matters. For a small desk, that is not money but people. A three-person rota means each person carries the phone one week in three. They cannot travel, cannot drink, cannot be out of signal, for a third of the year. A rota means a night call followed by a morning that should be protected, which the day desk then covers one person short. It means someone keeps the rota, handles swaps and holidays, and notices when one person has had three bad weeks running. The principles that keep a rota fair and therefore staffed are in Compensation and Recovery Time. Those principles are not optional extras to be added once the rota "settles in". A rota without them settles in by losing people.

Put that cost beside the count. "Four events in ninety days, each resolved within two hours by one person with access" is a sentence that argues for a number. "Three people losing a third of their evenings and weekends to answer four calls a quarter" is the same sentence from the other side. It is the one the director has not yet heard. Most directors, shown both, choose the number. The ones who still want the rota usually know something about next year's shifts that you do not. That is worth asking about before Friday.

A Short War Story: The Director's Sentence at Ashgrove Housing

Ashgrove Housing ran a tenants' emergency repairs line around the clock. When the IT desk of three was set up, the finance director said in a meeting that "IT must be 24/7 too, same as repairs". The sentence became a rota before anyone asked what the repairs line actually needed from IT at night. For two years the three technicians each carried the phone one week in three, with no written definition of what it was for and no time back for a bad night. Priya, the most senior of the three, kept her own tally. The phone rang thirty-one times in the second year. Twenty-six calls were for passwords and a printer in the repairs office, and three were for something the repairs line could not work without. In the third year Priya left. Her resignation note said, in one line, that she had not had a free weekend she could plan around in two years. The desk hired her replacement in four months and lost most of what she knew in the meantime. It replaced the rota with a single number held by the lead and a monitor on the repairs system. There was also a line on the repairs office wall saying what the number was for. The phone rang five times the following year. The lesson the lead wrote in the review was that a sentence spoken in a meeting had cost a senior technician. The review also said that nobody had ever counted what the sentence was for.

The After-Hours Need Assessment

The sheet below is the one Dana filled in for Gareth. It is designed to be completed in one afternoon from the ticket export and three conversations. Sections A and B are the count. Section C is the list of shifts and services that genuinely run outside hours. Section D is the answer, picked from the three, with the reason in one line. Section E is what gets set up whichever answer you pick, because the logging route and the published hours are needed even when the answer is no. Fill it in before the rota conversation, attach it to the proposal, and re-run it when the business changes its hours.

AFTER-HOURS NEED ASSESSMENT — ONE PAGE
Desk: ______________________   Completed by: ______________________   Period read: ____ days

A. THE TICKET READ (every ticket opened outside published hours)
   Published hours today: ______ to ______, days: ______________
   Tickets opened outside those hours in the period: ______ of ______ total
   Sorted by what the organisation needed at the time:
     Could wait until morning, no cost ................ ______
     A person stopped working until morning ........... ______
     A monitor and someone to act before morning ...... ______
     Work stopped for a group; a person within the hour  ______
   Notes on the last two rows (what, which shift, how long): ______________________

B. WHAT WAS NEVER RAISED (ask the people who work outside hours)
   Asked: ______________________  ______________________  ______________________
   "In the last three months, what happened outside hours that you could not get help with?"
   Events described, added to the rows above: ______

C. WHAT RUNS OUTSIDE HOURS
   Scheduled shifts and their hours: ______________________________________________
   Services the business depends on overnight: ____________________________________
   For each service: should anyone be woken if it fails? yes / no  ______________

D. THE ANSWER
   [ ] No after-hours cover   [ ] A number only   [ ] A rota
   Reason, one line, from the count: ______________________________________________
   Re-read on: ____________ or when a shift is added

E. SET UP WHICHEVER ANSWER
   [ ] Published hours, where everyone can find them
   [ ] A logging route for the night: form / mailbox / portal, first in the morning
   [ ] A monitor on each service listed in C
   [ ] The after-hours number, if any, and one sentence saying what it is for
   [ ] The old numbers taken down, including the laminated ones

Dana's proposal went to Gareth on Thursday, a day early, and it did not contain a rota. It contained the table, the four events, the two shifts, and the second row of the answers. That meant a number held by Dana and her most senior technician in alternating months. It also meant a monitor on the stock system and the order import, and a form for the dispatch shift. And it meant a new card for the loading bay with one number on it and one sentence underneath. Gareth read it, asked whether the number would be answered on Christmas morning, was told yes, and signed it. The fax number came down the same afternoon. It had been answering, in its way, for three years.

Frequently Asked Questions