A practical business systems health check

Review one working day

Follow an ordinary job from first enquiry to completion. Note every system, spreadsheet, inbox and message thread involved. Ask the people doing the work where they wait, retype information or chase an answer. This is an operational checklist, not a security certification, financial assessment or substitute for specialist advice.

Check who controls the essentials

List your domain, email, website, phone provider, job system, CRM and accounting software. Record the business owner, administrator, renewal date and recovery method for each. Check that former staff or suppliers do not hold the only access. Do not make risky account changes without confirming how the service depends on that access.

• Does the business control the domain and recovery email?
• Can a nominated person recover each critical account?
• Are administrators using suitable multifactor authentication?
• Can access be removed when a staff member leaves?

Trace every new enquiry

Pick examples from phone, website, email and social messages. Check whether each has an owner, a response and a next action. Pay attention to after-hours enquiries and missed calls. A notification is not the same as someone taking responsibility. Agree where the team looks for unassigned or overdue requests.

Find double entry and unclear records

Look for contact details copied between tools, job photos sent to personal phones and quote status tracked in several places. Choose a source of truth before connecting systems. For each potential automation, write down the trigger, required information, approval, failure alert and responsible person. Automating an unclear process can simply move the confusion faster.

Check recovery, not just backup labels

Ask what would happen if a device failed, a file was deleted or an important provider became unavailable. Identify what is backed up, how long versions are retained and who can restore them. Arrange a safe restore test with the responsible provider where appropriate. Do not assume cloud synchronisation preserves everything you need.

• Which data is business-critical and where is it stored?
• When was an appropriate restore last tested?
• Who is contacted for a phone, email or job-system outage?
• What manual process keeps essential work moving?

Check the people and the numbers

Ask staff which tool they avoid and why. It may be a permissions issue, unnecessary fields or a workflow that does not work on a phone. Then check one management figure, such as quote acceptance: define the date range and denominator, trace a few records and note missing information. A polished dashboard is only useful if the team trusts what it measures.

Choose the next manageable improvement

Group findings by urgency, business impact and dependencies. A lost administrator login, an unowned enquiry queue and an inconsistent template do not need the same response. Choose one improvement with an owner, a clear finish condition and a review date. Take active security incidents to your established incident contacts rather than waiting for a routine website enquiry.

Keep exploring

Use these guides to prepare a practical conversation about your business systems. They provide general technology information, not regulated professional advice.