Intelligent IT Operations
Managed vs. co-managed IT: who should own what?
With managed IT, a provider takes on an agreed set of work. With co-managed IT, you split that work with your own IT team. The right choice depends on who you have, and what they have time for.
People often compare these two models as if they were packages on a menu. They’re really two ways of dividing responsibility, and the details that matter (which apps are covered, when help is available, who signs off on changes) only show up in the agreement.
List the work first
Before you talk to any provider, write down the work that keeps your business running: helping employees, looking after laptops and servers, managing applications, making security calls, dealing with vendors, and planning ahead.
Then, for each item, ask who does it today and whether they actually have the time, information and authority to do it well. That list tends to show you which model fits.
It also heads off two common surprises: assuming managed IT covers everything, and assuming co-managed means extra help on demand. Both need clear boundaries to work.
How the two models differ
In a managed arrangement, the provider handles the routine work you agree on. Your business still sets priorities, approves access and purchases, and keeps anything you’ve chosen to hold on to.
In a co-managed arrangement, your internal team keeps named responsibilities and the final say on decisions, and the partner takes defined work or escalations. The handoff between the two teams, and any other vendors, needs to be spelled out.
Either way, settle a few things up front: who the escalation contacts are and what they can decide, whether planning and roadmap reviews are included, who owns security and recovery, and how new users, systems and projects get added.
Two situations
A good test is to walk a provider through a real request, like a new starter, an application that keeps failing, or an urgent maintenance decision, and ask them to explain who does what. Compare their answer with what’s in writing.
Questions to ask a provider
- Which users, devices, locations and applications are included?
- What are the support hours, and where does escalation stop?
- What do we stay responsible for?
- What happens when a problem involves another vendor?
- Which projects and changes fall outside the monthly service?
- How will reports show what’s still unresolved?
- How are onboarding, access approvals and changes to the scope handled?
Think about the first month too
Whatever split you choose has to work during onboarding as well as once things settle down. Existing contracts, who owns which accounts, missing documentation and how access gets handed over all affect the plan. A signed contract doesn’t resolve those on its own.
The worksheet below helps you spot work that’s clear, unclear or overloaded today. Use role names, and keep passwords and system details out of it.
Technology responsibility worksheet
Fill this in with colleagues. Use role names, never passwords or account details.
| Work or decision | Current owner | Clear, unclear or overloaded? | Proposed next step |
|---|---|---|---|
| Employee support | |||
| Device and server upkeep | |||
| Application administration | |||
| Access approval | |||
| Security escalation | |||
| Backup and recovery | |||
| Vendor coordination | |||
| Technology planning |
Keep your completed notes within your own team.
Talk to us
Not sure which model fits?
Tell us who handles IT today and where things get stuck. We’ll tell you which arrangement we’d suggest, and why.
Explore Intelligent IT Operations
- sales@altivusone.com
- Phone
- (346) 410-0961
- Office address
- 151 FM-407
Suite 200
Argyle, TX 76226
Thank you. Your message has been sent.
Someone from our team will be in touch.