Let’s discuss your project ↗Contact ↗
Practical guide

How to define your managed IT scope

Before entrusting your IT to a provider, gather the information needed to clarify the services and each person’s role.

Clarify the scope.

  • Equipment and users
  • Tasks and responsibilities
  • Priorities and constraints

1. Describe your IT environment

List approximate numbers of workstations, servers, networks and cloud tools. Identify the locations, users and equipment already managed by a service provider. A simple overview is enough to start; further details can be gathered later.

2. Separate needs from tasks

Describe observed difficulties rather than an assumed solution: equipment to replace, recurring problems, user requests or backups to review. Distinguish one-off work from ongoing upkeep. Prioritise issues according to their effects on your teams’ work.

3. Clarify responsibilities

Identify your internal contact, service providers and the people who approve work. Clarify available access, who authorises changes and the information expected after an intervention. For backups, identify the data involved, where it is stored and the checks currently planned.

4. Prepare a concrete request

Start with this summary, without sharing any passwords:

  • Your business, locations and approximate number of workstations.
  • Servers, cloud tools and current service providers.
  • Three priority difficulties or planned changes.
  • Tasks to delegate and those kept internally.
  • Timelines, access constraints and project contacts.

This summary helps us discuss the scope. Services and support arrangements will be defined with you.

5. Compare proposals on the same scope

Two managed IT proposals may cover different needs. Compare the equipment, users and tasks included, then identify any work that would require an additional intervention.

  • Support: which users, service hours and contact channels are included?
  • Interventions: which tasks can be handled remotely and which require an on-site visit?
  • Timing: does the stated time refer to acknowledging the request, starting work or resolving the issue?
  • Backups: which data is covered, who checks completion and how will a restore test be organised?
  • Reporting: what information will be shared about incidents, changes and next actions?
  • Transition: which documents and access arrangements are needed at the start and when changing providers?

6. Prepare a practical scoping brief

Complete an initial version with your IT contact. Mark information that is not yet known as “to be checked”. The aim is to make open questions visible, rather than to carry out a technical audit on your own.

  • Organisation: business activity, locations, main contact and people authorised to approve interventions.
  • Equipment: approximate numbers of workstations, servers, printers, network devices and cloud tools.
  • Essential uses: the applications and services your teams need to work.
  • Current situation: existing providers, recurring difficulties and planned changes.
  • Requested scope: tasks to outsource, tasks retained internally and identified exclusions.
  • Priorities: the practical impact of incidents, deadlines and intervention constraints.

7. Agree on responsibilities before starting

Ask for the division of responsibilities and unresolved points to be written clearly. For example, “supporting workstations” does not by itself identify who manages user accounts, licences or business applications. Separate these topics so that everyone shares the same expectations.

Let’s discuss your IT equipment.

Describe your environment and priorities in the contact form and select “Managed IT services”.