Co-Managed IT Works When Everyone Knows Who Owns What

Co-managed IT is a simple idea. You keep your internal IT person, or the office manager who became the IT person, and an outside team takes the work they can’t get to: security monitoring, patching, after-hours coverage, the projects that keep slipping. Done right, your person gets backup and your business gets depth it couldn’t afford to hire.

Done wrong, it creates a new problem. Two groups each assume the other one has something covered, and nobody does.

Write the split down

The most important thing you can do is put ownership in writing before anyone touches anything. Not a vague statement of work. A list. Who handles new user setup? Who approves firewall changes? Who patches the servers, and on what night? Who’s on call when email goes down at 7 p.m.?

Most co-managed problems I see trace back to a task that was never assigned. Backups are the classic one. Everyone assumed they were running. Nobody was checking.

Use one ticket system

If your internal person tracks work in their head and the outside team tracks it in their own system, nobody has the full picture. Put everything in one place where both sides can see it. That’s also how you find out where the time is going, which tells you whether the split is right.

Agree on escalation before you need it

Decide now what counts as urgent and who calls whom. When a machine starts acting strange on a Friday afternoon, your person shouldn’t be wondering whether this is something they handle or something they hand off.

Settle admin access early

Who holds the global admin accounts? Where are the passwords kept? What happens to access if either side leaves? This conversation is awkward, so it gets skipped, and skipping it is how businesses end up locked out of their own systems.

Meet monthly

Thirty minutes a month to review open tickets, upcoming projects, and anything that fell through the cracks keeps the relationship honest. It also gives your internal person a voice in the plan instead of feeling replaced by it.

Protect your internal person

Co-managed shouldn’t be a slow replacement. The best setups make the internal person more valuable: they keep the relationships and the business knowledge, and they stop being the single point of failure. If you’re weighing this, read what happens when IT has a day job, and see how it played out for a bakery machinery company that kept its internal team and added coverage around it.