Skip to content
+90 850 885 27 43 info@argeict.com

Article · Management

Dividing IT work between your team and a provider

A small IT team struggles to run daily support, infrastructure maintenance, and security monitoring at the same time. This article gives IT managers criteria for deciding which work to keep in the team and which to hand to a provider.

ARGE ICT · Published November 11, 2026 · Updated November 15, 2026

An IT manager usually handles user requests, infrastructure maintenance, security monitoring, and projects with the same team. Keeping all the work in the team weakens project delivery, and handing all of it over weakens the organization's own knowledge. Setting the criteria for the split in advance avoids both outcomes.

Work that should stay with the team

Some work needs knowledge of the organization, and the responsibility for some of it cannot be handed over. This work stays in the team:

  • Relationships with business units and prioritizing requests
  • Architecture decisions and standards
  • Budget, supplier, and contract management
  • Process knowledge of business applications
  • Information security policy and risk acceptance

Relationships with business units decide which requests the team takes up first. Architecture decisions and standards set the frame in which the provider works, and budget, supplier, and contract management keep the cost and length of the outsourced work in the organization's hands.

Process knowledge of business applications can be passed to a provider, but it is used together with the knowledge that stays inside the organization. Risk acceptance is the clearest case: deciding which risks the organization will live with belongs to the organization, not to the party doing the work.

Work that can be handed over, and decision criteria

In most organizations, the following work can go to an outside provider:

  • Monitoring outside office hours
  • Backup operations and restore testing
  • Updates and patching
  • Monitoring of security logs
  • Operation of the network and firewalls
  • First-level user support
  • Rarely needed specialties: database administration, SAP Basis, penetration testing

Five questions help decide whether a task can be handed over:

  • Is the task repetitive and can it be described in writing?
  • Does it have to be done outside office hours?
  • Does it depend on a single person in the team?
  • Is the expertise needed for only a small part of the year?
  • Can the result be measured?

Monitoring outside office hours, for example, is repetitive and in a small team can end up depending on one person. For expertise needed during only a small part of the year, calling in a specialist when needed can suit better than creating a position.

The more of these answers are yes, the better suited the task is to outsourcing.

Responsibility matrix

A responsibility matrix (RACI) names four roles for each task: who does the work, who approves it, who is consulted, and who is informed. In backup operations, for example, the provider does the work, the IT manager approves, application owners are consulted, and management is informed.

For updates, the provider carries out the work, and approval comes from whoever permits the change window. Tasks that tend to end up without an owner are marked separately in the matrix. These are certificate and domain renewal, license renewal, monitoring of backup alerts, and closing the accounts of employees who leave.

Once the matrix is written, it is read through with the provider, and each row is checked to confirm that it has a name beside it.

Contract terms to look for

The full list of contract terms is in What are managed IT services?. Three of them matter most to an IT manager.

The first is the provider's access: each member of the provider's staff gets a named account, multi-factor authentication (MFA) is enforced, and actions are logged. The second is the content of the report and the source of its measurements, with a written statement of which data produces which indicator. The third is exit and handover, meaning the return of documentation and administrator accounts to the organization when the contract ends.

Knowledge transfer and documentation

The network diagram, inventory, password manager, and runbooks are kept somewhere that belongs to the organization. Every change the provider makes is recorded in these documents.

In the periodic review meeting, the team and the provider go through the open items and the measurements together. Responsibility to management for the work that was handed over stays with the IT manager. A handover does not remove the duty to oversee the work.

Expert call on dividing IT work

Share the work your team runs today and the areas that take the most time; we respond to your request within one business day.

Speak to an expert