Practical planning guide · Published 12 November 2026 · Automated Australia
Look for a task your team repeats in roughly the same way: recording an enquiry, preparing an internal summary, moving approved information between systems, or reminding someone that a task needs attention. Write down the steps before deciding whether it needs AI. A simple rule or form may solve the problem more reliably.
Describe six things
- Trigger: what starts the work, and how do you identify a repeated event?
- Inputs: what information is needed, where does it come from and who may access it?
- Rules: which decisions can be written down, and which need judgement?
- Output: what should be created or changed, and how will you confirm it happened?
- Owner: who approves the work or handles an exception?
- Fallback: how does the team continue if an integration is unavailable?
If these answers are unclear, map the workflow with the people doing the job before commissioning software. Automating an unclear handover can make the same confusion happen faster.
Rules, AI, or a person?
A rule is a good fit for a predictable condition such as routing a selected service to a team. AI may help interpret varied language or prepare a summary, but it can be wrong. Keep approval with a person when the result commits the business to a price, makes a sensitive decision or changes something that is difficult to undo.
For an enquiry workflow, a useful first version can extract the requested service, suggest a category and prepare a reply. The team checks the draft before it is sent. That tests whether the assistance is useful without pretending that an automatic reply is always appropriate.