Before You Hire a Second Admin: Audit What Your Office Manager's Week Is Actually Made Of

The role gets hired for one thing and grows into another. Someone is brought in to run the office. Then accounts payable lands on them. Then debtor chasing. Then payroll. Then the month-end reconciliation, because nobody else knows where the receipts live. Nobody decides this. It accumulates one handover at a time, and each handover is individually reasonable. The pattern shows up constantly in small business forums. One owner described it plainly on r/smallbusiness: "Our office manager handles most of it but between processing invoices, coding everything in QuickBooks, reconciling the bank account, running payroll every two weeks, reviewing expense reports, following up on late payments, and prepping for tax filings, she's basically spending her entire week on financial admin." Read that list again. Seven named tasks, and every one of them is recurring, rules-based and calendar-driven. None of them is the job the person was hired to do. This is a recurring complaint in owner-operator communities rather than a measured statistic, and it is not specific to Australia. But the shape of it is consistent enough to plan around: the office manager role silently converts into an unstaffed finance function.

The failure is not dramatic. It is a slow widening of the gap between done and done on time. Another post on r/smallbusiness put the consequence in concrete terms: "She’s great but she’s one person doing a three-person job, and things are slipping: missed prior auths that delay procedures, phone calls going to voicemail, patients waiting 15 minutes just to check in." Notice which things slip. Not the payroll. Payroll has a hard deadline and legal consequences, so it always gets done. What slips is everything with a soft deadline: the callback, the follow-up, the client who needed an answer today. That is the real cost. The rules-based work crowds out the relationship work, because the rules-based work shouts louder. You lose revenue and goodwill in the quiet places, and it never appears on a report. There is a second cost, which is retention. Good admin people leave non-billable roles because those roles get no development budget and no visible progression. A post on r/auscorp captured the culture that produces this: "I was disheartened to hear the HR manager speaking badly another admin staff member who asked to go to an event because it’s a lot of money and she’s only admin so she won’t get the opportunities the professional staff members do." If your best admin person is doing a three-person job and being told their development is not worth funding, you will lose them. Then you are hiring two people, not one, and one of them has to relearn everything.

Do not survey the feeling. Log the week. Ask your office manager to keep a simple tally for five working days. Every discrete task gets a line, with four columns. Task: the specific thing, such as code supplier invoices in Xero, not accounts. Minutes: rough is fine, round to 5. Trigger: what caused it, a date, an email arriving, or a person asking. Decision: does this need a judgement call, or does it follow a rule? That last column is the whole exercise. If the task follows a rule that could be written down and handed to a new starter, it is rules-based. If it requires reading a situation, weighing an exception, or maintaining a relationship, it is judgement work. Two honest cautions. A week is a small sample, so run it in a normal week, not month-end, and note anything monthly that did not appear. And people under-report interruptions, so add a fifth column for interrupted by if the tally looks suspiciously tidy. At the end of the week you will have a list, not a feeling. Total the minutes in each category. That total is your actual hiring case.

The split is not about difficulty. Some rules-based work is technically demanding. It is about whether the decision changes. Rules-based and recurring work includes coding supplier invoices to the right account, sending the same three debtor reminder emails, reconciling matched bank transactions, building the same weekly job report, chasing timesheets before payroll, filing and renaming documents, and copying data between two systems. The judgement and relationship equivalents are deciding whether to hold a supplier payment, ringing the client who is genuinely in trouble, investigating the transaction that does not match, reading the report and flagging what looks wrong, handling the timesheet dispute, onboarding a new client properly, and deciding the process should change. The second list is why you hired a capable person. The first list is why they are drowning. The angle most owners miss: the second hire usually gets scoped entirely from the first list, because that is where the visible backlog is. So you hire someone to do repetitive work, permanently, at ongoing cost, and the judgement work is still unstaffed.

Be specific, because vague answers here produce disappointing projects. Software handles well: moving data between systems that both have an API, applying a rule that is written down, sending a scheduled reminder, flagging an exception for a human, generating a recurring report, and collecting information through a form instead of an email thread. In Australian service firms, that usually means Xero or MYOB talking to a job management system such as simPRO, ServiceM8 or Tradify, plus rostering in Deputy. Software handles badly: anything where the rule has never been written down, anything where the exception rate is high, and anything where the relationship is the point. Approving a payment when cashflow is tight is a judgement call. Do not automate it. The counter-argument is real. Automation projects fail often, and the usual cause is not the tooling. It is that the person who built it left, or the process changed and nobody updated the flow, so it quietly produced wrong output for two months. If you buy automations from an agency and nobody in your business understands them, you have swapped a workload problem for a dependency problem. That is the case for capability transfer instead of a retainer. If your office manager can map their own process and build the flow that removes the rules-based half of it, they own it, they can fix it when the process changes, and they can spot when it is wrong. That is also, not coincidentally, the development opportunity that keeps them.

Sometimes yes. The audit tells you which. If most of the week is genuine judgement work, client contact, exception handling and coordination, then you have a volume problem and you should hire. If most of the week is data entry, chasing and reconciliation, hiring a second person makes two people do the repetitive work instead of one. There is also a third answer that the r/smallbusiness threads keep pointing at: sometimes the gap is skill, not hours. A general office manager doing statutory finance work is a risk regardless of how many hours they have. In that case the answer is a bookkeeper or an external accountant for the technical work, not another generalist. The sequence that works: audit the week, remove the rules-based half, give the judgement half back to the person you already have, then hire against whatever is still overflowing after ninety days. You will hire a smaller, better-defined role, and you will have kept the person who knows how everything works.

How long should the audit run for? Five working days in a normal week, not month-end. Add a separate list of monthly and quarterly tasks that did not appear in the sample, with an estimate of hours for each. That combination gives you a realistic annual picture without asking anyone to time-track for a month. What if my office manager resists being time-tracked? Frame it as evidence for their case, not surveillance, because that is what it is. The tally is what justifies either a hire or removing work from their plate. Let them keep the log themselves and see the totals first. If they distrust the exercise, the results will be useless anyway. Should we just outsource bookkeeping instead? Outsourcing suits technical compliance work such as BAS preparation, statutory reporting and payroll processing. It does not remove the internal coordination around it: chasing receipts, approving invoices and answering supplier queries. Audit first, then decide which half goes external and which half gets automated internally. Is it cheaper to automate than to hire? Not always, and beware anyone who promises it is. Automation has real build and maintenance cost. The honest comparison is a one-off build plus ongoing ownership against a recurring salary that grows every year. Run the audit and compare against your own numbers, not a generic claim. Who in a small business should build the automations? The person who already knows the process, usually the office manager. They know the exceptions and the reasons behind each step. The transferable skill is diagnosis and process-mapping, not dragging nodes around a canvas. Tooling is the easy part and changes anyway. What happens if the person who built the automation leaves? This is the main failure mode, so plan for it. Train two or three people, not one. Document each flow in plain language: what it triggers on, what it changes, and how to turn it off. If only one person understands it, it will break silently after they go.

Quotes are reproduced verbatim and attributed to the subreddit only, never to an individual. r/smallbusiness: https://www.reddit.com/r/smallbusiness/comments/1qzi3vc/business_owners_doing_3m_how_are_you_handling_ap/ . r/smallbusiness: https://www.reddit.com/r/smallbusiness/comments/1r1nfib/my_dermatology_practice_is_growing_but_i_cant/ . r/auscorp: https://www.reddit.com/r/auscorp/comments/1qtkwoj/should_i_bring_unhappiness_up_in_midyear_review/ . These are qualitative observations from public discussion, not survey data. The pattern is recurring in owner-operator communities but has not been confirmed as specific to Australia.