Define where the automation starts and ends
Choose a recurring task with an identifiable output, such as a triage brief, extraction table, or project update. Use conventional rules for steps that do not need model interpretation.
Intake and classification
Extract required details, suggest a category, and identify missing context from forms, messages, or tickets.
Document and summary preparation
Create structured drafts from approved records with references that make checking easier.
Reviewed handoff
Present the proposed destination and action to a reviewer before a consequential system update or external message.
Decide what happens when a step fails
Missing sources, ambiguous requests, unavailable tools, and rejected drafts are ordinary workflow states. Define when the process stops, who receives the exception, and how a person resumes work. A failed model call must not silently become a successful business action.
Implementation and handover
Evaluate the time needed to complete the task, including human review and exceptions, before deciding whether to expand.
- Workflow map with triggers, source access, allowed tools, and review gates.
- Configured first workflow and representative acceptance tests.
- Evidence of denied actions, failures, corrections, and approved outputs.
- Operating notes covering retry behavior, pause and recovery, and change ownership.