Small Business IT Documentation Checklist: 10 Records Every Company Should Maintain
Small-business IT documentation often receives attention only when an employee leaves, a system fails or a new provider takes over. By then, the organization may be searching for domain credentials, trying to identify an internet circuit, or discovering that nobody knows who owns an important cloud subscription.
Good documentation records what the business operates, who is responsible and how essential services are restored. It reduces dependence on one person or supplier.
This checklist focuses on concise, current records that an authorized person can use during operations, a provider transition or an outage.
1. Business technology ownership and emergency contacts
Start with names and responsibilities. Record the internal person who approves technology decisions, the primary IT contact and an alternate who can act when that person is unavailable.
Include current details for the managed service provider, internet provider, monitoring team, software vendors, cyber insurer or broker, legal adviser and incident specialists.
The Canadian Centre for Cyber Security recommends identifying responders, responsibilities and current contact information, with an accessible hard copy when normal systems are unavailable.
Review the contact list quarterly and after staffing or supplier changes.
2. Hardware, software and cloud-service inventory
Inventory business computers, servers, network equipment, mobile devices, critical appliances, applications and cloud services.
Each entry should identify:
- Device, application or service name
- Business purpose
- Location and assigned user or owner
- Manufacturer, model and serial number where relevant
- Operating system or software version
- Support or warranty status
- Administrator or responsible supplier
- Data the system stores or can access
- Business impact if the system becomes unavailable
The NIST Cybersecurity Framework 2.0 Small Business Quick-Start Guide recommends maintaining an inventory of the hardware, software, systems and services a business relies on. The Canadian Centre for Cyber Security likewise recommends maintaining an IT asset inventory and identifying the assets most critical to operations.
Flag unsupported equipment, inactive services, duplicate subscriptions and devices that no longer report to security or patch-management tools.
3. Domain, website and cloud-account ownership
Document the owner, billing contact and administrative access path for domains, DNS, hosting, Microsoft 365, accounting and other essential cloud services.
The business should control these accounts. A supplier can receive delegated access, but subscriptions should not exist only under a technician’s personal account.
For each service, record the official sign-in URL, tenant or account identifier, renewal date, billing owner, support method and approved administrators. Do not place passwords or recovery codes directly in the document. Store secrets in an approved password manager and document where the authorized record is held.
Confirm that recovery email addresses and phone numbers belong to the organization and remain monitored.
4. Administrative and emergency-access records
List the systems that have privileged or administrative roles, who is authorized to use them and how access is reviewed.
Include Microsoft 365 administrators, domain and hosting accounts, network devices, backup platforms, security tools, servers and major applications. Named administrative accounts should be used wherever possible so activity can be attributed to a person.
Document emergency or “break-glass” access separately. Record who can authorize its use, where the credentials are securely stored, what alerts should occur and how the account is tested. Multi-factor authentication and recovery methods should be reviewed after role changes and employee departures.
5. Network and connectivity diagram
A network diagram should show internet circuits, firewalls, switches, wireless networks, servers, cloud connections, remote access and links between sites.
Record internet-provider account numbers, circuit speeds, static IP information, support contacts and contract dates. Identify which firewall and switching ports serve critical systems, but keep sensitive configuration exports in an appropriately secured technical repository.
Give the diagram a revision date, owner and enough detail for an authorized technician to understand the environment.
6. Application, licence and vendor register
Maintain a register of business applications, licences and suppliers. Include Microsoft 365, accounting and payroll software, customer-management tools, industry applications, backup services, security licences, internet services and hardware support contracts.
For each item, record the business owner, technical contact, user count, renewal date, billing frequency, cancellation terms, support details and any important integration with another system.
This prevents surprise renewals and shows dependencies when a service outage affects other workflows, integrations or vendors.
7. Backup coverage and restore procedures
Document what is backed up, how often, where recovery copies are stored and who reviews failures. Cover servers, business files, Microsoft 365 data, application data and configuration information needed to rebuild critical services.
Record recovery priorities, expected recovery time, acceptable data loss and the date and result of the latest representative restore test.
The Canadian Centre for Cyber Security baseline controls recommend backing up essential information, restricting access and regularly verifying restoration. A successful job notification is not a demonstrated recovery.
Keep step-by-step restore runbooks for the systems that the business cannot operate without. Review them after platform or supplier changes.
8. Employee onboarding, role-change and offboarding procedures
Create repeatable checklists for starting, changing and ending access.
An onboarding record should cover the approved device, user account, Microsoft 365 licence, application access, security policies, multi-factor authentication, training and equipment acknowledgement.
When a person changes roles, review existing access before adding new permissions. For departures, document the timing and owner for disabling accounts, revoking sessions, recovering devices, transferring business data, changing shared access and notifying relevant suppliers.
These procedures help prevent dormant accounts and record what was completed and by whom.
9. Outage, incident and recovery runbooks
Write short runbooks for events the business is likely to face: an internet outage, Microsoft 365 disruption, lost device, suspicious email, compromised account, server failure or unavailable business application.
Each runbook should state:
- How the issue is reported
- Who has decision authority
- Immediate actions and actions to avoid
- Internal and external contacts
- Communication steps
- Recovery priorities
- Evidence or records to preserve
- Criteria for returning to normal operation
The Cyber Centre’s IT recovery planning guidance recommends identifying roles, prioritizing critical functions, defining recovery objectives and testing the plan.
10. Known risks, projects and review history
Maintain a simple register of unresolved risks and planned improvements. Examples include unsupported software, an aging firewall, incomplete multi-factor authentication, inconsistent backups or a critical application without a recovery plan.
Assign each item an owner, priority, target date and current status. Record accepted risks and the person who approved the decision.
Add a review history showing who checked each document, when and what changed. Update records when technical work is completed.
How to keep IT documentation secure and usable
Separate operational documents from passwords and recovery secrets. Use access-controlled storage for documents and an approved password manager for credentials. Keep an offline copy of essential emergency contacts and recovery instructions.
Choose one authoritative location; duplicates across email, personal folders and old shared drives quickly become unreliable.
Review asset, licence and access changes monthly; contacts, suppliers and recovery priorities quarterly; and the full record annually. Update it after major projects, departures and provider changes.
Build the essential record in 30 days
Start with the systems that would cause the greatest disruption if the usual administrator were unavailable.
In week one, confirm account ownership and emergency contacts. In week two, build the asset and cloud inventory. In week three, document backups, networks and critical applications. In week four, review access, test one recovery procedure and assign remaining gaps.
The result should help the business answer four questions quickly: What do we operate? Who owns it? Who can administer it? How do we keep working or recover when it fails?
SOS Computer Experts helps businesses create current IT inventories, secure account ownership, practical runbooks and a managed technology roadmap. Ongoing managed IT services are available only in North Vancouver, Vancouver, Burnaby, Coquitlam, Richmond, Surrey and Langley.
In Victoria, Calgary, Edmonton and Toronto, SOS provides only fixed-scope enterprise cybersecurity assessments and project-based enterprise security work—not managed IT, helpdesk, general cloud, networking or infrastructure services.
Request an IT documentation baseline
If your records are incomplete or depend on one person, SOS can review the environment, identify the most important documentation gaps and define the next practical steps.
Contact SOS Computer Experts to request a free 15-minute IT baseline for a business in the seven-city managed service area.
Request a Free 15-Minute IT Baseline
Identify missing ownership records, inventories, recovery procedures and access documentation before they become an operational problem.
