Six to twelve months into a managed IT arrangement, the important question is no longer whether your provider can fix a problem.
It is whether the arrangement is improving the business.
A good provider should now understand your operating model, your priorities, your risk profile and the cost of keeping technology reliable. They should be able to explain what has improved, what remains exposed and what needs to happen next.
If the relationship has become a ticket desk that waits for something to break, it is time for a mid-term IT health check.
This is not an exercise in replacing technology for the sake of it. It is a structured review of whether your IT strategy, services and supplier accountability are still aligned with the business.
Start with the strategy, not the ticket count
The first test is simple: can your provider explain your technology priorities in business language?
They should understand:
- Which systems are critical to revenue and customer service
- Where downtime creates the greatest financial or operational risk
- Which processes are inefficient or overly manual
- What your next twelve to twenty-four months may involve
- Where technology costs are rising without a clear return
- Which risks need investment before they become incidents
This is the role of the Fractal IT Director: providing a strategic view that connects board-level objectives with the infrastructure, services and specialist execution required to deliver them.
Traditional Managed IT Services remain important, but they should support this strategic framework. Helpdesk Support, device management, patching, network monitoring, hardware and software licences are execution services. They are not a substitute for leadership.
A useful health check should therefore produce more than a service report. It should create a prioritised roadmap with owners, timescales, estimated costs and expected business outcomes.
1. Cloud Solutions: controlled, secure and financially understood
Many SMEs move quickly into cloud platforms, but do not always review how those platforms are being managed once implementation is complete.
Your review should establish whether your provider maintains a current inventory of cloud services, administrators, users, integrations and data owners. It should also confirm that leavers are removed promptly, privileged access is limited and multi-factor authentication is applied consistently.
Ask for evidence covering:
- Microsoft 365 and other cloud tenant security settings
- User onboarding and offboarding
- External sharing and guest access
- Backup arrangements for critical cloud data
- Recovery testing and documented restoration times
- Cloud usage, licence allocation and unused subscriptions
- Dependencies between cloud platforms and line-of-business applications
Cloud Solutions should make the business more resilient and flexible. They should not create an invisible collection of subscriptions that nobody fully owns.
This is also where Technology Expense Management becomes commercially useful. A strategic review should identify duplicated licences, dormant accounts, poorly sized services and contracts that no longer match your requirements. Saving money is not the same as reducing capability; it is about paying deliberately for the capability you actually need.
For businesses considering process improvement or a new operational platform, a structured Dynamics 365 Jump Start can also be useful. The key is to begin with process, data and commercial objectives rather than starting with a software demonstration.
2. Disaster Recovery: confidence must be tested
A backup dashboard showing green ticks is not a Disaster Recovery plan.
Your provider should be able to explain:
- What is backed up
- How frequently backups run
- Where copies are stored
- Who can access them
- How long data can be retained
- How quickly critical systems can be restored
- When the last successful restore test took place
The health check should distinguish between recovery point objectives and recovery time objectives. In plain English: how much data could you afford to lose, and how long could the business operate without a particular system?
These answers will differ between a practice management system, a file server, email, telephony and a non-critical workstation. A single generic backup policy is rarely enough.
Your provider should also explain what happens if it is affected by an incident. The National Cyber Security Centre recommends that SMEs clarify MSP responsibilities, access controls, incident reporting, backup arrangements and contract obligations. Its guidance on choosing a managed service provider is a useful independent reference.
3. Network Solutions: measure the experience, not just the equipment
A network can look healthy on paper while users experience slow applications, unreliable Wi-Fi and intermittent connections.
A mid-term review should cover your core Network Solutions, including:
- Firewalls and security configurations
- Switching and wireless infrastructure
- Internet capacity and resilience
- Site-to-site connections and remote access
- Guest, staff and device network segmentation
- Firmware and patching status
- Monitoring, alerting and performance trends
- Physical cabling and equipment age
Ask your provider to show trends rather than isolated snapshots. Has latency increased? Are wireless complaints concentrated in particular areas? Are cloud applications consuming more bandwidth? Are recurring faults being permanently resolved or repeatedly closed?
Good network management is preventative. It identifies capacity and resilience issues before they interrupt trading.
A provider should also be clear about what it manages directly and what sits with a connectivity supplier, landlord, cabling contractor or another third party. Ambiguous responsibility is a frequent cause of slow incident resolution.
4. Voice and Connectivity: does communication support the operation?
Voice and Connectivity are often treated as a commodity until call quality deteriorates or the primary internet circuit fails.
Your review should examine:
- Internet uptime and actual incident history
- Call quality, dropped calls and one-way audio
- Hosted telephony availability
- Mobile and remote-working arrangements
- Call routing during an outage
- Failover connections and diversion procedures
- Integration with collaboration tools and customer systems
- Contract renewal dates and excess capacity
The right question is not simply, “Are the phones working?”
It is, “Can customers, suppliers and staff communicate effectively when normal conditions change?”
A business continuity plan might include a secondary circuit, mobile failover, cloud-based call routing or documented diversion procedures. Whatever the design, it should be tested. A recovery plan that exists only in a supplier’s proposal document is not a recovery plan. It is optimistic stationery.
5. Helpdesk Support: responsiveness is only the starting point
Helpdesk Support is the most visible part of the relationship, but ticket volume alone tells you very little.
Review:
- First response times by priority
- Resolution times and ageing tickets
- Reopened tickets
- Repeat incidents
- First-contact resolution
- User satisfaction
- Escalation routes
- Communication during major incidents
- Requests that should have become improvement projects
A large ticket count may indicate strong engagement, poor systems or simply an easy route for users to report every minor issue. The valuable question is what the data reveals.
If the same printer, application, user group or network segment generates tickets every month, the provider should recommend a permanent fix. If they only close each ticket individually, the business is paying for the same problem repeatedly.
You should also know who is accountable for your service. A named technical or strategic contact should be able to discuss trends, risks and priorities without sending every question back to the queue.
6. Managed IT Services: is the provider proactive?
The clearest warning sign is that your provider only contacts you when:
- A contract is due for renewal
- A major incident has already happened
- A project needs approval
- A new product is being promoted
- An invoice requires clarification
A strategic Managed IT Services relationship should include scheduled reviews, infrastructure health reporting and forward planning.
At minimum, request a report covering:
- Device and server health
- Patch compliance
- Backup success and restore testing
- Security alerts
- Warranty and end-of-life dates
- Open risks
- Licence and subscription usage
- Recurring support trends
- Recommended actions and priorities
The provider should be willing to explain what is included, what is a bolt-on and what requires a specialist channel partner. There is nothing wrong with using a trusted network of technical partners. In fact, it can provide valuable scale and specialist capability. The issue is whether your provider remains accountable for the outcome.
That accountability matters particularly where you have specialist or legacy systems. If IBM i, Power Systems or AS/400 platforms are part of your estate, IBM i Management should be treated as a high-value technical consultancy discipline, not squeezed into a generic support queue.
The five warning signs of a reactive ticket desk
Six to twelve months in, reconsider the arrangement if:
-
There is no current technology roadmap.
Nobody can explain what should happen next or why. -
Reports describe activity but not risk.
You receive ticket totals and uptime figures, but no business interpretation. -
Recurring incidents are treated as normal.
The same faults return without a root-cause investigation. -
Costs are reviewed only at renewal.
Unused licences, duplicate services and ageing contracts are left untouched. -
Nobody challenges your assumptions.
A strategic partner should occasionally say that a proposed purchase, migration or upgrade is not the best route.
What good looks like after the health check
A useful mid-term review should leave you with a clear, practical picture:
- Your most important systems and risks are documented
- Cloud Solutions are secure, owned and commercially understood
- Disaster Recovery has been tested against realistic scenarios
- Network Solutions are monitored for performance and capacity
- Voice and Connectivity support continuity and flexible working
- Helpdesk Support data is being used to prevent repeat issues
- Managed IT Services are linked to a strategic roadmap
- Technology Expense Management opportunities are visible
- Specialist requirements have clear ownership
- Priorities are sequenced around business value rather than supplier convenience
The outcome should not be a thick report that disappears into a board pack. It should be a short list of decisions, supported by evidence.
For organisations reviewing technology alongside wider operational or property requirements, the Evestaff group gateway provides a discreet route to explore the broader services available across the group.
Your IT provider does not need to be the largest supplier in the market. It does need to understand the business, take responsibility and make the technology easier to govern.
At the mid-term point, that is the real health check: not whether the tickets are being closed, but whether the business is becoming more resilient, more efficient and better prepared for what comes next.
Join The Discussion