Guide · When to automate a process
Hire another coordinator, or automate the work?
When the operations workload outgrows the team, the reflex is to hire. Sometimes that is right. Sometimes the work is carrying data that a system could carry, and the hire spends their week retyping. Three questions tell them apart.
This guide does not compare costs. Salaries, build costs and hours vary too much to do that honestly. It helps you decide which kind of work you have.
Sort the work before you decide.
Most operations roles mix four kinds of work. Place each task by how repeatable it is and how much judgment it needs.
Approving a drafted census, reviewing flagged exceptions.
Relationships, coordinating people, deciding what to change.
Moving data between systems, recurring reports, rule checks.
One-off requests and edge cases not worth building for.
Signs it is automation work
- The same steps every week
- Copying figures from one system into another
- Checking records against written rules
- Assembling the same report from the same sources
- It grows with every new location
Signs it needs a person
- Relationships with customers, families or partners
- A judgment call that changes each time
- Exceptions that need context to resolve
- Coordinating several people or teams
- Deciding what to improve next
Often the answer is both.
Automate the carrying, and keep people for the judgment. The role does not disappear; it moves from retyping to reviewing.
Retyped every center's attendance logs into the billing census, more than a day a week, then cleared the biller's flags.
Reviews a drafted census and a short list of flags. Approves every line. Corrections become rules.
Questions to answer first.
- How many hours a week does the work take?Measured over a real week, not estimated in a meeting.
- Will it grow with the next location?If it doubles, a hire buys time; a system changes the curve.
- Are the rules written down?If not, write them first. That alone often helps.
- Can the data be read from your systems?An API, a scheduled export, or a shared file.
- Who handles the exceptions?Automation still needs a named person for what it flags.
- What happens when that person is out?Documentation matters whichever way you go.
Mistakes on both sides.
- Hiring someone to retype. A new person doing the same copying adds capacity once; the next location brings the same work back.
- Automating judgment calls. Approvals, clinical, billing and coding decisions stay with people.
- Automating before the rules are written. The system copies whatever disagreement already exists.
- Guessing the hours. Measure a real week before comparing anything.
- Expecting a system to run itself. Someone owns it, reviews what it flags, and approves rule changes.
- Promising savings up front. Measure them after it is running.
Working out which tasks to automate, and in what order, is what an audit is for. The automation audit checklist · Operations audit and automation
What owners ask about hiring and automation.
Will automation replace our coordinator?
It replaces the carrying, not the judgment. At our flagship client the operations lead still approves every line; what changed is that the census arrives drafted, with a short list of flags, instead of being retyped.
When should we hire an operations manager?
When the work is coordination, judgment and improvement across people: running the team, handling exceptions that need context, and deciding what to change. Automation can make that role more effective; it does not make it unnecessary.
What business processes can be automated?
Work that repeats the same way and follows rules you can write down: moving data between systems, reconciling two records, assembling a recurring report, routing a request to the right person, and flagging what breaks a rule.
Why is there no cost comparison here?
Salaries, build costs and the hours involved vary too much by business and market to publish one honestly. Measure the hours the work takes today, then compare real quotes. Savings from automation are measured after it is running, not promised before.
Can we do both?
Often that is the answer: automate the repeated carrying, and hire or keep people for the judgment. The person who would have retyped data becomes the person who reviews what the system flags.
About to post a job for an operations coordinator?
Bring the job description to a free 20-minute call. We will tell you which parts look like automation work and which need a person.