Boundaries for the Solo Admin

"Just a quick question." It is 17:25. Your coat is on one arm. The person in the doorway is holding a laptop, which is the first sign, and smiling apologetically, which is the second. In the history of IT support no quick question has ever been quick, and most were not questions. This one is about the month-end export, which has stopped working, and the month ends tomorrow.

You will stay. That is not the problem. The problem is that you stayed yesterday. The organization has learned, without anyone deciding it, that the IT department is open whenever the IT department is in the building. This article is part of our One-Person IT series. It is about the boundaries that keep a one-person desk running: not as temperament, but as an operational control, like a backup schedule or a change window.

It covers why boundaries are a control rather than a personality trait. Next come the four boundaries every solo desk needs (office hours, the walk-up redirect, the written emergency definition, and the scope line). Each comes with the exact words to say. Then come how to say no in a way that keeps the job and the manager conversation that makes any of it stick. What happens, slowly, when there are none, and a boundary card with the four scripts follow.

Boundaries Are an Operational Control, Not a Personality Trait

A boundary, on a support desk, is a written rule about when, where and for what the desk can be reached. It exists so that the desk's time is spent by decision rather than by proximity. That is a control, like a change window. It is not a statement about whether you are a helpful person. Helpful people with no boundaries run out of help around month four.

The point is that on a one-person desk you are the capacity. A team can absorb an interrupt; you cannot, so every unplanned request is subtracted from something that was planned. Without a rule, the subtraction is done by whoever is nearest, and the work is chosen by the floor plan. The hallway is efficient at delivering requests. It has never once prioritized one.

The boundaries below are not a wall; they are a door with opening hours and a bell for emergencies. People accept that shape readily, because every other service in their lives has it: the bank, the dentist, the vendor whose support line closes at six. What people do not accept is a boundary they discover by bouncing off it. So each boundary comes with the words to say, and the words always include the alternative.

Without the control, the desk's time belongs to everyone, which is the same as belonging to nobody. That slow collapse has its own section near the end. First, the four boundaries.

Boundary One: Office Hours and the After-Hours Rule

The first boundary is a published opening time for the desk and a written rule for what happens outside it. Office hours are the hours in which the queue is read and tickets are worked, say 08:30 to 17:30. The after-hours rule says that anything arriving outside them gets a ticket number immediately, a human look at the next triage, and an emergency path for the things that cannot wait. Post it in the auto-reply, on the door and on the ticket form, so that nobody learns it by asking.

Do it because a desk with no closing time has no opening time either; it is just a person, available until they are not. Publishing 17:30 means a 17:25 request is logged, acknowledged and seen at 08:30 by a person who slept. That is better for the request than a tired fix at 18:10, and better for every other ticket in the queue.

The words, at 17:25, with your coat on: "I've logged that as ticket 4471, so it's in tomorrow's 08:30 triage and you'll have an update by 09:00. If it's an emergency by the definition on the door, the number is on the sign and I'll come back in." Then ask: "What does it stop you doing, and by when?" The answer puts it in a lane, and the lane decides whether the coat comes off.

If your ticket tool has SLA targets, which are the response and resolution times the desk promises per priority, set its business-hours schedule to match the published hours. QuerySolv's SLA engine excludes non-working hours and holidays from the clock, so a ticket logged at 17:25 has run five minutes by the time triage sees it, not fifteen hours.

What goes wrong without the rule is not one late evening; it is the pattern. Each stay sets the expectation for the next. The expectation becomes a schedule that is never written down anywhere you could argue with it. The organization is not resentful. It is grateful, which is worse, because gratitude is very hard to renegotiate.

Boundary Two: The Walk-Up Redirect

The second boundary is a fixed hour for walk-ups and a sentence that sends every other walk-up to the queue without sending the person away. The hour is the sponge hour from Running Support Solo: one posted hour a day when the door is open and interruptions are the job. The redirect is what you say for the other seven hours. It always gives a route that works now and a time that works soon.

The words: "Happy to look at that. Send it to help@example.com and you'll get a ticket number straight back, or come by at eleven when the door's open. If it's stopping you working right now, tell me what it stops and I'll decide on the spot." Three options, all of them a yes. The person leaves with somewhere to go, which is the difference between a redirect and a brush-off.

Do it because walk-ups are not expensive in themselves; they are expensive at 09:40, in the middle of the one thing that needed two hours. The redirect moves the walk-up to a time when it costs four minutes instead of twenty-four. The person rarely minds, because what they wanted was to be sure it was handled.

The redirect only works if the ticket route is cheap for the requester. If sending a ticket means an account, a password, and a form with eleven required fields, the walk-up wins on effort. QuerySolv's requester portal needs no account and no password; a requester is identified by e-mail address, which is about as cheap as a route gets. The test is whether e-mailing the desk is easier than walking to it.

Without the redirect, the door is the queue, and a queue at a door is sorted by who is standing closest to it. The person who e-mailed at 09:00 waits behind the person who wandered in at 09:40, which teaches everyone to wander in. The queue holds no opinion about this. It just gets longer.

Boundary Three: The Written Emergency Definition

The third boundary is a written definition of what counts as an emergency, posted where the after-hours rule is posted. An emergency is a problem that justifies interrupting whatever the desk is doing, including not being there. The definition says which problems those are, which they are not, and who decides when it is unclear. Without the definition, "emergency" means "important to the person saying it", and everyone is sincere.

Write it as a table with three columns, because people will argue with a paragraph and accept a row. Change the specifics below to match what your organization does for a living, and keep the shape.

The words, when the request does not meet the definition: "That's not an emergency by the definition we published, so it's a Today ticket: done or updated by two o'clock. If I've misread it, tell me what it blocks and we'll look at the table together." The table is the authority, not you. A rule on the wall can be disagreed with politely. A person cannot, at 17:25.

Do it because the definition protects both sides. It gives you a way to say no that is not personal, and the requester a way to say "yes it is" that is not a raised voice. It also keeps the emergency path credible. When every request is an emergency, the real one arrives sounding like all the others.

Without a written definition, the loudest problem is the most urgent one, and the quiet requester with the real deadline loses to the confident requester with a slow laptop. That is not a judgment of either of them. It is what happens when the rule lives in a tired admin's head.

Boundary Four: The Scope Line

The fourth boundary is a short written list of what IT does not do, with the name of who does. The scope line is the edge of the service. The desk supports the company laptops, the network, the applications and the accounts. It does not support personal phones, the coffee machine, the home router, or the spreadsheet one department built and now runs on. Where that line goes is covered in Defining What IT Supports. Here the point is that the solo admin needs the line more than anyone, and needs it in writing.

The words: "That's outside what IT supports, so I'm not the right person, but here's who is. I'll log a ticket anyway so there's a record that you asked." Log it even when you will not do it. That is because the ticket is the only place where "we get asked about the coffee machine nine times a month" can become a fact. Nine is the number at which the coffee machine gets a laminated sign of its own.

Do it because on a one-person desk, scope is capacity. Everything you say yes to outside the line comes out of the line. Nobody sees the trade, because the thing you did not do was invisible. Vendors who sell to larger organizations assume a facilities team and a security team to hand things to. In your organization those teams are all you, which is why the line has to be drawn by you and backed by someone else.

Without the line, the desk becomes the place where anything with a plug goes, and then anything with a question. It grows a reputation for being helpful about everything, which sounds like praise and operates like a second job.

Saying No in a Way That Keeps the Job

A no that keeps the job offers three things in the same breath: the ticket, the alternative, and the time. The ticket says the request is recorded. The alternative says where the person can go now: a knowledge article, the sponge hour, someone else's queue. The time says when the desk will act, as a clock time or a date, never as "soon". Leave any of the three out and the no is heard as a door closing. Include all three and it is heard as scheduling, which it is.

Here is the shape on a Thursday at Northgate Retail, where Lena runs IT alone for a head office of fifty-four. At 17:25 Tomas from finance arrives with the month-end export error and the quick question. Lena asks what it blocks and by when: the month-end close, due to the auditors at noon tomorrow. By the table, a filing deadline inside the next business day qualifies; but triage is at 08:30, which leaves three and a half hours. She logs ticket 4488 at 17:27, tells Tomas "first thing at 08:30, update by 09:00, and if I'm stuck I'll call you", and goes home.

At 08:35 she finds that the export writes to a share that was renamed during last week's server move, and the path in the export job was not. She fixes the path, Tomas runs the export at 08:52, and confirms at 09:05. Twenty-two minutes of the morning, instead of an evening of guessing. Tomas was not kept waiting for anything he needed.

The time is the part most admins skip, and it is the part that does the work. "I'll get to it" is not a time. "By two" is. A no with a time is a promise the requester can hold you to. A no without one is a hope, and the requester will come back to check, in person, at 09:40.

The Manager Conversation

Boundaries on a one-person desk need one person above you to back them, because a boundary only you enforce is a preference. And preferences lose to directors. The manager conversation is a short meeting in which you present the four boundaries as an operational proposal. You ask for two things: approval to post them, and a sentence the manager will repeat when someone complains. The sentence matters more than the approval.

Bring one page with five parts. The problem, in numbers: walk-ups a week, evenings in the last month, how long the project list has not moved. The four boundaries, each in two lines. What you need from the manager: the sentence, and a first-month review date. The risks, honestly: two or three people will dislike it for a couple of weeks, and the emergency definition will be tested in week one.

Ask for the sentence in those words: "When someone comes to you about the sign on the IT door, I need you to say that you asked for it." A manager who will say that has made the boundary an organizational decision. A manager who will not has told you the boundary needs more evidence. The weekly numbers from the operating model are how you get it. The headcount version of the conversation, months later, is When to Hire the Second Person.

Without the backing, the first senior person to walk past the sign walks through it, everyone watches, and the sign becomes decoration. Nobody can hold a boundary alone against the organization's gravity. The conversation comes before the sign.

What Happens When You Have None

The collapse is slow and undramatic, which is why it goes unnoticed by everyone including the person it is happening to. The first month, the day stretches: an extra half hour at the end, because the evening is quiet. The second month, the stretch is the schedule. Lunch is eaten at the desk, then skipped. The project list stops moving, not because anyone said no to it, but because the two hours it needed went on a hundred four-minute favors that each felt reasonable. The queue is triaged by proximity. The admin, who knows this is wrong, has no rule to point at and no time to write one.

By month six the organization has adapted around the shape, which is the kindest and most dangerous thing it can do. People learn the admin is always there, so they stop writing tickets. The queue looks lighter, so the case for help looks weaker. Leave is deferred because nobody else can cover. Nothing is down and every dashboard is green. The person in the middle of this is not failing. They are doing exactly what a system with no boundaries asks of them. Burnout is the plain word for where this goes, and it gets its own series later. Here it is enough to say that boundaries are the control that stops the slope. They are far easier to install in month one than in month eleven. The companion piece is Staying Sane When You Are the Whole Department.

A Short War Story: The Door Sign at Meridian Parts

Marcus ran IT alone at Meridian Parts, eighty staff and one corridor that everybody used. He had tried asking people to e-mail instead of walking up, and it had worked for about a week each time. Then he posted a sign on his door with three things on it. The first was the sponge hour (11:00 to 12:00, door open). The second was the emergency definition in four lines. The third was how to reach him the rest of the time (the help address, and "you'll get a ticket number within a minute"). In the first month the walk-ups outside the hour fell by half, measured by the tickets he logged for them. The ones inside the hour went up. Nobody complained, and when his manager asked why, Marcus pointed out that the sign had never said no to anyone. It said where to go.

I have put up a version of that sign. The first time I left off the emergency line, so people reasonably assumed the door was shut to everything. The second version had the bell on it. It was rung twice in a year, both times correctly.

The Boundary Card

The four scripts fit on a card. Keep it by the door, and read the words aloud a few times before you need them. That is because the first time you say a boundary to someone's face it will come out apologetic. The card is there so that it comes out as a schedule.

THE BOUNDARY CARD
Desk: ____________________   Admin: ____________   Backed by: ____________

1. OFFICE HOURS: 08:30 to 17:30. Outside them, a ticket number at once,
   a human look at 08:30 triage, and the emergency number on the sign.
   Say: "I've logged that as ticket [n]. It's in tomorrow's 08:30 triage and
   you'll have an update by 09:00. If it's an emergency by the definition on
   the door, the number's on the sign. What does it stop you doing?"

2. WALK-UPS: 11:00 to 12:00, door open.
   Say: "Happy to. Send it to help@example.com and you'll get a number
   straight back, or come by at eleven when the door's open. If it's
   stopping you working right now, tell me what it stops."

3. EMERGENCIES: the table on the door decides; the manager if disputed.
   Say: "That's not an emergency by the definition we published, so it's a
   Today ticket: done or updated by [time]. If I've misread it, tell me
   what it blocks and we'll look at the table together."

4. SCOPE: IT supports company laptops, the network, the accounts, the
   listed applications. IT does not: personal devices, [list], [list].
   Say: "That's outside what IT supports, so I'm not the right person, but
   here's who is. I'll log a ticket so there's a record."

EVERY NO CONTAINS: the ticket number, the alternative, the time.
MANAGER'S SENTENCE: "I asked for the sign."   Review date: ____________

Change the hours, the address and the lists. Keep the three things every no contains. Keep the manager's sentence, because the card is only as strong as the name on the Backed by line. Tomorrow at 17:25 there will be a quick question. It will be about the same length as the others. This time you will have the words.

Frequently Asked Questions