How to Delegate as a Business Owner: MSP Desk Handoffs

What Actually Only You Do?

For one week, every time a request comes to you, log it. Note who resolved it, whether it went through you first, and whether the task was 'owner only' or 'handoff possible'. You'll probably be surprised, and the surprise is the point.

Record the count for each task in that same log. I'd try the highest-count repeatable task with a written procedure and a recipient who has room for it, then compare owner touches before and after the handoff. If that count hasn't fallen, I wouldn't add the next task yet; check why work still returns.

One operator reported that, after offering mailbox access instead of a password, repeated requests to add and remove mailboxes created a flood of support tickets. The operator described finding the automap feature as the fix. For your audit, keep mailbox permission requests as an illustrative category: check whether they reach you because the team lacks a procedure or clients expect you to answer.

The week's log gives you two things: a list of what only you do, and a list of what your team already handles without you. The second list matters almost as much as the first, because it shows what is already working.

If you find yourself on every ticket, that's the answer too. But if the team is already at full workload, handing off tasks isn't enough. You either hire or shift priorities, because reassigning work into a full queue just moves the bottleneck.

Start Handing Off the Easiest Tasks First

Pick the tasks that are simple, low-risk, and repeatable. Mailbox access changes, password resets, basic monitoring alerts. Not client communication, not the hard stuff, not yet.

Here's the sequence I'd use: document the process in one page, train one person on it, have them do it with you watching, then let them do it alone. That's it. No training manual, no LMS course, no six-week rotation.

Say you run a twelve-person MSP and the audit shows mailbox permission changes hit your desk six times a week. You write a one-page checklist: how to grant access, how to remove it, what to check after, who to tell. You train your most capable tech on it. They do the next one while you watch. By the third one, they're doing it alone.

The order matters more than the speed. Low-risk routine tasks first, then monitoring and routine maintenance, then client-facing communication. Each stage earns the next.

Where the Handoff Falls Apart

The approach fails in three places, and it's worth naming them once so you can see them coming.

• You bypass the plan when the pressure hits. A client calls, you take over, the tech backs off, and a week later they're back to escalating everything to you. The training is undone in one afternoon.
• The team is understaffed for the work, or isn't willing or ready to take it on. Check available capacity and hire or shift priorities before adding work to a full queue. Handing off tasks to a team that sees it as extra work without any reward is a short path to resentment and quiet failure.
• The tasks weren't actually simpler than they looked. If the first handoff needs judgment calls every time, it wasn't the right task to start with.

The fix for the first one is commitment: you don't take a handed-off task back unless the tech is stuck, and even then you walk them through it instead of doing it. The fix for the third is in your audit: choose the most routine, least ambiguous tasks first, and leave the rest for later.

This is also where documentation lives or dies. If there's no checklist, there's no handoff, there's just hope. A one-page process isn't a luxury, it's the thing that lets a junior tech do the work without you.

Use the Freed Hours to Work on the Business, Not in It

The whole point of the handoff isn't to make your day calmer, though that happens. It's to give you hours for sales and planning, the work that has no ticket and no due date and so never gets done.

Block the time on your calendar. Two hours every Thursday, say, or one morning a week. Treat it like a client meeting: don't move it, don't cancel it, don't answer the phone during it.

And be honest about the size of the block. If the handoff gives you three hours a week, that's three hours of real sales work, not a magic number that transforms the business overnight. Small blocks still need protection, because they're the only ones you're likely to get.

What goes in those hours is yours to decide. Review the pipeline, plan a marketing activity, call a prospect you've been meaning to call. The point is that it isn't reactive and it isn't the desk.

What to Do on Monday Morning

On Monday, start the one-week audit. Every request that hits your desk gets logged, and you mark it owner only or handoff possible. At the end of the week, you'll have the list that starts everything else.

Then schedule a team meeting and explain the plan. Not a big speech, just the shape: I'm going to write down what I do, we're going to move the easy stuff to you, and you'll have a checklist and my backing when you do it.

If your week looks like the mailbox-permission pattern above, that list will be mostly mailbox permissions and password resets. That's fine. That's where the first handoff starts.