What Does Co-Managed IT Actually Look Like Day to Day?

Co-managed IT is close to exactly what it sounds like. Your existing IT hire keeps their job, their relationships, and their daily routine, and an outside partner, ACT360’s Co-Managed IT Services team in this case, fills in around them. Most explanations stop right there, at the org chart, and never get to the part that actually matters to the people living it: the ticket queue.

If you’re trying to figure out what co-managed IT changes about a normal week at your business, the org chart isn’t where the answer lives. The answer lives in who your team calls first when something breaks, what gets escalated and to whom, and what happens the night a server throws an alert with nobody awake to see it.

This article walks through what a real co-managed engagement looks like once the paperwork is signed. The daily split of work, how requests actually get routed, what changes in the first few months, and what a routine Tuesday looks like next to a 2 a.m. outage. For the fuller breakdown of what’s included, pricing, and who it fits best, ACT360’s Co-Managed IT Services page covers that. This one is about the mechanics.

Co-managed IT is a shared arrangement where your internal IT hire, whether that’s one person or a small team, keeps ownership of the day-to-day relationship with your staff, and an external partner covers a specific, defined set of gaps: after-hours coverage, specialized security work, overflow during projects, and strategic input your internal hire doesn’t have the bandwidth or scope to provide alone.

It sits between two other paths. Standalone IT support is a helpdesk relationship on its own, with an outside provider as the primary contact for every request. Full Managed IT hands over the entire relationship, monitoring, security, vendor management, and strategy under one roof, usually because there’s no internal hire to begin with. Co-managed IT assumes the internal hire already exists and is good at their job. It just isn’t realistic for one person to be the only line of defense, the security specialist, the after-hours contact, and the vendor negotiator, all at the same time.

That’s part of why more growing businesses are looking at co-managed arrangements instead of a second full-time IT hire. Nearly seven in ten small businesses in Canada now say a shortage of qualified candidates in their sector is the top obstacle to hiring, according to the Canadian Federation of Independent Business. The Information and Communications Technology Council has separately projected sustained demand for digitally skilled workers in Canada that continues to outpace supply. Waiting months to fill a second IT role isn’t realistic when the gap needs covering now.

This is usually the first thing people want mapped out, and it’s rarely as clean as an org chart makes it look. Here’s how the work typically splits once a co-managed arrangement is actually running:

The exact split gets confirmed during the IT Readiness Assessment, not guessed at from a template. A business with one strong generalist hire and no security specialist will scope differently than a two-person internal team that just needs after-hours coverage.

Almost always, the same person they already call. That’s the point. Co-managed IT is built to be invisible to most of your staff, not a second helpdesk they have to figure out.

Here’s how a request typically moves through a co-managed setup:

1. An employee has a problem and calls or messages your internal IT hire, the same as always.
2. If it’s routine, your hire handles it directly. Nothing changes.
3. If it’s outside their specialty, security-related, or happens after hours, they escalate to a named ACT360 contact, Adam or Jeffrey, not a rotating queue.
4. ACT360 works the issue and reports back to your hire, who stays the point of contact for your staff.
5. Anything that needs to happen outside business hours routes directly to ACT360’s after-hours coverage, so nobody’s waiting until Monday.

The one exception is anything explicitly scoped as ACT360’s to own outright, like after-hours monitoring or a specific security tool. In those cases, staff get told upfront who to call, so there’s no confusion about which door to knock on.

Here’s what that split tends to look like once it’s running, not in theory, but as a week actually unfolds.

Monday morning usually starts the same way it did before co-managed IT existed. Your internal hire handles the weekend’s leftover tickets, sets up a new hire’s laptop, and fields the usual run of small requests. ACT360 isn’t visible in any of it, because there’s no reason to be.

Midweek is where the difference tends to show up. Say a vendor calls about a contract renewal, or a firewall needs a configuration review nobody’s had time to do properly. That’s usually the moment your internal hire flags it to their ACT360 contact instead of either ignoring it or trying to become a security specialist overnight. The work gets scoped, scheduled around production hours or business needs, and handled without pulling your hire off their regular workload.

Thursday night, after hours, is the scenario most businesses are actually paying for, even if it rarely happens. A server throws an alert at 11 p.m. Under a co-managed arrangement, that alert routes to ACT360’s monitoring, not to your internal hire’s personal phone. Having a defined incident response path in place before an incident happens, rather than improvising one at midnight, is exactly what the Canadian Centre for Cyber Security recommends for businesses of any size. Depending on severity, the alert either gets resolved overnight or your hire gets a clear summary Friday morning instead of a surprise.

Quarterly, the pace changes again. ACT360 and your internal hire sit down for a review that isn’t about ticket counts. It’s a look at what got handled, what’s coming up, whether the current split of responsibilities still makes sense, and whether anything needs to shift as the business changes. That’s also usually when a business finds out whether it’s outgrown a co-managed arrangement and is ready for something bigger, or whether the current scope is still the right fit.

The first few weeks look less like a cutover and more like an interview. ACT360 spends time understanding what your internal hire already owns well before touching anything: which systems they’re confident in, where the actual gaps are, and what’s been quietly labelled “fine” because there’s never been time to look closer.

From there, access gets set up gradually rather than all at once, typically starting with documentation and monitoring tools before anything higher-stakes changes hands. A first specialized project, often a security review or a piece of infrastructure that’s been on the back burner, usually gets scheduled somewhere in the first 60 to 90 days once both sides know how the other one works. There’s no big-bang cutover weekend, because there’s nothing to cut over. Your internal hire’s day-to-day doesn’t stop while any of this happens.

Usually less than people expect at first, and it grows as trust and scope do. A typical starting point includes shared visibility into the ticketing or documentation system, so nothing gets solved twice, plus access to whatever monitoring or security tooling ACT360 is running in the background. Full administrative access to every system is rarely handed over on day one. It’s scoped to whatever the engagement actually covers, and it expands only when the work calls for it, not by default.

A few honest signals tend to separate an arrangement that’s working from one that’s just adding a second invoice.

It’s working when:

• Your internal hire still feels like the owner of the relationship with your team, not sidelined by it.
• After-hours issues get handled without anyone losing sleep over a phone that used to ring at midnight.
• Specialized work that used to sit on a to-do list indefinitely, a migration, a security hardening project, actually gets scheduled and finished.
• Quarterly reviews surface real recommendations, not a list of closed tickets.

It’s not working when:

• Nobody defined upfront who owns what, so issues get handled twice or missed entirely.
• Your internal hire feels like they’re being quietly phased out instead of backed up.
• Escalations disappear into a general queue instead of reaching a named contact.

Most of what causes the second list isn’t a flaw in the model. It’s a scoping conversation that didn’t happen clearly enough at the start, which is exactly what the assessment step is supposed to prevent.

ACT360’s approach to co-managed IT runs on the same ACTION methodology behind every engagement: understand what’s already working before recommending anything. For a co-managed arrangement specifically, that means the Assess and Comprehend steps focus on your internal hire’s existing strengths, not a generic checklist, so the scope fills real gaps instead of duplicating work that’s already handled well.

A named contact, Adam or Jeffrey, coordinates directly with your internal hire rather than routing everything through a rotating support queue. That matters more in a co-managed setup than almost anywhere else, since the relationship between your internal hire and ACT360 is what determines whether the split actually holds up under a real incident, not just on a slide during the sales conversation.

ACT360 provides day-to-day co-managed IT coverage to growing businesses across Barrie, Newmarket, Orillia, Aurora, Innisfil, Markham, and Vaughan, plus the surrounding communities across Central and Southern Ontario.

Co-managed IT works when the split is specific, the escalation path is clear, and your internal hire feels backed up instead of watched. It doesn’t work when nobody defined any of that upfront. If you’re still deciding whether the model itself is the right call for your business, not just how it runs day to day, ACT360’s breakdown of when co-managed IT makes sense and when it doesn’t is the better starting point.

If you already know co-managed IT is the direction you want to go, the next step is figuring out exactly where the gaps are. An IT Readiness Assessment is a 30-minute, no-obligation look at what your internal hire already handles well and where a co-managed arrangement would actually help.

T: 705-739-2281 E: [email protected]