| name | sop-generation |
| description | Generate Standard Operating Procedures in GxP compliant format with purpose, scope, responsibilities, procedure steps, references, version control, and approval workflows. |
SOP Generation
Purpose
Generate Standard Operating Procedures (SOPs) for Talosix clinical trial EDC operations. SOPs must follow GxP-compliant format and satisfy regulatory expectations for documented procedures governing validated system use.
When to Use
- New process requires formal documentation
- Existing SOP needs revision due to system or process changes
- Change control identifies SOP update requirement
- Audit finding requires new or improved procedure documentation
- New regulatory requirement necessitates procedural controls
- Client onboarding requires process documentation
SOP Document Structure
Every SOP follows this standardized structure:
Header Block
STANDARD OPERATING PROCEDURE
Document ID: SOP-[DEPT]-[SEQ]-[VER]
Title: [Descriptive title]
Version: [X.Y]
Effective Date: [DATE]
Review Date: [DATE - typically effective + 2 years]
Page: [X of Y]
Department: [Owning department]
Author: [Name, Title]
Reviewer: [Name, Title]
Approver: [Name, Title]
Classification: [GxP Critical / GxP Supporting / Business]
Document Control Table
| Version | Date | Author | Change Description | Approved By |
|---------|------|--------|-------------------|-------------|
| 1.0 | [DATE] | [NAME] | Initial release | [NAME] |
Section 1: Purpose
State why this SOP exists. One to three sentences. Must clearly convey the regulatory or operational need.
Example: "This SOP defines the procedure for managing user access to Talosix EDC production systems to ensure compliance with 21 CFR Part 11 requirements for system access controls and unique user identification."
Section 2: Scope
Define what is covered and what is excluded.
- Systems in scope
- Processes in scope
- Personnel in scope
- Exclusions (with reference to other SOPs if applicable)
Section 3: Definitions and Abbreviations
List all specialized terms and abbreviations used in the procedure.
Section 4: Responsibilities
Define roles and their responsibilities in a table:
| Role | Responsibility |
|------|---------------|
| System Owner | [Specific responsibilities] |
| QA Manager | [Specific responsibilities] |
| System Administrator | [Specific responsibilities] |
| End Users | [Specific responsibilities] |
Section 5: Procedure
The core procedural steps. Follow these conventions:
- Number all steps sequentially (5.1, 5.2, 5.3, etc.)
- Sub-steps use decimal notation (5.1.1, 5.1.2)
- Use imperative voice ("Review the request" not "The request should be reviewed")
- Include decision points with clear criteria
- Reference forms, templates, and tools by document ID
- Identify responsible role for each step
- Include timelines where applicable (e.g., "within 5 business days")
Example structure:
5.1 Initiation
5.1.1 [Role] performs [action] using [tool/form]
5.1.2 [Role] verifies [criteria]
5.2 Review
5.2.1 [Role] reviews [item] against [criteria]
5.2.2 If [condition], proceed to 5.3
If [other condition], return to 5.1 with [action]
5.3 Approval
5.3.1 [Role] approves [item] by [method]
5.3.2 [Role] documents approval in [system/form]
Section 6: Records and Documentation
List all records generated by this procedure:
| Record | Format | Storage Location | Retention Period | Responsible |
|--------|--------|-----------------|------------------|-------------|
Section 7: References
List related documents:
- Regulatory references (CFR, Annex 11, ICH guidelines)
- Related SOPs
- Work instructions
- Templates and forms
- External standards
Section 8: Attachments
List and include any:
- Flowcharts
- Forms and templates
- Checklists
- Decision trees
Section 9: Revision History
Detailed change log for all versions.
Common SOPs for EDC Operations
System Management SOPs
SOP-SYS-001: System Validation
SOP-SYS-002: Change Control Management
SOP-SYS-003: Configuration Management
SOP-SYS-004: Incident Management
SOP-SYS-005: Problem Management
SOP-SYS-006: Release Management
SOP-SYS-007: Backup and Recovery
SOP-SYS-008: Disaster Recovery
SOP-SYS-009: System Retirement and Data Archiving
SOP-SYS-010: Periodic System Review
User and Access Management SOPs
SOP-ACC-001: User Account Management
SOP-ACC-002: Role-Based Access Control
SOP-ACC-003: Periodic Access Review
SOP-ACC-004: Password and Authentication Policy
SOP-ACC-005: Electronic Signature Management
Data Management SOPs
SOP-DAT-001: Study Build and Configuration
SOP-DAT-002: Data Entry Procedures
SOP-DAT-003: Query Management
SOP-DAT-004: Data Review and Cleaning
SOP-DAT-005: Database Lock Procedures
SOP-DAT-006: Data Export and Transfer
SOP-DAT-007: Data Migration
SOP-DAT-008: Medical Coding
SOP-DAT-009: SAE Reconciliation
SOP-DAT-010: CDISC Standards Compliance
Quality Management SOPs
SOP-QMS-001: Document Control
SOP-QMS-002: Training Management
SOP-QMS-003: CAPA Management
SOP-QMS-004: Internal Audit
SOP-QMS-005: Deviation Management
SOP-QMS-006: Risk Management
SOP-QMS-007: Vendor Qualification and Management
SOP-QMS-008: Regulatory Inspection Readiness
Security SOPs
SOP-SEC-001: Information Security Management
SOP-SEC-002: Security Incident Response
SOP-SEC-003: Vulnerability Management
SOP-SEC-004: Encryption and Key Management
SOP-SEC-005: Physical and Environmental Security
GxP Compliance Requirements for SOPs
Document Control
- Every SOP must have a unique document ID
- Version numbering: major.minor (1.0, 1.1, 2.0)
- Major version increment for substantive changes
- Minor version increment for editorial/formatting changes
- Only the current approved version is effective
- Superseded versions retained per retention policy
- Controlled distribution (electronic preferred)
Review and Approval Cycle
Draft → Author Review → Peer Review → QA Review → Approval → Effective
Timeline expectations:
- Draft to peer review: 5 business days
- Peer review completion: 5 business days
- QA review completion: 5 business days
- Approval: 3 business days
- Training completion: 10 business days after effective date
Periodic Review
- All GxP SOPs reviewed every 2 years at minimum
- Review triggered earlier by: regulatory changes, audit findings, process changes, incidents
- Review must confirm SOP still reflects current practice
- Review documented even if no changes needed ("reviewed, no changes required")
Training Requirements
- All personnel performing SOP procedures must be trained before executing the procedure
- Training documented with: trainee name, SOP ID and version, training date, training method, trainer/assessor
- Refresher training required when SOP is revised
- Training effectiveness assessed for GxP critical SOPs
Writing Standards
Language
- Clear, unambiguous, imperative statements
- Consistent terminology (define in Section 3)
- Avoid passive voice in procedural steps
- Use "shall" for mandatory requirements
- Use "should" for recommended practices
- Use "may" for optional actions
Formatting
- Consistent heading hierarchy
- Numbered steps (not bullets) for sequential procedures
- Tables for reference information
- Flowcharts for decision-heavy processes
- Bold for key terms on first use
- Cross-references by document ID, not page number
Regulatory Language
- Reference specific regulation sections (e.g., "per 21 CFR 11.10(e)")
- Use regulatory terminology correctly (e.g., "predicate rule" not "underlying rule")
- Align with ICH terminology where applicable
Output Format
When generating an SOP, produce:
- Complete SOP document following the structure above
- Associated forms and templates referenced in the procedure
- Process flowchart (described in text for diagram generation)
- Training assessment questions (3-5 questions per SOP)
- Implementation checklist
Regulatory References
- 21 CFR Part 11 - Section 11.10(j): Written policies
- EU Annex 11 - Section 2: Personnel (training documentation)
- ICH E6(R2) - Section 5.1: Quality Assurance and Quality Control
- ICH Q10 - Pharmaceutical Quality System
- ISPE GAMP 5 - Operational SOPs
- ISO 9001 - Document control requirements (adapted)
