# AI workflow design sheet Use this sheet to define one practical workflow before selecting products or connecting systems. Leave unknowns visible. The blank fields are for your own decisions; this is not a record of an implemented or tested system. ## 1. Define the task | Field | Your answer | |---|---| | Workflow name | | | Business problem | | | Person responsible for the result | | | Trigger: what starts the work? | | | Intended user or customer | | | Current process | | | Desired result | | | What is outside this task? | | Describe a successful result in one sentence: > When __________ happens, the workflow produces __________, which __________ checks and uses to __________. ## 2. Specify the input and output | Question | Your answer | |---|---| | Which source supplies the input? | | | Is this use permitted, and who controls access? | | | Which fields are actually needed? | | | Which source date or version matters? | | | What must the output contain? | | | Which evidence must accompany the output? | | | How should missing or conflicting information appear? | | | Where does an accepted result go? | | Attach one fictional input and your expected output. Mark them as examples. ## 3. Choose the interface and execution approach These are separate decisions. - **Interface:** form, chat, document upload, email intake or another entry point. - **Execution:** predefined steps, an agent choosing permitted tools, or a combination. Explain why the task needs that approach. If you choose an agent, name the decisions that cannot usefully be fixed in advance. ## 4. Set the action boundary | Action | Allowed scope | Review or approval, if required | Responsible person | |---|---|---|---| | Read source information | | | | | Prepare a draft | | | | | Create or update a record | | | | | Send an external message | | | | | Make another commitment | | | | Define what happens when a request falls outside that scope. Write down who can change these permissions. ## 5. Draft the instruction > Use the supplied __________ to produce __________. Include these fields: __________. Keep explicit facts separate from assumptions. Show missing or contradictory information as __________. Include source evidence in __________. You may __________. Refer __________ to __________. The result will be checked by __________ before __________. Adapt the instruction to the task. A prompt does not replace access controls or implementation checks. ## 6. Plan representative checks Write expected handling before running the examples. | Example | Expected handling | Observed result | Correction needed | |---|---|---|---| | Complete input | | | | | Required information missing | | | | | Two sources disagree | | | | | Duplicate submission | | | | | Source or tool unavailable | | | | | Request outside allowed scope | | | | ## 7. Measure the complete process Record actual observations. Do not fill these fields with assumed savings. | Measure | Existing process | Proposed workflow | |---|---|---| | Comparable tasks observed | | | | Input preparation time | | | | Execution time | | | | Review and correction time | | | | Handoff time | | | | Accepted results and total attempts | | | | Recurring errors or missing information | | | | Measured usage cost, where available | | | ## 8. Name the ongoing owner - Who updates source material and permissions? - Who notices failures and handles unresolved cases? - How can the workflow be paused or reverted? - Where are decisions and corrections recorded? - When will the result be reviewed again? **Next implementation decision:** __________ **Owner and review date:** __________