In this guide 6 sections
Your office has outgrown informal IT support when faults wait for one busy person, nobody can list who holds which password, and no backup has ever been restored. Former staff with live accounts is another sign. These are gaps in process rather than skill. A named support contact and a routine schedule close most of them.
Faults wait for one person
In many small offices, IT is handled by the owner’s relative or the most technical colleague. They do it alongside a job of their own. When a machine fails at month end, they may be busy, travelling or on leave.
Watch how requests arrive. If faults are mentioned in passing or dropped into a chat group, some are forgotten. A fault that keeps returning gets fixed from scratch each time, because nobody kept a record.
This is the first sign. The work depends on availability, not on a route.
Nobody can say what the business owns
An administrator password often lives on paper, in a chat and in the memory of former staff. It is rarely changed, because nobody knows everything it opens. Subscriptions are bought by departments, some on personal cards, some for people who have left.
Try answering a few plain questions without looking anything up. If the answers take a day of searching, the inventory is missing.
- Who holds the main administrator password today?
- In whose name is the domain registered?
- Which subscriptions renew in the next three months?
- Which laptop is with which employee, and how old is it?
Backups that have never been restored
Backup software reports that a job ran. It does not tell you whether a file can be recovered. A disk change or a moved folder can break the job quietly.
Run a simple test this week. Pick a file changed last month and restore it to a different location. Open it and check the contents.
If nobody knows how to do that, the backup is an assumption. A pen drive that someone remembers to plug in counts as one too.
Former staff still have access
Handover at exit often covers the client list and little else. The mailbox stays active, the laptop goes home, and customer files sit in a personal drive. A VPN login may still work months later.
Take the list of people who left in the past year. Check each one against mail, shared drives, accounting software and any remote access. Every live account found is a sign that leavers are handled by memory.
- Mailbox still receiving or sending mail
- Shared drive folders still shared with a personal address
- Company laptop never returned or never wiped
- Remote access or VPN login still active
Small faults nobody reports any more
A laptop needs two restarts every morning. Updates have been deferred for weeks and the disk is nearly full. Staff stop mentioning it because the machine still works.
The riskier version arrives by mail. A message styled as an instruction from the owner asks the accounts desk to pay a new account. Without two-step login and mail filtering, the only control is the caution of whoever reads it.
Start with an inventory of devices, accounts and licences. Then turn on two-step login for mail and administrator accounts and test one restore.
- Deferred updates on several machines
- No two-step login on mail accounts
- Payment change requests accepted by email alone
Office IT health check
A short list of yes or no questions on passwords, backups, leavers, licences, updates and two-step login. Answer each one with the person who handles IT today. Every “no” or “not sure” becomes a line on the list of things to fix first.
Open a blank worksheet to printQuestions owners ask
Do these signs mean we need a monthly support contract?
Not always. A small team on laptops with no server may need only a one-off setup and written notes. A monthly arrangement suits offices where routine work and requests keep arriving.
Can the colleague who helps today keep doing it?
Yes, if their role is written down. A co-managed setup lets them keep daily faults while an outside team takes backups, security baselines and leave cover. GullySystem works this way alongside internal staff.
Is a messy starting point a problem?
No. Shared passwords, untested backups and live accounts for former staff are the usual starting point. The first weeks go into an inventory and a stabilising pass, with a written list of priorities.