Beyond Break-Fix: The Managed IT Baseline Every Client Deserves
May 15th, 2027
Many businesses pay for "managed IT" and receive a help desk with a monthly invoice. Someone answers when something breaks, fixes the immediate problem, and leaves. The arrangement feels familiar because it is the same relationship the company had with its break-fix provider, just with a recurring fee.
Managed IT means something more specific. It means a set of services that run continuously, whether or not a ticket exists. The provider takes responsibility for the health of the environment, not just for closing tickets. That responsibility shows up in a baseline of work every client should receive.
If you are evaluating a provider or wondering what your current one should be doing, use this list as a starting point.
The Technical Baseline
Patch Management
Operating systems, applications, and firmware should be patched on a defined schedule. Critical security updates should be deployed quickly, with a process for testing and rollback when a patch causes problems.
The provider should report patch compliance by device and follow up on machines that fail or go offline. Patching is not a one-time project. It is a monthly routine with visible results.
Verified Backups
Backups should cover the data and systems the business needs to operate, follow a schedule that meets the recovery point objective, and be stored in a way that survives ransomware. Most importantly, they should be tested.
Ask for the last restore test, what was restored, and how long it took. A backup that has never been restored is an assumption, not a recovery plan.
Endpoint Protection
Every endpoint should have managed endpoint protection that is installed, updating, and reporting to a central console. Alerts should be reviewed, not just collected.
The provider should have a response procedure for malware detections, including isolation, investigation, and cleanup. A detection without a response is only a notification.
Monitoring and Alerting
Servers, network equipment, and critical applications should be monitored for availability, capacity, and security events. Alerts should route to someone who can act, with clear escalation paths.
Monitoring should include the things that fail quietly: disk health, backup jobs, certificate expiration, and account lockouts. The goal is to find problems before users do.
Identity and Access Management
Accounts should be created and removed through a documented process. MFA should be enforced for email, remote access, and administrative accounts. Privileged access should be limited and reviewed.
Joiner, mover, and leaver processes are part of the baseline. An account that remains active after an employee leaves is a security gap, no matter how good the rest of the program is.
Asset Inventory and Documentation
The provider should maintain an inventory of hardware, software, licenses, and network configuration. Documentation should cover how key systems are configured, who has access, and how to recover them.
Good documentation reduces downtime and makes the business less dependent on any one person. It also makes onboarding a new provider possible without starting from scratch.
The Service Baseline
Response and Resolution Targets
Every ticket should have a priority and a response target. The provider should measure performance against those targets and share the results.
Response time is not the same as resolution time. A provider that acknowledges every ticket in five minutes but takes days to fix recurring issues is not delivering managed service.
Onboarding and Standards
A new client should go through a structured onboarding: discovery, documentation, security review, and remediation of the most serious gaps. The provider should not simply inherit the previous provider's setup without checking it.
Standards matter. A consistent set of tools, configurations, and security settings across clients makes support faster and reduces the chance of a missed control.
Reporting
Monthly reporting should show what was done, what was found, and what needs attention. Look for ticket trends, patch compliance, backup results, security events, and upcoming renewals.
The report should be written for a business owner, not an engineer. If it cannot be understood without a translator, it is not doing its job.
Quarterly Business Reviews
A quarterly review connects IT work to business goals. The provider should bring a roadmap, discuss budget and risk, and ask what the business is planning for the next six to twelve months.
This is where lifecycle replacements, security improvements, and new initiatives get planned before they become emergencies.
What "Managed" Should Not Mean
Managed IT should not mean unlimited tickets for anything that breaks, with no responsibility for prevention. It should not mean a portal where the client submits requests and waits. It should not mean a provider that only appears when something is on fire.
It also should not mean hiding problems. A provider that reports only good news is not giving the client the information needed to make decisions. Honest reporting, including open risks, is part of the service.
Questions to Ask
- What is included in the monthly fee, and what is billed separately?
- How do you measure patch compliance, and can I see last month's report?
- When was our last restore test, and what was the result?
- Who reviews security alerts, and what is the escalation path?
- How do you handle onboarding and offboarding?
- What does the quarterly business review cover?
- What would you fix first if you took over today?
The last question is revealing. A provider with a real baseline can answer it specifically. A break-fix provider will talk about the last ticket.
Build the Relationship Around Prevention
The best managed IT relationship feels calm because the work is happening before problems reach users. That calm is the product. It comes from routines, documentation, reporting, and planning, not from heroic responses to avoidable failures.
ATS delivers managed IT services built around that baseline, with clear reporting and planning. If you are not sure what your current provider does between tickets, contact our team for an assessment.
Posted in: IT Support
