Most agency work still moves as files, inboxes, and re-keyed forms. Automation is not a single product. It is a pipeline: capture the request, check it against policy, route exceptions to people, and write the result back to the system of record. This field guide is how we pick the first processes worth automating.
Find the work that repeats
Walk a single transaction from intake to close. Count handoffs, systems touched, and time spent waiting. The best candidates are high volume, rule-heavy, and painful when they are late: invoice intake, license renewals, eligibility packets, records requests, and help-desk triage.
Skip processes that change every week or that exist only in one person’s head until you document them. Automation without a stable procedure just fails faster.
Separate the happy path from judgment
Encode the 70 to 80% of cases that follow a checklist. Leave the ambiguous remainder to specialists, with the SI or bot preparing a packet instead of making the call. That split is what keeps automation inside policy and union agreements.
Choose the thinnest reliable tool
- RPA when the system of record has no API and the UI is stable.
- Workflow / integration (Power Automate, n8n, or an ESB) when APIs exist.
- Document intelligence when the bottleneck is PDFs, emails, and scanned forms.
- A small language model with retrieval when the work is reading policy and drafting a first response.
Do not start with a platform bake-off. Start with one pipeline and the controls it must satisfy.
Build the operational envelope
Logging, role-based access, retention, and a kill switch are part of the pipeline, not an appendix. Staff need a queue of exceptions, not a black box. Measure baseline cycle time before go-live so you can prove the gain.
Sequence for trust
Pilot with a team that wants the help. Publish before-and-after numbers. Retrain the hours you give back into exception handling and citizen contact. Expand only when the first pipeline is boring; that is the sign it is working.
Paperwork becomes a pipeline when the agency treats automation as operations: owned, observable, and reversible. That is how manual processes shrink without a moonshot rewrite.