Support and escalation
Agree which requests your team handles first, which come directly to Subnet and how unresolved issues move between teams. Staff need a clear contact path, and both teams need to know when ownership changes.
IT services
Co-managed IT combines your team’s knowledge of the organisation with agreed support and specialist capability from Subnet. Your team can retain its chosen responsibilities while we take on defined areas of work. The starting point is a clear division of ownership, access, approvals and escalation.
An internal IT team can understand the organisation well and still need help with particular technologies, competing priorities or the volume of daily support. Co-management gives you a way to discuss those gaps without assuming that every responsibility needs to move.
Start with the work that is difficult to cover consistently. It might be a defined part of end-user support, core infrastructure, security operations or a project that needs specialist expertise. Then identify what your team wants to lead and where shared working would be useful.
Agree which requests your team handles first, which come directly to Subnet and how unresolved issues move between teams. Staff need a clear contact path, and both teams need to know when ownership changes.
Define the systems and operational tasks in scope. Record who can make changes, who approves higher-impact work and who is responsible for maintaining the documentation. Existing tool access and integration needs should be checked before the model is agreed.
Give security decisions their own responsibility split. Specify who reviews alerts, authorises action, handles remediation and accepts unresolved risk. Ongoing managed security can be considered through +Security; the coverage and authority still need to be agreed.
Identify where your team needs delivery capacity or technical input. Agree how project decisions, documentation and knowledge transfer will reach the people who will operate the result.
Illustrative example: your internal team remains the first point of contact for staff and owns the business application roadmap. Subnet takes responsibility for an agreed set of infrastructure tasks and provides an escalation path for those systems.
A service issue starts with the nominated team. If it crosses the agreed boundary, that team passes on the relevant information and confirms who owns the next action. A change requiring business approval returns to the authorised person before it proceeds.
The service review can look at unresolved work, recurring issues and whether the responsibility split still fits. This example is a model to discuss, not a fixed inclusion or a promise that every tool can be shared.
List the services your people support today, the tasks they want to keep and the areas that need extra capacity or expertise. Include other providers and any existing escalation arrangements.
For each agreed area, identify the lead team, approvals, access requirements and the point at which an issue is handed over. Set support coverage and commercial terms in the service agreement.
Walk through a typical support request, a significant incident and a planned change. Resolve unclear ownership before relying on the model for live work.
Agree how service issues and changes in demand will be reviewed. Additional scope, tools or projects need a clear approval path rather than an assumption that they are included.
A co-managed arrangement is defined by the work each team owns. The agreement should make it possible to answer a practical question: when something happens, who is responsible for the next action?
Subnet’s published NCVER case study describes collaboration with the organisation’s in-house team across end-user services and core technology management. It also records service delivery management and knowledge transfer between teams.
Read the NCVER case studyYes. The arrangement can reserve strategy, budgets, application ownership and approval decisions for your team while assigning defined delivery tasks to Subnet. Document that authority alongside access permissions so the practical working model matches the agreement.
No. Start with the areas where you need help and agree whether a shared model is suitable. The final scope should identify which requests stay with your team, which Subnet handles and how exceptions are escalated.
It starts with a conversation about what your team supports today and where you need more capacity or expertise. The boundaries for each agreed area are then written down: the lead team, approvals, access requirements and the point at which an issue is handed over. Before the model is relied on for live work, the teams walk through a typical request, a significant incident and a planned change, and resolve any unclear ownership. Scope, tools or projects added later need a clear approval path rather than an assumption that they are included.
Discuss the tools and services you want to retain during scoping. Compatibility, licensing, access and the information needed for support must be checked. Shared visibility does not mean every existing tool can automatically integrate.
Subnet needs the access required for the work that has been agreed. The agreement should record which systems and permission levels are involved, who can make changes and who approves higher-impact work, so your team keeps control of what it has chosen to keep. Existing tool access and integration needs are checked before the model is agreed, because not every tool can be shared automatically.
Agree a lead owner and escalation path for cross-team issues. The handover should include the relevant context, current status and next action. Business decisions and changes beyond the agreed authority stay with the nominated approver.
Yes, it can be reviewed. If you hire, lose a role or want Subnet to take on more or less, the responsibility split can be revisited. The service review can look at unresolved work, recurring issues and whether the split still fits, and additional scope, tools or projects go through the agreed approval path. Subnet’s coverage models are designed to grow or reduce with the customer, although the detail depends on your agreement.
Co-management describes how responsibilities are shared. Foundations is Subnet’s managed IT service, while +Security addresses managed security. The appropriate services and their boundaries depend on the work you want Subnet to own.
Only where they are included in the agreement. Set the project boundary, coverage hours, on-site requirements and any additional charges explicitly. Co-management alone does not define those commercial or service commitments.
Pricing depends on the support scope, number of users and devices, escalation requirements, security inclusions, infrastructure complexity and which responsibilities remain with your internal team.
EXPLORE FURTHER
BEFORE WE TALK
You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.
LET’S TALK
Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.