In most Australian businesses with 10–40 employees, there is one person who holds the entire back-office together. They know the login credentials for every system. They know which provider to call for which issue. They know the compliance deadlines, the payroll quirks, the bookkeeper’s preferences, and the IT company’s support process.
That person is usually the office manager. Sometimes it is the owner’s spouse. Occasionally it is a long-tenured administrator who has been with the business since the early days. Regardless of their title, they are the institutional memory of the back-office.
When they leave — and everyone leaves eventually — the business discovers how much operational knowledge was stored in a single person’s head.
I have seen this pattern repeatedly. The office manager gives four weeks’ notice. The owner realises, with increasing alarm over those four weeks, how much the office manager knows that nobody else does.
Where are the payroll system login credentials? The office manager knows. What is the process for onboarding a new employee? The office manager knows. When is the next BAS due, and what needs to happen before then? The office manager knows. Who is the contact at the IT company, and what is the support process? The office manager knows.
The handover is rushed and incomplete. The outgoing office manager writes as much down as they can, but institutional knowledge is not the kind of thing that transfers cleanly to a document in four weeks. It is accumulated experience, relationships, and pattern recognition that developed over years.
The replacement takes three to six months to reach the outgoing manager’s level of effectiveness. During those months, things fall through the cracks. A compliance deadline is missed because nobody knew it was coming. A supplier relationship deteriorates because the new person does not have the context the previous person had. An IT issue takes three times longer to resolve because the new person does not know the history.
Single points of failure in the back-office are not the result of poor management. They are the natural consequence of how small businesses grow.
In the early stages, the owner handles everything. As the business grows, they delegate to the most capable person available — usually the office manager. The delegation is organic, not structured. Tasks are handed off one by one, based on capacity and willingness, without documentation or formal process design.
Over time, the office manager accumulates an enormous body of knowledge about how the back-office works. This knowledge exists in their head, in their email history, in their personal notes, and in their relationships with providers. Very little of it exists in a form that anyone else can access.
This is not the office manager’s fault. They were never asked to document their processes. They were asked to do the work — and they did it well. The documentation gap is a structural issue, not a personal one.
The reflexive response to this problem is “we need to document our processes.” This is true but insufficient. Documentation helps. It does not solve the underlying structural problem, which is that too much operational capability is concentrated in a single person.
The more robust solution has three elements:
Documented processes that describe how each back-office function works, who is responsible, what systems are used, and what the escalation path is. Not 50-page SOPs — practical, one-page guides that enable someone else to pick up the work.
Shared system access so that login credentials, provider contacts, and operational information are stored in a system (a password manager, a shared drive, a knowledge base) rather than in someone’s head or personal email.
Distributed capability so that no single person is the only person who can perform any critical function. This might mean cross-training a second staff member, or it might mean engaging external providers whose service continues regardless of internal staffing changes.
The businesses most resilient to key-person risk are not the ones with the best documentation. They are the ones where the back-office architecture does not depend on any single individual — internal or external — for its continued operation.
If the question “what happens if our office manager quits tomorrow?” produces anxiety rather than a clear answer, the underlying structure needs attention. Not because your office manager is planning to leave — but because every business should be able to answer that question with confidence.