Skip to main content

Article

What does your managed IT provider actually cover?

Your managed IT provider covers what your agreement actually says, not everything that might go wrong with technology. Support can vary by site, device, service, hours and task. A provider may maintain an account without being responsible for backing up its data or restoring it after an incident.

Use this guide to map responsibilities with your provider and your own team. It is useful whether you are comparing providers or reviewing an existing arrangement. The contract, service schedule and agreed changes are the starting point; ask for written clarification when they are unclear.

Make a coverage map

List each important service or asset on a separate line. For each one, record: what is included, excluded or conditional; who does the work; your business owner; when or how often; evidence; and the next action. Mark anything not confirmed as “unknown”, not “covered”. Identify the relevant agreement or quote beside each answer.

  • Sites and assets: Which offices, servers, laptops, network equipment and remote or personally owned devices are listed? Are new devices automatically included or only after approval?
  • Accounts: Who approves new starters, changes and leavers? Who creates, changes and removes access, including supplier and administrator access?
  • Security: Who configures multi-factor authentication, applies updates, watches alerts and acts on them? Note any systems or hours excluded.
  • Backup and recovery: Which data and systems are protected, who checks failures, and who can restore them? See the recovery questions below.
  • Licences and suppliers: Who buys, renews and administers each subscription? Who contacts the internet, phone, software or cloud supplier when a fault crosses service boundaries?
  • Support and change: Which requests are routine support, and which require a separate quote or approval? Record hours, escalation routes and out-of-hours arrangements.

Illustrative worksheet entry: Shared business files — backup status: unknown; provider says it administers the file service, but the agreement does not identify backup coverage. Business owner: operations manager. Evidence: current service schedule. Next action: ask the provider to confirm included files, retention, restore testing and any separate charges in writing. This is an example, not a description of a Comm Centre service.

Scope map

Four questions that make a service boundary clear

  1. Scope Which sites, people, devices and services are included?
  2. Owner Who performs each task and who approves it?
  3. Evidence What reports or test results show what happened?
  4. Escalation Who responds, when, and through which channel?

The signed agreement and any written changes define the actual service.

Separate security duties from assumptions

“Managed” does not, by itself, say who detects a suspicious sign-in, investigates an alert or informs your business of an incident. Ask who performs each action, what is monitored, when alerts are reviewed and who makes business decisions. The joint advisory on managed providers and their customers recommends contracts clearly specify responsibilities and incident notification.

Ask your authorised administrator to keep a current list of provider access and review whether it is appropriate. Agree how access is granted and removed, and how provider activity can be reviewed. The Australian Cyber Security Centre’s guidance on engaging an MSP recommends limiting privileged access and setting clear security expectations.

Cloud services add another boundary: the cloud supplier, your IT provider and your business may each have a role. Check the ACSC’s small-business cloud responsibility guidance and the documentation for each service rather than assuming the cloud supplier handles every task.

Check backup and recovery separately

For each critical system, ask what is backed up, how often, how long copies are kept, where they are stored and how they are protected from alteration or deletion. Ask who receives and investigates failed-backup alerts. A successful backup report alone does not show that your business can restore what it needs.

Agree who can request a restore, who performs it and who checks that the restored data is usable. Ask for the date, scope and result of the latest relevant restore test, and when the next test is planned. Discuss how much data loss your business could tolerate and how quickly it needs the service back; any recovery targets should be written down and distinguished from guarantees. Restoration work, testing and extra storage may or may not be included.

Responsibility worksheet

Review the areas that often cross boundaries

  1. Accounts Ownership, access, recovery and joiners or leavers.
  2. Security Updates, monitoring and incident responsibilities.
  3. Recovery Backup scope, restore testing and business sign-off.
  4. Change & exit Projects, licences, records and handover.

Do not assume a provider or customer owns any task until it is confirmed in writing.

Understand response, resolution and escalation

A response may be an acknowledgement or an initial action, depending on the agreement. Resolution means the issue is fixed; an interim workaround or restoration of service may occur earlier. A response target is not a promise of a completed fix. Check how severity is assigned, what starts the clock, the applicable business hours and time zone, and what happens if a supplier is involved or a request arrives outside those hours.

Write down who to contact for an urgent outage, when to escalate and who in your business can approve decisions. If you suspect a cyber incident, stop making unapproved changes and contact your nominated incident lead and provider through a verified channel; use an alternative channel if your normal one may be compromised. Do not send passwords, recovery codes or unnecessary personal information in a request.

Clarify changes, costs and exit

Ask whether an office move, migration, new site, equipment installation or major account change is included support or a separately approved project. Request an itemised quote where needed, including applicable GST, travel, licences and out-of-hours work. Do not assume an estimate includes every supplier’s charges.

Before an agreement ends, identify who controls the domain, cloud accounts, licences, configurations, documentation and backups. Ask what can be transferred, what depends on supplier terms, what will be returned or deleted, and what handover assistance and charges apply. Agree a safe transition plan before changing administrator access; have authorised people verify access and recovery arrangements rather than exchanging credentials by ordinary email.

Turn gaps into agreed actions

Ask for a written response to each unknown and a recent, relevant piece of evidence, such as a service report, access review or restore-test result. Check what each report actually covers. Assign an owner and a review date to every gap, especially an unprotected critical system or an unclear incident contact. Escalate urgent gaps to your business decision-maker rather than treating this worksheet as proof of protection.

For help interpreting your arrangement, speak with your current provider or an independent adviser; seek legal advice if you need an interpretation of the contract. If your provider is Comm Centre, see the Comm Centre support page and confirm the appropriate contact route for your agreement.

Sources and further reading