The short answer
Fully managed IT: one provider monitors, supports, maintains and secures your systems and users. It fits organizations with no IT staff, or one overloaded non-specialist.
Co-managed IT: your IT person or team stays in charge; a provider adds monitoring, patching, routine tasks, after-hours cover, specialist escalation and projects. It fits organizations that value in-house knowledge but lack capacity or depth.
Both work. Both fail when nobody writes down who owns what.
Side by side
| Fully managed | Co-managed | |
|---|---|---|
| Who leads day to day | The provider | Your internal IT lead |
| Users call | The provider's help desk | Usually your IT team, provider behind them |
| Tools (monitoring, patching, ticketing) | Provider's | Shared, or provider's with your team's access |
| After-hours cover | Provider, for managed-service clients under the agreement | Provider, for agreed systems and alerts |
| Strategy and budget | Provider's vCIO with your leadership | Your IT lead, supported by the provider's vCIO |
| Best when | No IT staff, or IT is someone's side job | One or more IT staff who need backup |
| Main risk | Losing internal knowledge of the business | Unclear boundaries between two teams |
Switching models later
Neither model is permanent: co-managed while you have an internal IT person, fully managed if they leave, or the reverse when you grow enough to hire. Keep documentation, credentials and domain registrations in your organization's name so either move is straightforward.
How to decide
Is IT someone's actual job?
If not, fully managed is usually simpler and safer.
Keep knowledge in-house?
Specialist systems (clinical software, manufacturing controls, custom databases) benefit from an insider.
What is slipping?
After-hours, patching, security monitoring: co-managed fills those. Everything: fully managed.
Will both sides share?
Co-managed needs one ticket system, one set of documentation and named accounts.
The responsibility matrix
A co-managed agreement stands or falls on a clear split. A starting point to adapt:
| Task | Your IT team | Provider | Shared |
|---|---|---|---|
| First-line user support during business hours | Yes | ||
| After-hours alerts and triage | Yes | ||
| Operating system and third-party patching | Yes | ||
| Line-of-business application support | Yes | ||
| New user setup and offboarding | Yes | ||
| Firewall and network changes | Yes (approval by your IT lead) | ||
| Backup monitoring and restore testing | Yes | ||
| Security alert investigation | Yes | ||
| Vendor relationships for core business systems | Yes | ||
| Roadmap and budget | Yes (owner) | vCIO support |
The rows matter less than every row having an owner.
Hypothetical example
A regional distributor with two internal IT staff chooses co-managed IT. The internal team keeps the warehouse scanners, the ERP and user support. The provider takes 24/7 monitoring, patching, backup testing, endpoint security alerts and a Windows server upgrade the team never had time for. A monthly review between the IT lead and the provider's vCIO keeps the list current.
What usually goes wrong
| Pitfall | Fix |
|---|---|
| Two sources of truth (tickets, documents, a password spreadsheet) | One ticket system and one documentation platform; unrecorded means it did not happen |
| Shared admin logins hide who changed what | Named, least-privilege provider accounts with multi-factor authentication |
| A Friday-evening change becomes a 2 a.m. alert | An agreed change process, even a light one |
| The internal team feels displaced | Involve them in choosing the provider and writing the matrix: their job should get easier and more interesting |
| Fully managed, no business contact | Name who approves changes, purchases and priorities |
The Canadian Centre for Cyber Security recommends that individuals have only the privileges they need, and service providers only the access required to manage their services (ITSM.50.030).
Rather talk it through? We can run a short responsibility-mapping session with your IT lead and show which model closes your gaps. Talk to a Promatics specialist
When to bring in help
A stable team, documented systems, a tested backup and holiday cover? You may not need either yet. Bring in a provider when IT staff cannot safely take leave, patching and monitoring lag, or projects wait months. No internal IT? See managed IT services.
How Promatics approaches co-managed IT
- MapA responsibility-mapping workshop with your IT lead.
- OnboardTools and access through separate named accounts, so every action is traceable.
- Share the workYou keep specialties; we take monitoring, patching, routine work, after-hours, escalation.
- ReviewRegular reviews with our vCIO keep the split honest.
Our co-managed IT page sets out the full scope.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Cyber security considerations for consumers of managed services (ITSM.50.030), Canadian Centre for Cyber Security
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.