Contact Info
Unit 9, 17 Power Ave
Alexandria, NSW 2015
info@hexflow.com.au
+61 (2) 8529 4085
Follow Us
Practice administrator working alongside an automated workflow at a desk

Admin Jobs and Automation: What Actually Changes Hands

Automation does not usually take a job. It takes the parts of a job that can be written down, and leaves the person holding everything that cannot — which is a different job, and often a harder one.

Questions about automation admin jobs arrive in two shapes: will the role still exist, and what will the person in it actually do all day. The honest answer to the first is that some roles genuinely shrink. The honest answer to the second is that the work left over is supervision, exceptions and relationships, and most practices do not train anybody for that.

The Work That Disappears First

The tasks that go first are the ones where the input, the rule and the output are all written down. Re-typing a form into a practice management system. Building a letter from a precedent. Moving a list from one system to another. Chasing a document that is overdue by comparing two dates. Reconciling a timesheet against a roster.

None of it needs judgement. All of it needs attention, which is why it eats the day and why the saving is real when it goes.

The Work That Gets Bigger, and Nobody Budgets For It

Something has to check the output, decide what happens when the rule does not fit, and explain to a client why the system said what it said. In most practices, the person who did the data entry ends up doing the exception handling — more skilled work than the job it replaced.

That is a promotion in disguise, and a training problem. Automate without rewriting the role description and you get a confused employee and a queue nobody owns.

What Moves to the Agent, What Stays With a Person

Can sit with the agent

  • Data entry between two systems, and the reconciliation that follows
  • Document assembly from an approved template
  • Overdue-item chasing, at a fixed cadence, with a polite escalation
  • Standard status updates to clients, where the status is a fact already recorded
  • Booking, rescheduling and confirmation, within written rules
  • Preparing a first draft of anything with a precedent

Stays with a person

  • Any conversation where the client is upset, worried or asking why
  • Deciding whether a situation is an exception worth escalating
  • Negotiating fees, deadlines or scope
  • Handling a complaint, and the record of how it was handled
  • Judgement on a person’s circumstances — health, capacity, hardship
  • Anything that requires an apology
  • Deciding what to automate next, and what to leave alone

The right-hand column is shorter and that is exactly why the role changes rather than disappears. It is also why the left-hand column is where the cost saving sits: it is bulky, repetitive and easy to measure.

The Grey Zone Nobody Writes a Rule For

Genuinely arguable — decide it in writing, per practice

  • Coordination. An agent can propose a roster. Whether it should be allowed to confirm a shift change is a management decision, and it depends on how much authority you want to delegate at 6am.
  • Triage of inbound enquiries. Sorting new-mail into “new matter”, “existing client” and “not for us” is mechanical until the one that is misclassified was a distressed caller.
  • Debt chasing. Reminders are procedural; the fourth one is a relationship decision and should never be automatic.
  • Client updates on progress. Fine when the update states facts already recorded. Not fine when it sets an expectation about timing.
  • Summarising a call. Useful, and dangerous if the summary is treated as the record instead of the transcript.

What Happens to the Person in the Role

Three outcomes. The role absorbs the oversight and becomes system supervision — the good outcome, and it needs a new job description and a pay conversation. The role shrinks and the person leaves — real, and pretending otherwise insults the person doing the job. Or the role stays as it was and the agent is bolted on beside it, which is the worst of the three: you pay for both and the work is done twice.

If you cannot say which one is happening in your practice, it is the third.

Where This Analysis Is Wrong

If the volume is low, the agent costs more than the admin hours it saves. At two or three documents a day, the integration and the oversight outweigh the typing, and the honest recommendation is to leave it alone.

If the work is highly variable, the agent handles the standard case and creates exceptions faster than a person would, leaving a queue of edge cases and less time to deal with them.

And if the admin person is the one clients ask for by name, automating their tasks removes the reason they were valuable while leaving them in the room. That is a resourcing decision, not a technology one, and it belongs to you.

What we build

We automate the left-hand column, refuse the restricted items in the right-hand one, and write down the grey zone as a rule your team can actually apply. We also write the exception queue into the design, so the person supervising the system has somewhere to work.

If you want to see what the role looks like afterwards, we will map one week of the current job first.

Easir Maruf works at Hex Flow in Alexandria, Sydney, building and supporting AI agents and workflow automation for accounting, legal, medical and NDIS practices.

Post a Comment