What Should a Managed IT Services Agreement Include?

A managed IT agreement should make one thing easier before service ever starts: knowing who owns what.

The monthly price matters, but a clear agreement is more valuable than a cheap one if it prevents surprise charges, support gaps, and arguments about whether a problem is “included.”

1. Support coverage and service hours

The agreement should define when employees can request support, how critical incidents are handled, and whether after-hours or 24/7 response is included for specific severity levels.

2. What the helpdesk owns

Look for clarity around login issues, email, applications, devices, connectivity, printers, permissions, onboarding, offboarding, and vendor escalation. A helpdesk should not simply forward every issue somewhere else.

3. Cloud administration

If your business depends on Microsoft 365 or Google Workspace, the agreement should explain who manages users, identity, licensing, email, permissions, sharing, onboarding, offboarding, and security configuration.

4. Device management and maintenance

Define who handles monitoring, patching, endpoint security, encryption, remote support tools, inventory, configuration, and lifecycle planning for company devices.

5. Cybersecurity responsibilities

Security scope may include endpoint protection, identity and MFA controls, security awareness training, vulnerability or configuration reviews, email security, backup oversight, and incident readiness. The agreement should also be clear about what is not included, such as legal advice, forensic services, or guaranteed compliance outcomes.

6. Projects versus routine support

This is one of the most important distinctions. The agreement should explain which work is included in the monthly service and which work becomes a separately scoped project—such as migrations, office moves, major deployments, integrations, or infrastructure redesign.

7. Vendor management

If an internet provider, phone vendor, line-of-business application, copier company, hardware manufacturer, or cloud provider is involved, define whether the MSP coordinates escalation on your behalf.

8. Onboarding and documentation

A strong onboarding process should document users, devices, cloud systems, vendors, security tools, licensing, administrative access, known issues, and support procedures. You should understand whether onboarding has a separate fee and what deliverables it includes.

9. Response expectations and escalation

Service levels should distinguish critical incidents from normal support requests. Ask how severity is determined, what the response target means, and what happens when an issue needs escalation.

10. Pricing, exclusions, and termination

Make sure the agreement explains the pricing basis, included tools or licenses, excluded expenses, project rates, hardware or software pass-through costs, term length, renewal rules, and termination process.

Compare ownership, not just price

Two proposals can have similar monthly prices and very different responsibilities. The most useful comparison is a responsibility map: support, cloud, devices, security, vendors, projects, backups, onboarding, documentation, and planning.

For a broader view of the model, see our Managed IT Services overview or review managed IT pricing. If you want us to scope your environment, you can also request a managed IT quote.