Business IT

What Should a Managed IT Provider Own

Learn what a managed IT provider should handle, how they should communicate and what a good technology plan looks like.

A managed IT provider should give your business a clear account of who owns support, management and IT planning. The monthly agreement needs to explain more than the products installed on computers. It should connect the work staff need to perform with the people responsible for keeping the supported setup usable.

For a business with 10 to 200 users, the practical question is whether the support plan fits the company. A law firm, medical practice and field-service business can have different apps, deadlines and physical needs. Use the questions below to review tasks before deciding whether a proposal offers the coverage you actually need.

Set the Supported Setup

Ask for a definition of supported users, locations, devices and apps. Include remote staff and staff who move between offices. Find whether the provider owns Microsoft 365 management, network equipment, security planning or only a subset of those tasks. A service title cannot answer those questions by itself.

Record which tasks fall outside the agreement and who handles them. An app company may control its own upgrades. A landlord may control the communications room. An internal staff member may still manage some systems or accounts. Those limits are normal, but they need a usable planning process. Your business should not have to rediscover the limit every time a problem affects more than one system.

Understand How Staff Request Help

A support process should tell staff where to report an issue and which details help assessment. The affected person, device, app and business impact give the team a better starting point than a message saying only that something is broken. Explain how urgent outages differ from routine requests and who can approve access or software changes.

Ask how the record follows a request through troubleshooting and vendor coordination. If a different technician continues the work, the staff member should not need to repeat everything already provided. Request the provider's actual coverage and escalation terms rather than assuming a testimonial sets a response target. Any published commitment needs to be reflected accurately in the agreement you approve.

Separate Daily Management from Project Work

An office move, major app transition or new location can involve carriers, cabling, procurement and staff updates. That work may require a separate project even when the same provider handles daily support. Ask how projects are found, scoped and approved. The proposed outcome should include dependencies and a way to confirm completion.

Do not judge a monthly fee only by whether it appears to include every possible change. An undefined promise can create disagreement about roles later. A clearer model identifies recurring tasks, explains project limits and records the approvals needed before work begins. Leadership then has a practical basis for comparing cost with tasks instead of comparing two service names that mean different things.

Ask Who Administers Access

New hires, departures and role changes should follow an agreed process. Find the person who approves permissions and the provider who implements them. Ask how admin access is recorded and how business roles of domains, Microsoft 365 and vendor services is preserved. Credentials should follow a secure process suitable to the setup.

If your company already has an internal IT staff member, define the split of tasks explicitly. A co-managed relationship needs agreed admin limits and escalation paths. It should also explain how both parties keep records current. Without that detail, adding another team can increase ambiguity even if both teams have capable technicians and good intentions.

Connect Security to Evidence

Ask which security tasks the provider owns and which are retained by your business or another specialist. Look for login security, device management, monitoring and an incident plan. A product list is useful context, but it is not evidence that a particular control is configured and operating correctly in your setup.

Request an explanation of how exceptions are handled and how leadership receives unresolved findings. A missing app owner or unsupported device should appear as an found issue, not disappear behind a general claim that security is covered. Evidence should describe the actual system and date reviewed. It should also distinguish IT setup from a policy commitment made by your company.

Review Recovery and Vendor Needed Steps

Discuss which data and business functions need recovery planning. Find backup admins, restoration procedures and the parties involved if an app is not working. Ask what has been tested and what remains assumed. The provider should be able to explain the difference between an inventory entry, a successful backup job and a checked restoration exercise.

Prepare a vendor record covering carriers, software companies and other IT dependencies. Include the contact, contract owner and supported system. If an outage crosses vendor limits, your agreement should explain who coordinates the conversation. This is particularly useful in leased offices or specialized setups where the IT team cannot directly control every part of the needed step chain.

Expect an IT Plan You Can Operate

A roadmap should connect proposed work to business priorities, support evidence and known constraints. Leadership needs to understand why a task matters, what it costs and who authorizes it. Separate urgent business gaps from improvements that can be scheduled. Avoid treating the ticket queue as the only source of future IT decisions.

Ask how the plan is reviewed as staff, locations and apps change. The answer should fit the scale of your company. A smaller business may need a concise set of tasks and upcoming decisions rather than a large reporting exercise. The test is whether the document helps an authorized person make the next decision with enough data and without relying on undocumented IT knowledge.

Compare What Each Proposal Covers

Create a comparison that lists supported users, remote coverage, physical work, admin roles, security tasks and project limits. Mark unknowns and request clarification before selecting a provider. Prices are easier to compare when each provider covers the same work. A lower fee with missing tasks may create more work for your staff or another vendor.

Read how DataSolved approaches managed IT. If you are changing providers, use the switching guide to review access, contract and handover dependencies. A 20-minute fit call can help you decide whether the proposed support fits your business before a deeper review.

Connect This Guidance to Your Business

See how these steps fit your business. Start with managed IT services and security tasks. Our guide for service firms covers access, staff tasks and client work.

Free Checklist for Business Owners

Free IT and Security Checklists

Practical guides you can use today, whether or not you ever work with us.