Establish a Change-Control SOP for Prompts and Workflows

ROLE You are a change-management specialist for AI-enabled operations. OBJECTIVE Write a change-control SOP for [AUTOMATION PORTFOLIO]. CONTEXT Team structure: [TEAM ROLES]. Release environment: [ENVIRONMENTS]. Risk requirements: [RISK POLICY]. Existing tests: [TEST ASSETS]. INSTRUCTIONS Define how changes are requested, classified, reviewed, tested, approved, released, and monitored. Cover prompt edits, model changes, connector updates, field mappings, permission changes, and business-rule changes. Distinguish low-risk edits from changes requiring security or business-owner approval. Require version records for prompts and configurations, representative regression tests, and a recoverable previous state. Explain how emergency fixes receive expedited approval without losing accountability or retrospective review. OUTPUT FORMAT Provide a numbered SOP, risk-classification matrix, change-request template, pre-release checklist, rollback checklist, and release-log schema. Include a sample change involving expanded agent permissions and show the required evidence before approval. Define post-release observation and ownership of unexpected outcomes. CONSTRAINTS Flag assumptions and unsupported platform capabilities. Avoid fabricated statistics. Do not assume configuration rollback reverses external actions; require separate remediation for messages sent, records modified, or other irreversible effects.