Prompt file imported from steikould/center_of_excellence_personas (.github/prompts/process-engineer/pe-03-sop-generation.prompt.md). Copyright stays with the author.

PE-03 — AI-Enhanced SOP Generation

Name: pe-03-sop-generation
Author: steikould

Goal: Use Copilot to design an SOP template system, generate SOPs from process descriptions, and build a workflow that maintains version control and regulatory compliance.

What You're Learning

How to use Copilot as a drafting partner for regulated documents
Template design that balances consistency with flexibility
Version control discipline for controlled documents
How AI-assisted drafting fits within a GMP quality system

Concept: SOPs in a Regulated World

SOPs are not optional documentation — they are legally binding instructions. In a GMP environment:

SOPs must be approved before use and reviewed on a defined cycle
Every revision must be tracked with a rationale for the change
Personnel must be trained on the current version before performing the procedure
Deviations from SOPs must be documented and investigated
During an audit, SOPs are primary evidence that you do what you say you do

AI can accelerate SOP creation and maintenance, but it cannot replace:

Subject matter expert review of technical accuracy
QA approval of regulatory compliance
Training verification before an SOP is effective
Change control when revising an existing SOP

The sweet spot for AI: first draft generation, consistency checking, gap identification, and revision tracking.

The Challenge

Part 1 — Design Your SOP Template

Work with Copilot to create a robust SOP template that works for your organization:

#file:personas/process-engineer/copilot-instructions.md

Help me design a comprehensive SOP template for a GMP animal pharmaceutical manufacturing facility. The template must include:

Header section:
- SOP number (format: [DEPT]-[CATEGORY]-[SEQ]-[REV], e.g., QC-ANAL-001-R03)
- Title
- Effective date
- Next review date (based on review cycle: 1 year for operational, 2 years for administrative)
- Document owner, author, and approvers (with signature/date lines)
- Supersedes (previous version reference)

Body sections:
1. PURPOSE — Why this SOP exists (one paragraph)
2. SCOPE — What is covered and explicitly what is NOT covered
3. RESPONSIBILITIES — Table of roles and their responsibilities for this procedure
4. DEFINITIONS — Terms specific to this procedure
5. SAFETY PRECAUTIONS — If applicable (PPE, chemical handling, equipment hazards)
6. MATERIALS AND EQUIPMENT — What is needed to perform the procedure
7. PROCEDURE — Numbered steps with action verbs, specific parameters, and acceptance criteria
8. DOCUMENTATION — What records must be created/completed
9. REFERENCES — Related SOPs, regulations, guidelines, specifications
10. ATTACHMENTS — Forms, checklists, decision trees
11. REVISION HISTORY — Table: version, date, description of change, reason for change

Also include guidance notes (in italics) within each section explaining what content should go there, so anyone using this template knows what to write.

Part 2 — Generate an SOP from a Process Description

Pick a real procedure you need to document (or update). Describe it to Copilot in plain language:

Using the SOP template we just designed, generate a complete SOP from this process description:

Process: [describe the procedure in your own words — be as detailed as you can, but don't worry about formal language]

Context:
- Department: [e.g., Quality Control, Manufacturing, Warehouse]
- Regulatory requirements: [e.g., "Must comply with USP <71> sterility testing requirements"]
- Systems involved: [e.g., "Results recorded in LIMS, batch record updated in ERP"]
- Critical parameters: [e.g., "Temperature must be maintained at 20-25°C throughout"]
- Common failure modes: [e.g., "Contamination during sample transfer is the #1 risk"]

Generate the full SOP. For the procedure section:
- Every step starts with an action verb
- Include specific parameters, not "appropriate" or "sufficient"
- Add NOTE callouts for critical steps where errors commonly occur
- Add HOLD POINT callouts where QA verification is required before proceeding
- Include exception handling: what to do if a step fails or produces an unexpected result

Review the output critically. Copilot will produce a solid draft, but you are the subject matter expert. Fix technical inaccuracies, add missing steps, and sharpen any vague language.

Part 3 — Consistency and Compliance Check

Use Copilot to review the SOP against quality standards:

Review the SOP we just created against these criteria:

1. REGULATORY COMPLIANCE
   - Does every step that generates a record reference 21 CFR Part 11 requirements?
   - Are data integrity principles (ALCOA+) addressed where data is recorded?
   - Are there clear instructions for what to do when a deviation from this SOP occurs?

2. CLARITY AND SPECIFICITY
   - Are all steps unambiguous? Could two trained people perform the same step identically?
   - Are all parameters specific (numbers, ranges, units) rather than subjective ("appropriate," "sufficient")?
   - Are decision points clear (if/then, not "use professional judgment")?

3. COMPLETENESS
   - Is every input accounted for (materials, data, approvals)?
   - Is every output defined (records, results, notifications)?
   - Are all exception paths documented?

4. CROSS-REFERENCES
   - Are all referenced SOPs, specifications, and regulations correctly cited?
   - Are there SOPs that should be referenced but aren't?

5. TRAINING IMPLICATIONS
   - What training is required before someone can perform this procedure?
   - Are there steps that require specific qualifications or certifications?

Score each criterion 1-5 and provide specific findings with recommended corrections.

Part 4 — Version Control and Revision Workflow

Design a system for managing SOP revisions with AI assistance:

Help me design an AI-assisted SOP revision workflow:

1. REVISION TRIGGER: What events should trigger an SOP review?
   (Deviation, CAPA, regulatory change, process change, periodic review, audit finding)

2. CHANGE ASSESSMENT: When a revision is needed, how do we classify the change?
   - Editorial (typos, formatting) → no retraining required
   - Minor (clarification, adding detail) → read-and-understand training
   - Major (process change, new steps, removed steps) → formal retraining with assessment

3. DRAFTING: How can Copilot help with revisions?
   - Generate redline comparison between versions
   - Identify all downstream impacts (other SOPs that reference this one, training records)
   - Draft the revision history entry
   - Update cross-references automatically

4. REVIEW AND APPROVAL: What's the workflow?
   - SME review → QA review → Department head approval → Training coordinator notification

5. TRACKING: Design a revision tracking table that captures:
   - Version, date, change type, change description, reason, regulatory impact, training impact

Create a complete SOP revision management workflow as a process map (Mermaid) and a checklist.

Save Step

Save these artifacts to personas/process-engineer/workspace/artifacts/:

pe-03-sop-template.md — Your master SOP template with guidance notes
pe-03-sample-sop.md — The SOP you generated from a process description
pe-03-revision-workflow.md — The AI-assisted revision management process

Save the SOP template also as a reusable prompt:

personas/process-engineer/workspace/prompts/sop-generator.prompt.md — A prompt that takes a process description and generates a compliant SOP

Mark PE-03 complete in your personas/process-engineer/journey.md.

Stretch Goal

Generate a "family" of related SOPs — a parent SOP that references 2-3 child SOPs. For example:

Parent: Batch Record Review and Release
- Child 1: In-Process Testing Review
- Child 2: Certificate of Analysis Generation
- Child 3: Deviation Assessment During Batch Review

Show how the cross-references connect them and how a change in one ripples to the others.

Next: PE-04 — Continuous Improvement Metrics

# PE-03 — AI-Enhanced SOP Generation > **Goal**: Use Copilot to design an SOP template system, generate SOPs from process descriptions, and build a workflow that maintains version control and regulatory compliance. --- ## What You're Learning - How to use Copilot as a drafting partner for regulated documents - Template design that balances consistency with flexibility - Version control discipline for controlled documents - How AI-assisted drafting fits within a GMP quality system ## Concept: SOPs in a Regulated World SOPs are not optional documentation — they are legally binding instructions. In a GMP environment: - SOPs must be approved before use and reviewed on a defined cycle - Every revision must be tracked with a rationale for the change - Personnel must be trained on the current version before performing the procedure - Deviations from SOPs must be documented and investigated - During an audit, SOPs are primary evidence that you do what you say you do AI can accelerate SOP creation and maintenance, but it cannot replace: - Subject matter expert review of technical accuracy - QA approval of regulatory compliance - Training verification before an SOP is effective - Change control when revising an existing SOP The sweet spot for AI: **first draft generation, consistency checking, gap identification, and revision tracking.** ## The Challenge ### Part 1 — Design Your SOP Template Work with Copilot to create a robust SOP template that works for your organization: ``` #file:personas/process-engineer/copilot-instructions.md Help me design a comprehensive SOP template for a GMP animal pharmaceutical manufacturing facility. The template must include: Header section: - SOP number (format: [DEPT]-[CATEGORY]-[SEQ]-[REV], e.g., QC-ANAL-001-R03) - Title - Effective date - Next review date (based on review cycle: 1 year for operational, 2 years for administrative) - Document owner, author, and approvers (with signature/date lines) - Supersedes (previous version reference) Body sections: 1. PURPOSE — Why this SOP exists (one paragraph) 2. SCOPE — What is covered and explicitly what is NOT covered 3. RESPONSIBILITIES — Table of roles and their responsibilities for this procedure 4. DEFINITIONS — Terms specific to this procedure 5. SAFETY PRECAUTIONS — If applicable (PPE, chemical handling, equipment hazards) 6. MATERIALS AND EQUIPMENT — What is needed to perform the procedure 7. PROCEDURE — Numbered steps with action verbs, specific parameters, and acceptance criteria 8. DOCUMENTATION — What records must be created/completed 9. REFERENCES — Related SOPs, regulations, guidelines, specifications 10. ATTACHMENTS — Forms, checklists, decision trees 11. REVISION HISTORY — Table: version, date, description of change, reason for change Also include guidance notes (in italics) within each section explaining what content should go there, so anyone using this template knows what to write. ``` ### Part 2 — Generate an SOP from a Process Description Pick a real procedure you need to document (or update). Describe it to Copilot in plain language: ``` Using the SOP template we just designed, generate a complete SOP from this process description: Process: [describe the procedure in your own words — be as detailed as you can, but don't worry about formal language] Context: - Department: [e.g., Quality Control, Manufacturing, Warehouse] - Regulatory requirements: [e.g., "Must comply with USP <71> sterility testing requirements"] - Systems involved: [e.g., "Results recorded in LIMS, batch record updated in ERP"] - Critical parameters: [e.g., "Temperature must be maintained at 20-25°C throughout"] - Common failure modes: [e.g., "Contamination during sample transfer is the #1 risk"] Generate the full SOP. For the procedure section: - Every step starts with an action verb - Include specific parameters, not "appropriate" or "sufficient" - Add NOTE callouts for critical steps where errors commonly occur - Add HOLD POINT callouts where QA verification is required before proceeding - Include exception handling: what to do if a step fails or produces an unexpected result ``` Review the output critically. Copilot will produce a solid draft, but you are the subject matter expert. Fix technical inaccuracies, add missing steps, and sharpen any vague language. ### Part 3 — Consistency and Compliance Check Use Copilot to review the SOP against quality standards: ``` Review the SOP we just created against these criteria: 1. REGULATORY COMPLIANCE - Does every step that generates a record reference 21 CFR Part 11 requirements? - Are data integrity principles (ALCOA+) addressed where data is recorded? - Are there clear instructions for what to do when a deviation from this SOP occurs? 2. CLARITY AND SPECIFICITY - Are all steps unambiguous? Could two trained people perform the same step identically? - Are all parameters specific (numbers, ranges, units) rather than subjective ("appropriate," "sufficient")? - Are decision points clear (if/then, not "use professional judgment")? 3. COMPLETENESS - Is every input accounted for (materials, data, approvals)? - Is every output defined (records, results, notifications)? - Are all exception paths documented? 4. CROSS-REFERENCES - Are all referenced SOPs, specifications, and regulations correctly cited? - Are there SOPs that should be referenced but aren't? 5. TRAINING IMPLICATIONS - What training is required before someone can perform this procedure? - Are there steps that require specific qualifications or certifications? Score each criterion 1-5 and provide specific findings with recommended corrections. ``` ### Part 4 — Version Control and Revision Workflow Design a system for managing SOP revisions with AI assistance: ``` Help me design an AI-assisted SOP revision workflow: 1. REVISION TRIGGER: What events should trigger an SOP review? (Deviation, CAPA, regulatory change, process change, periodic review, audit finding) 2. CHANGE ASSESSMENT: When a revision is needed, how do we classify the change? - Editorial (typos, formatting) → no retraining required - Minor (clarification, adding detail) → read-and-understand training - Major (process change, new steps, removed steps) → formal retraining with assessment 3. DRAFTING: How can Copilot help with revisions? - Generate redline comparison between versions - Identify all downstream impacts (other SOPs that reference this one, training records) - Draft the revision history entry - Update cross-references automatically 4. REVIEW AND APPROVAL: What's the workflow? - SME review → QA review → Department head approval → Training coordinator notification 5. TRACKING: Design a revision tracking table that captures: - Version, date, change type, change description, reason, regulatory impact, training impact Create a complete SOP revision management workflow as a process map (Mermaid) and a checklist. ``` ## Save Step Save these artifacts to `personas/process-engineer/workspace/artifacts/`: - `pe-03-sop-template.md` — Your master SOP template with guidance notes - `pe-03-sample-sop.md` — The SOP you generated from a process description - `pe-03-revision-workflow.md` — The AI-assisted revision management process Save the SOP template also as a reusable prompt: - `personas/process-engineer/workspace/prompts/sop-generator.prompt.md` — A prompt that takes a process description and generates a compliant SOP Mark PE-03 complete in your `personas/process-engineer/journey.md`. ## Stretch Goal Generate a "family" of related SOPs — a parent SOP that references 2-3 child SOPs. For example: - Parent: Batch Record Review and Release - Child 1: In-Process Testing Review - Child 2: Certificate of Analysis Generation - Child 3: Deviation Assessment During Batch Review Show how the cross-references connect them and how a change in one ripples to the others. --- **Next**: PE-04 — Continuous Improvement Metrics

{ "prompt": "# PE-03 — AI-Enhanced SOP Generation\n\n> **Goal**: Use Copilot to design an SOP template system, generate SOPs from process descriptions, and build a workflow that maintains version control and regulatory compliance.\n\n---\n\n## What You're Learning\n- How to use Copilot as a drafting partner for regulated documents\n- Template design that balances consistency with flexibility\n- Version control discipline for controlled documents\n- How AI-assisted drafting fits within a GMP quality system\n\n## Concept: SOPs in a Regulated World\n\nSOPs are not optional documentation — they are legally binding instructions. In a GMP environment:\n- SOPs must be approved before use and reviewed on a defined cycle\n- Every revision must be tracked with a rationale for the change\n- Personnel must be trained on the current version before performing the procedure\n- Deviations from SOPs must be documented and investigated\n- During an audit, SOPs are primary evidence that you do what you say you do\n\nAI can accelerate SOP creation and maintenance, but it cannot replace:\n- Subject matter expert review of technical accuracy\n- QA approval of regulatory compliance\n- Training verification before an SOP is effective\n- Change control when revising an existing SOP\n\nThe sweet spot for AI: **first draft generation, consistency checking, gap identification, and revision tracking.**\n\n## The Challenge\n\n### Part 1 — Design Your SOP Template\n\nWork with Copilot to create a robust SOP template that works for your organization:\n\n```\n#file:personas/process-engineer/copilot-instructions.md\n\nHelp me design a comprehensive SOP template for a GMP animal pharmaceutical manufacturing facility. The template must include:\n\nHeader section:\n- SOP number (format: [DEPT]-[CATEGORY]-[SEQ]-[REV], e.g., QC-ANAL-001-R03)\n- Title\n- Effective date\n- Next review date (based on review cycle: 1 year for operational, 2 years for administrative)\n- Document owner, author, and approvers (with signature/date lines)\n- Supersedes (previous version reference)\n\nBody sections:\n1. PURPOSE — Why this SOP exists (one paragraph)\n2. SCOPE — What is covered and explicitly what is NOT covered\n3. RESPONSIBILITIES — Table of roles and their responsibilities for this procedure\n4. DEFINITIONS — Terms specific to this procedure\n5. SAFETY PRECAUTIONS — If applicable (PPE, chemical handling, equipment hazards)\n6. MATERIALS AND EQUIPMENT — What is needed to perform the procedure\n7. PROCEDURE — Numbered steps with action verbs, specific parameters, and acceptance criteria\n8. DOCUMENTATION — What records must be created/completed\n9. REFERENCES — Related SOPs, regulations, guidelines, specifications\n10. ATTACHMENTS — Forms, checklists, decision trees\n11. REVISION HISTORY — Table: version, date, description of change, reason for change\n\nAlso include guidance notes (in italics) within each section explaining what content should go there, so anyone using this template knows what to write.\n```\n\n### Part 2 — Generate an SOP from a Process Description\n\nPick a real procedure you need to document (or update). Describe it to Copilot in plain language:\n\n```\nUsing the SOP template we just designed, generate a complete SOP from this process description:\n\nProcess: [describe the procedure in your own words — be as detailed as you can, but don't worry about formal language]\n\nContext:\n- Department: [e.g., Quality Control, Manufacturing, Warehouse]\n- Regulatory requirements: [e.g., \"Must comply with USP <71> sterility testing requirements\"]\n- Systems involved: [e.g., \"Results recorded in LIMS, batch record updated in ERP\"]\n- Critical parameters: [e.g., \"Temperature must be maintained at 20-25°C throughout\"]\n- Common failure modes: [e.g., \"Contamination during sample transfer is the #1 risk\"]\n\nGenerate the full SOP. For the procedure section:\n- Every step starts with an action verb\n- Include specific parameters, not \"appropriate\" or \"sufficient\"\n- Add NOTE callouts for critical steps where errors commonly occur\n- Add HOLD POINT callouts where QA verification is required before proceeding\n- Include exception handling: what to do if a step fails or produces an unexpected result\n```\n\nReview the output critically. Copilot will produce a solid draft, but you are the subject matter expert. Fix technical inaccuracies, add missing steps, and sharpen any vague language.\n\n### Part 3 — Consistency and Compliance Check\n\nUse Copilot to review the SOP against quality standards:\n\n```\nReview the SOP we just created against these criteria:\n\n1. REGULATORY COMPLIANCE\n - Does every step that generates a record reference 21 CFR Part 11 requirements?\n - Are data integrity principles (ALCOA+) addressed where data is recorded?\n - Are there clear instructions for what to do when a deviation from this SOP occurs?\n\n2. CLARITY AND SPECIFICITY\n - Are all steps unambiguous? Could two trained people perform the same step identically?\n - Are all parameters specific (numbers, ranges, units) rather than subjective (\"appropriate,\" \"sufficient\")?\n - Are decision points clear (if/then, not \"use professional judgment\")?\n\n3. COMPLETENESS\n - Is every input accounted for (materials, data, approvals)?\n - Is every output defined (records, results, notifications)?\n - Are all exception paths documented?\n\n4. CROSS-REFERENCES\n - Are all referenced SOPs, specifications, and regulations correctly cited?\n - Are there SOPs that should be referenced but aren't?\n\n5. TRAINING IMPLICATIONS\n - What training is required before someone can perform this procedure?\n - Are there steps that require specific qualifications or certifications?\n\nScore each criterion 1-5 and provide specific findings with recommended corrections.\n```\n\n### Part 4 — Version Control and Revision Workflow\n\nDesign a system for managing SOP revisions with AI assistance:\n\n```\nHelp me design an AI-assisted SOP revision workflow:\n\n1. REVISION TRIGGER: What events should trigger an SOP review?\n (Deviation, CAPA, regulatory change, process change, periodic review, audit finding)\n\n2. CHANGE ASSESSMENT: When a revision is needed, how do we classify the change?\n - Editorial (typos, formatting) → no retraining required\n - Minor (clarification, adding detail) → read-and-understand training\n - Major (process change, new steps, removed steps) → formal retraining with assessment\n\n3. DRAFTING: How can Copilot help with revisions?\n - Generate redline comparison between versions\n - Identify all downstream impacts (other SOPs that reference this one, training records)\n - Draft the revision history entry\n - Update cross-references automatically\n\n4. REVIEW AND APPROVAL: What's the workflow?\n - SME review → QA review → Department head approval → Training coordinator notification\n\n5. TRACKING: Design a revision tracking table that captures:\n - Version, date, change type, change description, reason, regulatory impact, training impact\n\nCreate a complete SOP revision management workflow as a process map (Mermaid) and a checklist.\n```\n\n## Save Step\n\nSave these artifacts to `personas/process-engineer/workspace/artifacts/`:\n- `pe-03-sop-template.md` — Your master SOP template with guidance notes\n- `pe-03-sample-sop.md` — The SOP you generated from a process description\n- `pe-03-revision-workflow.md` — The AI-assisted revision management process\n\nSave the SOP template also as a reusable prompt:\n- `personas/process-engineer/workspace/prompts/sop-generator.prompt.md` — A prompt that takes a process description and generates a compliant SOP\n\nMark PE-03 complete in your `personas/process-engineer/journey.md`.\n\n## Stretch Goal\n\nGenerate a \"family\" of related SOPs — a parent SOP that references 2-3 child SOPs. For example:\n- Parent: Batch Record Review and Release\n - Child 1: In-Process Testing Review\n - Child 2: Certificate of Analysis Generation\n - Child 3: Deviation Assessment During Batch Review\n\nShow how the cross-references connect them and how a change in one ripples to the others.\n\n---\n\n**Next**: PE-04 — Continuous Improvement Metrics", "variables": [], "notes": "SOPs are not optional documentation — they are legally binding instructions. In a GMP environment: - SOPs must be approved before use and reviewed on a defined cycle - Every revision must be tracked with a rationale for the change - Personnel must be trained on the current version before performing the procedure - Deviations from SOPs must be documented and investigated - During an audit, SOPs are primary evidence that you do what you say you do", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/steikould/center_of_excellence_personas", "path": ".github/prompts/process-engineer/pe-03-sop-generation.prompt.md", "ref": "1872309cfc57f4a821a765ef386508d6be8de68a", "url": "https://github.com/steikould/center_of_excellence_personas/blob/1872309cfc57f4a821a765ef386508d6be8de68a/.github/prompts/process-engineer/pe-03-sop-generation.prompt.md", "key": "steikould/center_of_excellence_personas/.github/prompts/process-engineer/pe-03-sop-generation.prompt.md" } } }

pe-03-sop-generation

About