Practical guide · Better IT by Care Computers

What should an IT health check cover?

A good IT health check should give a business a clear, proportionate view of its current technology and responsibilities. It should not be a sales pitch for a predetermined replacement project. The scope should reflect the organisation, its important services and the questions it needs answered.

Read this guide

Practical guide

Agree the scope and useful outcome

Before an assessment begins, define what is in scope, which locations and services are included, who will provide access and what the organisation wants to learn. A clear scope helps avoid both an unhelpfully narrow checklist and an open-ended investigation.

The outcome should describe the current state, important dependencies, known limitations, areas that need verification and practical recommendations. Findings should distinguish urgent issues from longer-term improvements and explain their business relevance.

User accounts and devices

Review how staff and suppliers access business services, how accounts are created and removed, and who holds administrative privileges. Check authentication controls, account recovery methods and whether access is appropriate to current roles.

Build a view of business computers, mobile devices and other endpoints. Understand ownership, operating system support, security configuration, update status, endpoint protection and how devices are managed when staff work remotely or equipment is replaced.

Users and identities

Current user and administrator accounts, sign-in protection, role changes, leavers and supplier access.

Endpoints

Device inventory, ownership, lifecycle, supported operating systems, update and protection status.

Applications

Important business software, dependencies, support status, integrations and known workarounds.

Infrastructure, networking and cloud services

For servers and infrastructure, record purpose, location, dependencies, support status, resilience and planned lifecycle. For networking, review connectivity, firewalls, switches, wireless, remote access and any configurations that are important to business services.

For cloud services, identify tenants, subscriptions, owners, administrators, connected applications, sharing settings and support responsibilities. The provider and customer have different duties, so document which party configures and monitors each relevant area.

Include internet circuits, voice services, DNS, domains and any third-party platforms that affect access or business operations. Confirm account ownership, supplier contacts, contract terms and renewal dates.

Cyber security, backup and recovery

Assess security controls in context: identity and access, device protection, updates, email and web protections, supplier connections, monitoring, incident reporting and decision-making. Record what is enabled, who manages it, how exceptions are handled and which evidence supports the assessment.

Review backup coverage, retention, access, monitoring and restore testing. Identify what the organisation expects to recover, how quickly it needs those services and who can authorise recovery. Connect technical recovery to business continuity, communications and practical workarounds.

  • What information and services are backed up, and what is excluded?
  • When was a restore tested and what did the test demonstrate?
  • Who reviews security alerts and coordinates a response?
  • Where are incident contacts, recovery decisions and continuity steps documented?

See the cyber security questions to review alongside the separate backup and restore considerations.

Documentation, licensing and suppliers

Check whether key information is current and accessible to authorised people: asset records, diagrams, support procedures, configuration notes, contracts, warranties and recovery information. Identify knowledge that sits with one person or supplier and could make support difficult if they were unavailable.

Review licences, quantities, ownership, renewal dates and dependencies. The aim is to understand whether the current arrangements match actual use and business requirements, not to remove licences without checking the impact.

List critical suppliers, service owners, contract and renewal dates, escalation routes and any dependencies between providers. Make clear who can approve account, DNS, access or service changes.

Support processes and technology planning

Understand how users request help, how requests are prioritised, what support hours apply and how recurring issues are reviewed. Assess whether responsibilities between internal staff, an external provider and specialist suppliers are clear.

Finally, connect the technical findings to plans for the business. Consider lifecycle changes, growth, locations, ways of working, compliance needs and projects already under discussion. Recommendations should have owners, order, dependencies and a reasoned priority.

What to expect from the output

A practical report or review meeting should explain scope and limitations, summarise the current environment, identify areas that could not be verified and list actions in a proportionate order. Ask for plain-language explanations and a chance to correct factual errors.

For help thinking about how an assessment could fit your organisation, see the Care Computers IT health check overview. If the review identifies a provider relationship question, changing IT provider can be considered separately; a health check does not require you to make that decision.

Whenever you’re ready

A useful assessment leaves you with clearer priorities.

If you want help understanding your current environment, start with the areas that matter most to your organisation and agree what a useful assessment should deliver.