What managed IT should include, and what it usually does not

Managed IT · Published

A plain list of what a managed IT arrangement should cover, the things that are often left out, and why we do not co-manage alongside another provider.

“Managed IT” is used to describe everything from an hourly break-fix arrangement with a monthly invoice to a fully outsourced technology function. Two providers can quote a similar figure for very different things. This article lists what a managed arrangement should include for a small organisation, what commonly sits outside it, and how to tell the difference before signing.

What should be included

A service desk with a real queue. Requests are logged, prioritised and tracked to resolution, and you can see them. If the arrangement runs on a mobile number and memory, it is not managed.

Monitoring and maintenance you do not have to ask for. Devices, servers and cloud services are watched for problems, updates are applied on a schedule that suits your operations, and the provider tells you what changed. The point of managed IT is that things are noticed before they become a support call.

Documentation that would survive the provider leaving. Network diagrams, device lists, account inventories, vendor contacts, licence records and the procedures for common tasks, kept current and owned by you. This is the item most often missing, and the one that hurts most when a relationship ends.

Security foundations, not just antivirus. Multi-factor authentication enforced, administrator accounts controlled, endpoint protection in place, and someone responsible for reviewing what those tools report. Security awareness training for staff belongs here too.

Backups that are tested, not just running. A backup job that reports success every night is not the same as a restore that works. A managed arrangement includes regular restore tests and a written recovery plan that says what comes back first.

Vendor liaison. When the internet provider, the practice management vendor and the printer supplier each say the problem is someone else’s, one party owns the coordination. That should be the managed provider.

Lifecycle planning. A list of what is ageing, what is out of support, and when it needs to be replaced, so hardware replacements are planned and budgeted for before they become urgent.

Regular reporting in plain language. What happened, what changed, what is coming next, and what decisions are needed from you. If the report is a page of ticket counts, it is not doing its job.

Onboarding and offboarding of staff. New starters are set up before day one, and departing staff have their access removed at the agreed departure time. Delays here can leave former staff with access they no longer need.

What is usually not included

None of these is unreasonable to exclude. The problem is discovering the exclusion when you need the service.

Projects. Migrations, office moves, server replacements and new systems are usually quoted separately. Check whether the arrangement includes any project hours, and whether planning and scoping are covered even when delivery is not.

Hardware and licences. The equipment and subscriptions themselves are almost always billed separately. Check whether the provider marks them up, and whether you own the licences.

After-hours and emergency response. Most arrangements cover business hours. If a practice runs on Saturdays or an incident at 9pm matters to you, the coverage hours need to say so.

Third-party application support. The provider will keep the workstation healthy, but the clinical or line-of-business application usually belongs to its vendor. A good provider coordinates with that vendor. Check whether that coordination is included or billed by the hour.

Strategy and budgeting. Advice on where technology should go over the next two or three years is often a separate advisory service. It is worth having. It is worth knowing whether you are paying for it.

Staff training beyond security awareness. Teaching people to use Teams or the new practice software well is rarely included.

Questions to ask before signing

  • What is the response target for something that stops a person working, and what is it for something that stops everyone?
  • Who owns the documentation, and can I have a copy today?
  • What happens to my data and accounts if we part ways?
  • Which of the items above are included, which are hourly, and which are not offered?
  • Who is responsible for testing backups, and when was the last test?

Why we do not co-manage with another provider

Telos Consulting takes on managed IT as the sole provider for an environment. We work alongside internal IT staff, and we coordinate with specialist vendors all the time, but we do not share ongoing responsibility for an environment with another managed provider.

The reason is accountability. Dividing responsibility between providers can create gaps in ownership, documentation and incident response. Taking responsibility for the environment gives us a clear view of how the systems fit together and gives you one provider to call.

We will happily review another provider’s proposal or plan, and if you decide to move, we coordinate the transition with the incumbent so that access, documentation and responsibility move across cleanly. How managed IT onboarding works describes that process.

Know what your managed IT covers. Telos Consulting builds the arrangement around your environment, with service desk support, maintenance, documentation, vendor liaison and planning. Security and backup services are scoped to your needs, with responsibilities and exclusions agreed before work begins. Start a conversation and we will walk through what your organisation needs and what the arrangement includes.