See clearly
IT audit for SMEs: see clearly before you decide
An independent assessment, decisions with no blind spots
An information systems audit is an independent assessment of a company’s IT: governance, applications, infrastructure, security, data, providers, budget and continuity. It identifies risks, dependencies and priorities, then turns them into a realistic action plan. Lunova, a consulting firm based in Nyon, carries out these audits for SMEs in Western Switzerland without selling or installing the solutions it recommends.
Situations
When does an information systems audit become necessary?
An audit is rarely the starting need. It becomes necessary when a decision, a difficulty or a transformation requires understanding the information system beyond the visible issue. Several situations can lead to widening the analysis to the whole information system:
A specific problem that hides others. A recurring outage, persistent user dissatisfaction, an incident: looking for the cause, deeper questions about how the IS is organised come to light.
A difficulty that spills beyond its scope. A cybersecurity issue or a problematic application reveals weaknesses that reach well beyond that scope.
Preparing an IT master plan. Before setting a multi-year trajectory and priorities, you need an objective assessment, otherwise the trajectory rests on impressions.
Acquiring a company. Before a takeover, the audit identifies risks, dependencies, the real level of control over the IS and the investments to plan for.
Scope
What does an IS audit cover?
The scope adapts to the context, but the analysis grid stays the same. It covers organisation as much as technology, because a problem that shows up in IT does not necessarily have an IT cause.
IT governance and organisation
Who decides, who arbitrates, how IT is steered; roles, responsibilities, skills.
Business needs and applications
Does IT really meet operational needs; fit, obsolescence, redundancies, dependencies.
Infrastructure, cloud and security
Overall consistency, resilience, level of control, main risks.
Data
Where it is, who is responsible for it, whether it is protected and usable; the audit takes data protection and applicable requirements into account, in particular under the Swiss Federal Act on Data Protection (FADP), and refers to legal expertise when the subject warrants it.
Providers, contracts and budget
Responsibilities, dependencies, quality of supplier management, commitments, deadlines, and where the money really goes.
Projects, continuity and documentation
Priorities and delivery capacity, backup and recovery, critical people and systems, control over IS knowledge.
To examine
Common points of attention in SMEs
Every company’s situation is different. Some subjects nevertheless deserve careful examination in an audit:
- leadership does not always have a clear view of IT risks, dependencies and spending;
- responsibilities, decisions and supplier management sometimes rest on habit rather than on a shared framework;
- day-to-day operations may depend on a single provider, or on one person who alone holds a key skill;
- insufficient documentation and staff turnover gradually erode control over the system;
- a difficulty that shows up in IT regularly originates in the organisation, the processes or the quality of the data.
Example
Case study: regaining control of a growing SME’s IS
Context. An SME of about 35 users, expecting rapid growth over the following two years.
The situation. The company had lost control of its information system. Several providers were involved and tended to pass responsibility to one another. Users were dissatisfied and IT difficulties regularly affected the business.
The need. Restore a stable situation while preparing the company for growth.
Our engagement. An initial audit, then identifying and prioritising the issues, building the action plan, clarifying each partner’s roles and responsibilities, setting up indicators, leading the projects needed to bring the environment up to standard, and regular supplier follow-up.
The result. Stability restored, higher user satisfaction, clarified responsibilities, providers followed up regularly and better control of the information system.
This case makes an important point: the audit was only the beginning.
It was the sequence of diagnosis → action plan → governance → steering delivery that produced the result.
Method
How does a Lunova audit work?
While tailored to your issues, our audits follow a common six-phase methodology. It aims at two things: every significant finding rests on identified evidence and can be explained to leadership, and the rating is transparent and argued rather than asserted. Before the final deliverable, findings and recommendations are presented to you along the way and validated with you: nothing comes as a surprise at the final presentation.
1 · Scoping
We identify the stakeholders to involve (leadership, staff, providers, customers) and set up with you the steering committee that will follow progress and decide when needed. The kick-off meeting closes this step: everyone leaves with the objectives, their role and the schedule.
2 · Fact-finding
We meet leadership, the IT team, business units and the providers concerned, to capture each one’s issues. Minutes follow every interview and confirm nothing was left out. Available documents and factual evidence complement these discussions.
3 · Analysis
A first assessment is presented to the steering committee to validate the focus areas before any recommendation: it is the audit’s first deliverable. The analysis then follows the same logic for each domain (observation, risk, business impact, recommendation), looking for the real cause rather than the symptom.
4 · Rating and prioritisation
Risks are assessed by likelihood and business impact; maturity is scored from 0 to 5 per area, with the current level and the target. This rating is a reasoned expert judgement, not a certification.
5 · Action plan
Recommendations become a trajectory over 0-3, 3-6, 6-12 and 12-24 month horizons where the context allows, taking into account criticality, dependencies, prerequisites, resources, costs and your capacity to absorb change. Guiding principle: secure before expanding.
6 · Presentation to leadership
Presentation to leadership: strengths, risks, maturity, findings and impacts, prioritised recommendations, action plan and follow-up. It always starts with what works: an audit that leaves the impression that everything must be redone triggers no decision.
Deliverables
What do you receive at the end?
The audit produces usable documents, not a statement of intent. At the end of the engagement, leadership has:
- a diagnostic report setting out findings by domain, each with its business impact;
- a risk map, rated by likelihood and impact;
- a maturity assessment by area, with the current level and the target;
- a prioritised action plan by time horizon;
- an oral presentation to leadership and the follow-up arrangements.
These documents belong to the company, which then uses them to decide on investments, scope projects and manage its providers.
Positioning
Why bring in an outside view?
Your IT provider knows its scope and the technologies it runs. That is legitimate, and it is also its limit: it sees the system from its own position. Lunova looks at the situation from the position of the company and its leadership, including the governance and management of that provider.
Lunova is neither an integrator nor a reseller of solutions. Our role is that of a conductor: analysing, advising, selecting, challenging, coordinating, arbitrating with you and following delivery, without taking the place of the specialists who do the work. We know technologies and partners that we know work, and we propose them when they meet the need; the criterion remains your need, never a resale.
Depending on what the audit reveals, the next step takes different forms: interim IT management when the company finds itself without an IT manager, client-side advisory to formalise a need and choose a solution, or leadership of a project that needs to get back on track.
Before you decide
Frequently asked questions about IT audits
How much does an IT audit cost for an SME?
The budget depends on the size of the company, the scope chosen and the depth of analysis expected. An audit focused on a specific issue does not cost the same as a full assessment preparing an IT master plan. A first conversation helps understand the situation and define the right scope before pricing the engagement.
How long does an audit take?
From about three days for a focused audit to several weeks for a full scope. The duration depends on the size of the company, the number of stakeholders and providers to meet, the complexity of the system and the level of existing documentation.
How can we tell whether the problem really comes from our provider?
This situation arises in particular when several providers are involved and pass responsibility to one another. The audit clarifies who does what, what is contractually owed, what belongs to the internal organisation and what is genuinely the provider’s.
Our IT partner already knows our system. What does an external audit add?
Detailed internal knowledge and an independent view do not produce the same result. The point is not to document more, but to identify risks, dependencies and priorities with enough distance, and to make them something leadership can decide on.
Should we change the tool or review the processes first?
With ERP in particular, changing a tool without addressing the processes and data quality risks reproducing the problem in a new environment. The audit determines whether the difficulty really comes from the tool, the processes, the data or a combination, so that the decision rests on facts rather than impressions.
What happens after the audit?
You have a prioritised action plan that you are free to implement with whoever you choose. When clients wish, we continue by steering that plan: clarifying responsibilities, setting up indicators and following up providers.