An IT Support Checklist Before You Hire a Provider

Before hiring an IT support provider, check whether they clearly define scope, response priorities, documentation ownership, Microsoft 365 administration, device support, security basics, backup monitoring, vendor coordination, project exclusions, and transition steps. A good provider should make responsibilities easier to understand before you sign, not after the first problem.

Start with the support scope

Ask what the provider supports on a normal monthly basis. This should include user help desk, computers, Microsoft 365, email, Teams, SharePoint, OneDrive, endpoint protection, network equipment, printers, backups, and common vendor coordination where relevant. If the provider says “everything,” ask for examples and exclusions.

Scope clarity matters because many disputes begin with different assumptions. The business thinks a task is included. The provider considers it a project. Neither side benefits from discovering that during an urgent issue.

Review response and escalation

Ask how requests are submitted, how priority is assigned, and who handles urgent issues. A company-wide outage, a compromised account concern, and a single-user request should not move through the same path. The provider should also explain when tickets escalate to senior staff or external vendors.

For a local business in Calgary, onsite expectations may matter. Confirm whether onsite visits are included, scheduled, limited, or billed separately. Remote support solves many issues, but some problems still need hands-on work.

Check ownership of access and documentation

The business should retain ownership of its Microsoft 365 tenant, domains, DNS, website hosting, backup systems, network equipment, and vendor accounts. The provider can administer those systems, but the company should not be locked out of its own environment.

Ask how documentation is maintained and what happens if the relationship ends. A professional answer should include a clean offboarding process, return of documentation, removal of provider access, and cooperation with the next support team.

Business scenario: comparing two proposals

A 19-user company receives two IT support proposals. One is cheaper and promises unlimited support, but excludes onsite work, backup remediation, Microsoft 365 cleanup, and network changes. The other costs more but includes quarterly reviews, backup monitoring, Microsoft 365 administration, device lifecycle tracking, and documented escalation.

The company chooses the second provider because the proposal matches its actual needs. The decision is not based on price alone. It is based on which provider accepts responsibility for the systems the business depends on.

Hiring checklist

• Ask what is included in monthly support and what becomes project work.
• Confirm response priorities for outages, security issues, key-user problems, and low-impact requests.
• Review Microsoft 365, device, network, backup, and cybersecurity responsibilities.
• Ask how documentation is created, updated, and returned if the relationship ends.
• Confirm who owns administrator accounts, domains, DNS, hosting, and vendor portals.
• Request examples of reports or review meetings the provider gives clients.
• Ask how the provider handles onboarding from a previous IT company.

Common hiring mistakes

One mistake is choosing the provider with the smoothest sales conversation but the least specific scope. Another is ignoring exclusions because the monthly price looks attractive. A third is failing to ask about offboarding. A provider that cannot explain how they would leave professionally may also be weak at documentation.

Do not treat certifications, tools, or vendor logos as a substitute for operational clarity. They may be useful signals, but they do not answer who will manage your backups, devices, access, and staff requests day to day.

Ask providers to walk through their first 30 days. The answer should include access validation, tool deployment, documentation review, backup confirmation, security baseline checks, and staff communication. If onboarding sounds vague, the relationship may start with avoidable confusion.

References and testimonials can be helpful, but they should not replace your own scope review. A provider that worked well for a very different company may not fit your business. Compare the provider against your systems, staff expectations, risk tolerance, and budget approval process. That is more useful than asking whether they are generally good at IT.

Ask about tool ownership too. Remote access agents, endpoint protection, backup software, and monitoring platforms may be licensed through the provider. That can be normal, but you should know what happens if you leave. The business should not lose visibility into core systems just because a contract ends.

Finally, compare the people process. Staff should know how to ask for help, managers should know how approvals work, and leadership should know how concerns are escalated. A capable technical provider can still frustrate a business if the service process is hard to use.

That clarity makes the final decision easier to defend internally.

Next step: run a proposal comparison

Create a comparison table with scope, response, access ownership, backups, security, Microsoft 365, onsite work, reporting, and exit terms. Gaps will appear quickly. OnlineV’s Managed IT Services gives a reference point for ongoing support. You can also review IT Consulting, Cybersecurity, and Managed IT insights.