generated from atomicai/getting-started
Initial commit
This commit is contained in:
89
Examples/SOP-001-Document-Control.md
Normal file
89
Examples/SOP-001-Document-Control.md
Normal file
@@ -0,0 +1,89 @@
|
||||
# SOP-001: Document Control Procedure
|
||||
|
||||
## Document Information
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Document ID** | SOP-001 |
|
||||
| **Version** | 1.0 |
|
||||
| **Effective Date** | 2024-01-15 |
|
||||
| **Review Date** | 2025-01-15 |
|
||||
| **Author** | Quality Manager |
|
||||
| **Approved By** | Director of Quality |
|
||||
|
||||
## 1. Purpose
|
||||
|
||||
This Standard Operating Procedure establishes the process for creating, reviewing, approving, and managing quality management system documents.
|
||||
|
||||
## 2. Scope
|
||||
|
||||
This procedure applies to all controlled documents within the Quality Management System, including:
|
||||
- Policies
|
||||
- Standard Operating Procedures (SOPs)
|
||||
- Work Instructions
|
||||
- Forms and Templates
|
||||
|
||||
## 3. Responsibilities
|
||||
|
||||
### 3.1 Document Author
|
||||
- Draft new documents or revisions
|
||||
- Submit documents for review via Pull Request
|
||||
- Address reviewer feedback
|
||||
|
||||
### 3.2 Document Reviewer
|
||||
- Review documents for accuracy and completeness
|
||||
- Provide feedback within 5 business days
|
||||
- Approve or request changes
|
||||
|
||||
### 3.3 Quality Manager
|
||||
- Maintain document numbering system
|
||||
- Ensure documents are properly archived
|
||||
- Coordinate annual document reviews
|
||||
|
||||
## 4. Procedure
|
||||
|
||||
### 4.1 Creating a New Document
|
||||
|
||||
1. Create a new branch from `main`
|
||||
2. Use the appropriate template from `/Templates`
|
||||
3. Assign a document number following the convention:
|
||||
- POL-XXX for Policies
|
||||
- SOP-XXX for Standard Operating Procedures
|
||||
- WI-XXX for Work Instructions
|
||||
- FRM-XXX for Forms
|
||||
4. Complete all required sections
|
||||
5. Submit a Pull Request for review
|
||||
|
||||
### 4.2 Document Review Process
|
||||
|
||||
1. Assign at least one reviewer to the Pull Request
|
||||
2. Reviewers have 5 business days to complete review
|
||||
3. Address all feedback before merging
|
||||
4. Obtain required approvals
|
||||
5. Merge to `main` branch
|
||||
|
||||
### 4.3 Document Revision
|
||||
|
||||
1. Create a new branch from `main`
|
||||
2. Update the version number
|
||||
3. Document changes in the Revision History section
|
||||
4. Follow the standard review process
|
||||
|
||||
## 5. Document Numbering
|
||||
|
||||
| Type | Format | Example |
|
||||
|------|--------|---------|
|
||||
| Policy | POL-XXX | POL-001 |
|
||||
| SOP | SOP-XXX | SOP-001 |
|
||||
| Work Instruction | WI-XXX | WI-001 |
|
||||
| Form | FRM-XXX | FRM-001 |
|
||||
|
||||
## 6. Revision History
|
||||
|
||||
| Version | Date | Author | Changes |
|
||||
|---------|------|--------|---------|
|
||||
| 1.0 | 2024-01-15 | Quality Manager | Initial release |
|
||||
|
||||
---
|
||||
|
||||
*This is an example SOP for training purposes. Customize for your organization's needs.*
|
||||
Reference in New Lab Ticket
Block a user