Working markdown template
Document one AI-assisted workflow end to end.
Capture the tool, allowed inputs, output, reviewer, approval checkpoint, escalation path, and retention rule before an AI workflow is reused.
Step 1 · Fill the SOP
Workflow details
Use this for any AI-assisted task that could become repeatable, customer-facing, examiner-facing, or part of a retained business record.
Step 2 · Review
Before this SOP is adopted
Markdown output
ai-workflow-sop-template.md
# AI-Assisted Procedure Summary Workflow **Department:** Operations **Workflow owner:** Department lead **Risk tier:** Yellow **Status:** Draft --- ## 1. Business Purpose Use an approved AI tool to convert internal procedure text into a plain-English draft summary for staff review. --- ## 2. Approved Tool Approved AI writing assistant --- ## 3. Allowed Inputs Approved internal procedure text, role/audience, process owner, known exceptions, review owner. --- ## 4. Prohibited Inputs Customer names, account numbers, balances, transactions, SSNs, DOBs, confidential records, examiner correspondence, legal advice requests, SAR or AML case details, authentication details, API keys, passwords, or access tokens. --- ## 5. Prompt / Task Instructions Rewrite the approved procedure text into a plain-English staff summary. Preserve policy meaning. Do not add requirements. Flag unclear or missing information with [VERIFY]. Label output as draft pending review. --- ## 6. Expected Output Draft staff-facing summary with purpose, key steps, exceptions, escalation triggers, and reviewer checklist. --- ## 7. Human Reviewer Department lead or process owner --- ## 8. Review Standard Reviewer confirms the source meaning was preserved, no prohibited data was included, uncertain items are flagged, escalation language is accurate, and the output is labeled draft until approved. --- ## 9. Approval Checkpoint The output may be distributed only after the human reviewer approves the final version. --- ## 10. Retention Rule Save only the reviewed final version and source reference in the approved internal repository or toolbox. Do not retain unreviewed drafts as official records. --- ## 11. Escalation Triggers Escalate to Compliance, Legal, InfoSec, or Risk if the workflow touches customer impact, credit, BSA/AML, fraud, authentication, complaints, examiner-facing material, confidential records, or uncertain regulatory interpretation. --- ## 12. Review Checklist - [ ] Business purpose is clear - [ ] Approved tool is named - [ ] Allowed inputs are defined - [ ] Prohibited inputs are explicit - [ ] Human reviewer is identified - [ ] Approval checkpoint is documented - [ ] Retention rule is defined - [ ] Escalation triggers are listed --- ## 13. Final Approval | Field | Response | |---|---| | Reviewed by | | | Review date | | | Approved for use? | Yes / No / Conditional | | Conditions or notes | | | Next review date | |
How to use this template
Use for repeatable work
If the workflow will be reused, document it before scaling.
Name the reviewer
Medium and high-risk outputs need a clear accountable human owner.
Define the data boundary
Allowed and prohibited inputs should be clear before anyone runs the prompt.
Retain the reviewed version
Save final reviewed outputs, not messy draft exchanges, as the business record.