Choose a contained automation recipe with a clear boundary, human checkpoint and recovery route.
Pick work that is repetitive and rule-led
Mapping detail
Good candidates have a recognisable trigger, consistent inputs and an ordinary next action. Saving an email attachment to the correct job folder may qualify; deciding whether a complex complaint is justified does not. Observe the task several times before automating it. Note variations, exceptions and the consequences of a wrong action. A small saving repeated daily is often safer and more valuable than a grand flow touching every department.
Put approval before commitments
Mapping detail
Drafting and preparation are easier to automate safely than irreversible actions. A flow can assemble a quotation draft from approved rates, but a person should check scope and send it. It can prepare an invoice from a completed-job record, but should stop when required purchase-order details are missing. Place human approval before spending money, changing customer commitments, publishing content, deleting records or sending sensitive information.
Keep each recipe inside a stated boundary
Mapping detail
Specify what the recipe does and deliberately does not do. A payment-chaser flow might remind the account owner that an invoice is overdue, while leaving customer contact to them. A stock warning may open a purchasing task without placing an order. Boundaries make testing possible and prevent staff from assuming the system has handled work beyond its remit. Add a visible marker to records created or changed automatically.
Make the fallback part of the design
Mapping detail
Every recipe needs a place for records it cannot process. Use a review queue with the original input, failure reason and suggested next step. Avoid catch-all error emails that reveal little and are soon ignored. Decide whether a retry is safe; repeated invoice creation is not, while retrying a failed internal notification may be. Retain the manual procedure so the business can continue during supplier outages.
Retire recipes that no longer match the work
Mapping detail
Review each flow when software, pricing, staff responsibilities or customer terms change. Check its last successful and failed runs, not merely whether it is switched on. Ask the people receiving its output whether they still use it. Disable duplicate or obsolete flows in a controlled way and preserve a short change record. Automation should reduce uncertainty, not leave hidden rules that nobody feels able to challenge.
Practical cards
Seven bounded automation recipes
Each illustrative recipe includes a stopping point so it can be trialled without handing over judgement.
Attachment filingWhen a tagged supplier email arrives, save its PDF to the matching job folder and alert staff if no job reference matches; do not delete the email.
Quote preparationCopy approved enquiry details into a quote draft and assign it for review; do not calculate unusual work or send the quote.
Job-start packAfter a job is approved, create the standard folder and checklist; stop if the customer or site reference is incomplete.
Completion checkWhen field staff mark work complete, ask for missing photos or notes; do not mark the contractual job complete automatically.
Invoice draftPrepare a draft from an approved completion record and current price source; require accounts approval before issue.
Overdue invoice taskCreate a task for the account owner when an invoice passes its due date; exclude disputed accounts and do not auto-send threats.
Low-stock warningNotify purchasing when recorded stock crosses a set level; show recent usage and outstanding orders, but do not place an order.
Review request promptAfter a genuinely completed job, prompt staff to decide whether a neutral review invitation is suitable; do not filter recipients by expected sentiment.
