IT INFRASTRUCTURE
Small business IT maintenance: assets, access and continuity
Organise computers, networks, accounts, servers and cloud services so support and recovery do not depend on one person’s memory.
Inventory equipment and services
Infrastructure includes workstations, network devices, business accounts, storage, applications and cloud services. Record ownership, purpose and responsibility. Document dependencies so an internet outage is not misdiagnosed as separate failures in every application.
Make configuration and access information available to authorised staff without keeping passwords in an open spreadsheet. Track licences, suppliers and renewal dates. A useful inventory supports maintenance, replacement planning and appropriate support for critical systems.
Manage the account lifecycle
Provide access according to role rather than administrator rights for every task. Review permissions when people change roles and remove unnecessary access when they leave. Shared accounts can obscure who changed a record or configuration.
Plan multifactor authentication and account recovery where supported. Decide who manages recovery information and verifies reset requests. External collaborators should receive only the access and duration they need. Security should fit a workable process rather than invite workarounds.
Control network and device changes
Reliable networks depend on suitable equipment, configuration and capacity. Document routers, access points and important connections. Consider separating guest connectivity from business resources where appropriate. Plan changes with a recovery route if connectivity is lost.
Track workstation updates, storage and conditions affecting work. Replacement should follow user needs as well as age. Use approved remote-access methods rather than exposing administrator services directly to the internet for convenience.
Connect backups, monitoring and recovery
Identify the data to protect and systems to recover first. Acceptable data loss and acceptable downtime are different decisions. Test backups against those needs, including cloud data that may otherwise be assumed safe from every kind of mistake.
Monitoring needs an accountable response. Choose meaningful indicators and avoid alert volume that causes everything to be ignored. Document incident actions, supplier contacts and escalation. Change history helps identify whether a failure follows a recent configuration change.
Define the support scope
Support may cover computers, networks, servers and accounts without including every possible project. Specify users, locations, working hours and critical services. Agree remote assistance, on-site work and out-of-hours availability separately.
Distinguish preventative maintenance, incidents and projects such as migrations. Request documentation the company can retain and clear reports. The aim is an understandable environment with known responsibilities and a tested recovery process rather than a universal package.
Example: a departing employee retains access
Leaving should trigger an agreed process beyond collecting a laptop. Review accounts, shared folders, external applications and devices. The business decides what information needs transfer; authorised technical staff implement the access changes.
Onboarding likewise needs equipment, applications and role-based permissions. Checklists reduce improvisation and excessive privileges. Record completion and the person who approved it.
Assess before promising ongoing support
Missing documentation, unclear account ownership or untested backups may require an initial assessment. Provide prioritised findings rather than promise an instant fix. Some changes need planned downtime or supplier coordination.
Resolve core dependencies and access before adding monitoring tools. More tools do not automatically mean more reliability. Support scope should follow the actual business risk and environment.