Server, device and service inventory
See which systems are in use, where they are located and who is responsible for them.
IT documentation
IT documentation and infrastructure map
We inventory your IT infrastructure, document critical systems, map risks and deliver a clear report that shows what exists, what is risky and what should be fixed first.
Problem
Without documentation, every incident starts by searching for basic answers.
The goal is an operational view of the system that decision makers and responsible people can use when action is required.
The company does not know who has admin access.
Domains, DNS, hosting and email are undocumented.
Backups exist, but restore has not been verified.
Former employees may still have access.
There is no network map.
Everything depends on one person.
There is no procedure for outages.
Risks are not ranked by business impact.
Deliverables
You receive a system map, risk register and order of priorities.
The scope follows the real infrastructure: users, locations, servers, cloud services and critical applications.
Infrastructure map
Connect locations, networks, servers, cloud services and critical dependencies.
Domains, DNS, hosting and email review
Identify ownership and the points where one mistake could interrupt communication.
Google Workspace / Microsoft 365 review
Review account organization, administrative access and baseline security settings.
Backup and restore review
Check what is copied, where it is stored and whether a realistic recovery plan exists.
Baseline security review
Map MFA, access, firewall, devices and obvious sources of unnecessary risk.
Risk register
Separate risks by likelihood, business impact and remediation priority.
PDF report
Deliver an overview that can support decisions, planning and internal records.
Recommendations and priorities
Define the order of work: urgent, important and planned, without random spending.
Operational handover
IT infrastructure documentation your next administrator can use.
We agree which systems to review and who will confirm the information. Unknown details remain explicitly marked as unverified.
Inventory and responsibilities
For the agreed devices and services, we record purpose, location, ownership, dependencies and the source of each finding. Verified observations are distinguished from information supplied by your team.
Network map
We map the agreed sites, internet connections, network segments, VPN links, servers and cloud services. Critical connections and dependencies are identified for troubleshooting.
Access and ownership
We document who controls domains, DNS, email and administrator accounts, where access is securely managed and how it can be recovered. Passwords and keys are excluded from the report.
Backup and recovery procedure
We record backup coverage, copy locations, ownership and the agreed recovery sequence. A successful backup job is distinguished from evidence of an actual restore test.
Risk register and next steps
Findings include business impact, priority and a proposed action. Owners and deadlines are agreed with your team; recommendations are not presented as completed fixes.
Review and document maintenance
We deliver the PDF and review open questions with your team. The review date and document owner are recorded; ongoing updates and editable formats are agreed separately.
Illustrative example
What might a documentation entry contain?
This fictional example illustrates the structure. It contains no real client information and does not represent a completed assessment.
- System: a business application on a virtual server.
- Dependencies: internet access, DNS, the virtualization host and storage.
- Ownership: the application and backup owners designated by the company.
- Recovery evidence: not supplied; restore remains unverified.
- Next action: agree an isolated restore test and record the outcome.
Scope and security
Review first, then agreed implementation.
The assessment uses supplied information and authorized access. Permanent administrator access is not a prerequisite; we agree how to review each system. Configuration changes, migrations and practical restore testing require a separate scope and approval.
Backup and disaster recovery · Managed IT support · Discuss your documentation scope
Process
The review is structured. The output is useful to both technical teams and management.
We introduce visibility first. Only then do we propose interventions, migrations or a maintenance model.
Initial call
Information gathering
Technical review
Infrastructure map
Risk register
PDF report
Maintenance proposal
Not included
The assessment is clearly separated from ongoing support and larger interventions.
- Support during agreed business hours is not included in this service.
- 24/7 availability is provided only through a separate SLA agreement.
- Urgent interventions and work outside business hours are agreed separately.
- Migrations are not included.
- Deep penetration testing is not included.
- Ongoing maintenance is agreed separately.
Important
The report does not become shelfware.
Recommendations are separated into urgent, important and planned actions, so the next investment starts with actual risk.
Starting price
The final offer depends on scope, but the starting point should be clear.
We confirm the scope after a short discussion about users, locations, servers and critical services.
IT documentation and infrastructure map
from €250 one-timeStarting scope for the infrastructure, access, backup and business service review.
Complex infrastructure
custom offerMultiple locations, servers, network segments or critical applications require a precisely defined scope.
Documentation + maintenance
custom offerConnect the documentation with a realistic monthly maintenance and responsibility plan.
EUR pricing for international inquiries. For Serbian resident companies, invoicing and payment are performed in RSD in accordance with the issued offer and invoice.
FAQ
Common questions before the review starts.
Do you store our passwords?
We document where access is managed, who is responsible and how access can be recovered. Passwords are not placed in the PDF report. If centralized storage is needed, we recommend a suitable password manager and access policy.
Do you fix issues during the documentation process?
Small corrections can be identified and handled by agreement. Larger interventions, migrations and urgent work are scoped separately so the assessment and the implementation remain clear.
How long does the documentation take?
For a small company, typically a few business days after the required information is collected. For multiple locations, servers or more complex services, we confirm the timeline after the initial call.
Can this be the start of monthly maintenance?
Yes. Documentation is a good starting point because it defines what exists, what is risky and which maintenance level makes sense for the company.
Do we receive a PDF report?
Yes. You receive a clear PDF report with an infrastructure overview, risk register, priorities and recommended next steps.
Does the documentation prove that backups can be restored?
Documentation alone does not prove recovery. We record available evidence and mark untested restores explicitly. Practical recovery testing is scoped separately, with authorization and a record of the results.
Who updates the documentation after handover?
We identify the document owner and review date at handover. Ongoing updates are not automatically included; they can be part of a separately agreed maintenance arrangement.
First step
Send the basic information about the company and the systems you use.
We reply with a realistic review scope, delivery model and next step.