ARGE ICT · Published November 11, 2026 · Updated November 15, 2026
As long as the infrastructure appears to be running, most companies have no written record of whether backups can be restored, which devices are out of warranty, or who has access to which system. That information is usually looked up only during an outage, an audit request, or an investment decision.
When an assessment is needed
An infrastructure assessment usually comes up in these situations:
- The person responsible for IT or the outside support firm changes.
- Before a relocation, a merger, or a new ERP project
- Before a budget is presented to management
- After an outage or a security incident
- Ahead of a customer or auditor request
- When the infrastructure documents are out of date
What these situations share is a decision or a change that requires the current state of the infrastructure to be known in writing. Before a new ERP project, for example, an assessment shows in writing whether the existing servers, network, and backups will be enough for the project.
Areas reviewed
We review the ten areas in scope:
- Servers and virtualization
- Backup and disaster recovery
- Network and wireless network
- Firewall and endpoint security
- Identity and access
- Email and Microsoft 365
- Cloud use and cost
- License and warranty status
- Technical measures under KVKK, Türkiye's Personal Data Protection Law (Law No. 6698)
- IT processes and documentation
Some of these areas concern the infrastructure itself, meaning servers, the network, and backups. The others cover how the infrastructure is managed, meaning processes, licenses, and documentation. Each area in scope is reviewed separately and assessed in its own line of the report. We decide with you which systems are reviewed before the work starts.
Steps in the process
The work runs in four steps:
- Discovery call: in a one-hour call, we learn about your business, your team, the problems you face, and your budget priorities.
- Non-disclosure agreement (NDA) and scope: once the agreement is signed, we define with you the systems to be reviewed and the access we will be given to them.
- Review: we review the systems through read-only, authorized, time-limited access, and on site as well when necessary.
- Report and roadmap: we collect the findings in a scored, prioritized report, read it with you, and build a roadmap ordered by your budget.
The review and report usually take one to two weeks; the time depends on the size of your infrastructure. No changes are made to systems during the review. Access to your systems starts only after the agreement is signed and the access permissions are defined.
The service comes in two forms: a preliminary assessment of an infrastructure or security project you are planning, or a stand-alone, independent consulting service. The details of the steps and the two forms are on the IT Health Check page.
Reading the report
The report shows a score and a green, yellow, or red status for each area in scope. The findings are listed in order of priority, and the roadmap is arranged to fit your budget. We prepare the report in language that non-technical managers can read as well.
The scores make it possible to compare the areas with one another; when the same assessment is repeated later, progress is tracked with those scores.
Read the red areas and their business impact first, and then the owner and schedule of each item on the roadmap. For the presentation to management, the questions in IT risk and investment decisions for CEOs can be used.
The report is yours; you can carry out the recommendations with your own team or with another firm. We state the fee and terms in our proposal.
Carrying out the recommendations is outside the scope of the IT Health Check; the work ends with the report and the roadmap.
Preparing for the review
Before the work starts, these items can be prepared:
- An inventory and a network diagram, if you have them
- A list of license, warranty, and maintenance contracts
- An authorized person to answer questions on behalf of the company
- Read-only access accounts
- A joint decision on which systems will be accessed
Missing documents do not prevent the work; a gap in the documents is itself a finding. Access accounts are created as read-only, and access ends when the review is finished.
How it differs from a security assessment and a penetration test
An IT Health Check reviews the infrastructure as a whole through read-only access and delivers a scored report. A security assessment, in contrast, looks only at security and includes active testing.
In a penetration test, a specialist tests, within the agreed scope, whether vulnerabilities can be exploited. An IT Health Check is neither a penetration test nor a certification audit, and it does not issue a compliance certificate.
Which work is needed depends on the question. An IT Health Check answers questions about the overall state of the infrastructure; a penetration test answers how well a system resists attack.
Frequently asked questions
How often should an IT Health Check be repeated? There is no fixed interval. The assessment is repeated after major changes such as a relocation, a merger, a new ERP, or a change of the person responsible for IT, and when the work on the roadmap has been completed. The scores in the first report are used to compare progress in the next assessment.
Do we need an outside assessment if we have an IT team? It is not required. An outside assessment provides the time the team cannot set aside within its daily workload, and the view of someone who did not build the infrastructure. The team can use the findings in the report as independent support for the budget case it presents to management.
Does an IT Health Check cause downtime? No. The review is carried out through read-only access, and no changes are made to systems during the review. Any problems found are listed in the report; remediation is planned after the report, by your decision.