Insights
An SME IT assessment: scope, findings and deliverables
An IT assessment looks at the actual state of your devices, accounts, backups and security, then hands you prioritised findings, the related risks and an action plan. Its scope and duration depend on what you ask it to examine.
Published on By Smart ITReading 7 minutes
Organisational byline. Prepared with AI tools; every cited fact is automatically checked against its source.

An IT assessment — often called an IT audit — answers a specific question: what state is your IT in, what risks does that create for the business, and where should you start. It is neither an equipment list nor a sales proposal. A serious assessment is built on evidence — readings, configurations, documents — and keeps that evidence clearly apart from the recommendations drawn from it.
The word covers very different things. This is not a financial audit, a certification or a penetration test (a controlled attack designed to test your defences). An SME IT assessment looks at how IT is organised and run day to day. Before it starts, the scope should be written down: sites, users, tools and areas included, and anything explicitly left out.
The areas reviewed
Most assessments cover the same broad areas, with a depth suited to the size of the business. For each one, the point is not only what is in place, but what proves it.
| Area | What is checked | Evidence requested |
|---|---|---|
| Inventory | Computers, servers, network equipment, phones, installed software and online services in use | Up-to-date list showing the user, age and support status of each device |
| Accounts and access | Active accounts, accounts of former staff, admin rights, multi-factor authentication | Export of accounts and roles, list of administrators, multi-factor authentication status per account |
| Backups | Data covered, frequency, location and protection of copies, restore tests | Recent backup reports, record of the latest restore test |
| Device security | Updates, malware protection, disk encryption, local admin rights | Update and protection status read from the devices or the management console |
| Filtering, forwarding rules, shared mailboxes, sending domain configuration | Email service settings, list of rules and delegations | |
| Network | Firewall, guest and internal Wi-Fi, remote access, equipment past end of support | Network diagram, firewall configuration, list of open remote access points |
| Licences and contracts | Licences assigned and in use, renewal dates, maintenance and provider contracts | Invoices or vendor portals, current contracts with their end dates |
| Documentation | Whether procedures and admin information exist, are current and can be found | The documents themselves, with their last revision date and location |
| Business continuity | Ability to resume work after a failure, theft or attack | Recovery plan or, failing that, written answers on priorities and acceptable downtime |
These areas line up with public frameworks. The CIS Controls, for instance, start with inventory: actively managing all enterprise assets. They also have a control for account management, administrator accounts included, and one for restoring systems to a pre-incident state. Their first level, IG1, is a set of 56 basic safeguards described as essential cyber hygiene. The NIST CSF 2.0 is organised around six functions: Govern, Identify, Protect, Detect, Respond and Recover. An assessment need not follow either framework line by line, but it helps to know which one it relies on.
For more on two of these areas, see how to check that your backups can actually be restored and security priorities for a small business.
The method: interviews, readings, analysis
1.Scoping
The goal, scope, contacts, access required and report format are agreed in writing before work starts.
2.Interviews
Management, the office or finance manager, a few users and, where relevant, the current provider each describe what they do, what gets in the way and what they believe is in place.
3.Readings
Admin consoles, configurations, backup reports and documents are reviewed. This is where statements are checked against facts.
4.Analysis
Each gap is rated: possible impact on the business, likelihood, urgency.
5.Debrief
The report is presented, priorities and open questions are discussed, and the final version is then delivered.
Keeping findings and recommendations apart
A finding describes what was observed, with its source; a recommendation says what should be done. Illustrative example: the finding "three former employees' accounts are still active, reading of 12 March" leads to the recommendation "disable these accounts and formalise the leaver procedure". A report that blends the two makes the reasoning impossible to check, and makes it hard to challenge a recommendation without disputing the finding.
What you should receive
The deliverable is what remains once the assessor has left. Before commissioning an assessment, check that it will include at least:
- A management summary, readable without technical knowledge, stating where the main risks lie.
- The findings, grouped by area and priority, each linked to its evidence.
- The related risks, expressed as business consequences: downtime, data loss, information leak, non-compliance.
- An ordered action plan: what comes first, who does it, and an estimate of the effort.
- The limits of the assessment: what was not examined, for lack of access or because it was out of scope.
- As appendices, the inventory and readings, reusable by an in-house team or a provider.
Duration and effort vary widely with the number of users, sites and tools, and with the depth expected. A quote that specifies neither the scope nor the content of the deliverable gives you nothing to compare offers on.
Preparing for the assessment
An assessment moves faster, with fewer back-and-forths, when documents are gathered in advance. What is missing is information too: a missing document is often the first finding.
- The list of current users and recent leavers.
- The hardware inventory, even partial, and recent purchase invoices.
- Admin access to the main services: email, storage, firewall, backup.
- Current contracts, licences and subscriptions (IT provider, maintenance, telecoms, software), with their renewal dates.
- The latest backup reports and, if there is one, the record of the last restore test.
- Any existing documentation: network diagram, procedures, passwords kept in a password manager.
- A list of notable incidents in recent months and pain points raised by staff.
Warning signs
- A "free" audit whose report boils down to a sales proposal: that is a sales meeting, not an assessment.
- A generic report that could apply to any business and cites no dated observation.
- Recommendations that all point to the assessor's own products or services, with no alternative.
- No prioritisation: forty points of equal weight do not help anyone decide.
- No stated limits: an assessment that excluded nothing has probably checked nothing in depth.
- Findings with no evidence, which neither your team nor a third party can verify.
A first conversation is not a full assessment
Before commissioning an assessment, many businesses mainly need to know whether one is needed and what it should cover. That is the purpose of Smart IT's free audit: a 45-minute remote conversation, with no commitment, about your organisation, your tools and your main difficulties. It identifies three priorities and ends with a written summary of the priorities and proposed next steps.
This first conversation relies on the information you choose to share. It involves no work on your systems, no penetration test and no exhaustive technical diagnosis, so it produces neither readings nor evidenced findings in the sense described above. An in-depth technical review can be the subject of a separate proposal.
There is also a public scheme focused on cybersecurity. Luxinnovation's Fit 4 Cybersecurity programme lets a company carry out a comprehensive audit of its exposure to cyber-attacks. Its diagnostic can combine several targeted audits, including physical security of the premises, architecture, backup efficiency, configuration and penetration testing, and leads to a roadmap with a costed action plan. The company selects a registered expert, and the subsidy rate depends on its size; current conditions are on the programme page.
After the assessment
The action plan usually turns into projects: replacing computers, reviewing access, moving backups, migrating email. Each needs scoping, a schedule and checks, which is what IT consulting and project management covers. The assessment is also a solid basis for choosing an IT provider against established needs, or for switching IT provider knowing exactly what has to be handed over.
Frequently asked questions
As a rule, yes. They often hold the access and documentation, and their answers are part of what is reviewed. The assessment is about the state of your IT, not about blaming anyone.
To produce evidenced findings, yes: read-only access to admin consoles and reports. Which access is granted, for how long, and how it is removed at the end should be settled at the scoping stage.
Not necessarily. A penetration test is a separate service, with its own framework and authorisations. If you want one, it must be written into the scope explicitly.
There is no universal frequency. A new assessment is useful after a significant change: an office move, team growth, a change of provider, an incident. Between assessments, following up the action plan matters more than the original report.
A good assessment shows three things: a written scope, findings tied to evidence and a prioritised action plan. If you are not yet sure which one to commission, a first conversation can help you decide.
Find out whether you need a full assessment
A 45-minute remote conversation, with no commitment, to identify three priorities. You receive a written summary.
