Quality Documentation Elite

A specialized skill for managing quality documentation systems — covering document control procedures, Standard Operating Procedures (SOPs), work instructions, quality records management, change control, and regulatory documentation compliance for medical device and regulated industries.

When to Use This Skill

Choose Quality Documentation Elite when you need to:

• Design or improve a document control system
• Write SOPs and work instructions for regulated processes
• Implement change control procedures for quality documents
• Set up quality records management with retention policies
• Prepare documentation for regulatory audits (ISO 13485, FDA QSR)

Consider alternatives when:

• You need general technical documentation (use a tech docs skill)
• You need code documentation (use a code docs skill)
• You need project documentation (use a PM skill)

Quick Start

Copy
# Create an SOP for document control
claude "Write a Standard Operating Procedure for document control in a medical device company, compliant with ISO 13485:2016 Clause 4.2.4 and FDA 21 CFR 820.40."

Copy
# SOP-QA-001: Document Control
**Revision**: 03
**Effective Date**: 2024-12-15
**Author**: Quality Assurance Manager
**Approved By**: Director of Quality

## 1. Purpose
Define the process for creating, reviewing, approving,
distributing, and controlling quality management system
documents to ensure only current, approved versions are
available at points of use.

## 2. Scope
All QMS documents including:
- Quality Manual, policies, and procedures
- Work instructions and forms
- Design and manufacturing records
- External documents (standards, regulations)

## 3. Definitions
| Term              | Definition                          |
|------------------|--------------------------------------|
| Controlled Copy  | Document distributed under the DCS   |
| Obsolete         | Superseded version, retained for reference |
| DCR              | Document Change Request              |
| DHF              | Design History File                  |

## 4. Responsibilities
| Role             | Responsibility                      |
|------------------|--------------------------------------|
| Document Author  | Draft and revise documents           |
| Department Head  | Review for technical accuracy        |
| Quality Assurance| Approve, assign number, distribute   |
| Document Control | Maintain master list, archive        |

## 5. Procedure

### 5.1 Document Creation
1. Author drafts document using approved template
2. Assign document number per numbering convention:
   [DEPT]-[TYPE]-[SEQ] (e.g., QA-SOP-001)
3. Submit to department head for technical review
4. Submit to QA for quality review and approval
5. QA assigns effective date and distributes

### 5.2 Document Change Control
1. Originator submits Document Change Request (DCR)
2. Impact assessment: identify affected documents
3. Department head reviews and approves change
4. QA reviews for regulatory impact
5. Updated document issued, obsolete version marked
6. Training impact assessed and assigned if needed

### 5.3 Document Distribution
- Controlled copies tracked on Distribution Log
- Electronic documents: access-controlled shared drive
- Paper copies: stamped "CONTROLLED" with copy number
- Obsolete versions: stamped "OBSOLETE", removed from use

Core Concepts

Document Hierarchy

Level	Document Type	Purpose	Example
1	Quality Manual	QMS overview and policy	QM-001
2	Procedures (SOP)	How to perform key processes	SOP-QA-001
3	Work Instructions	Detailed step-by-step tasks	WI-MFG-015
4	Forms & Records	Evidence of process execution	FM-QA-001, DHR
5	External Docs	Standards, regulations, refs	ISO 13485, FDA 820

Document Numbering Convention

Copy
## Numbering System: [DEPT]-[TYPE]-[SEQ]

### Department Codes
| Code | Department              |
|------|------------------------|
| QA   | Quality Assurance       |
| RA   | Regulatory Affairs      |
| RD   | Research & Development  |
| MFG  | Manufacturing           |
| SC   | Supply Chain            |
| HR   | Human Resources         |

### Document Types
| Code | Type                    |
|------|------------------------|
| SOP  | Standard Operating Procedure |
| WI   | Work Instruction        |
| FM   | Form (blank template)   |
| POL  | Policy                  |
| SPE  | Specification           |
| TMP  | Template                |

### Revision Tracking
- Initial release: Rev 01
- Sequential revisions: Rev 02, 03, etc.
- Draft stages: Rev 01-DRAFT (not for use)
- Each revision requires: DCR, review, approval

Records Management

Copy
## Quality Records Retention Schedule

| Record Type              | Retention Period          | Regulation        |
|-------------------------|---------------------------|-------------------|
| Design History File     | Lifetime of device + 2 yrs| 21 CFR 820.184   |
| Device Master Record    | Active + 2 years          | 21 CFR 820.181    |
| Device History Record   | Lifetime of device + 2 yrs| 21 CFR 820.184   |
| Complaint Files         | Lifetime of device + 2 yrs| 21 CFR 820.198   |
| CAPA Records            | Lifetime of device + 2 yrs| 21 CFR 820.198   |
| Training Records        | Duration of employment + 3 yrs | ISO 13485 6.2 |
| Audit Reports           | 5 years minimum           | ISO 13485 8.2.4   |
| Management Review       | 5 years minimum           | ISO 13485 5.6     |
| Supplier Evaluations    | Active relationship + 5 yrs| ISO 13485 7.4    |

## Record Storage Requirements
- Protected from damage, deterioration, loss
- Readable for entire retention period
- Controlled access (need-to-know basis)
- Backup copies for electronic records
- Migration plan for obsolete media formats

Configuration

Parameter	Description	Example
regulation	Applicable regulatory framework	"ISO 13485" / "FDA 820"
document_type	Type of quality document	"sop" / "work_instruction"
department	Owning department	"quality" / "manufacturing"
revision	Document revision number	"03"
include_training	Include training impact assessment	true
output_format	Document format	"markdown" / "docx"

Best Practices

1. Keep SOPs at the right altitude — SOPs should describe the process flow, responsibilities, and decision points. Detailed step-by-step technical instructions belong in Work Instructions referenced by the SOP. SOPs that are 40 pages long get neither read nor followed.

2. Use templates consistently across all document types — Every SOP should have the same header structure, section numbering, and approval block. Consistency reduces training time and makes documents navigable by anyone in the organization, not just the author's department.

3. Make the document numbering system self-explanatory — Anyone should be able to look at MFG-WI-023 Rev 04 and know it's a Manufacturing Work Instruction, number 23, revision 4 without consulting a legend. This speeds up document retrieval and reduces filing errors.

4. Track training impact for every document change — When a procedure changes, determine who needs retraining and document the completion. Auditors specifically check whether personnel working under a procedure were trained on the current revision.

5. Implement periodic review cycles and enforce them — Set review dates at document creation (annually is standard for SOPs) and use automated reminders. Documents that haven't been reviewed become unreliable — they may reference superseded standards, former employees, or discontinued processes.

Common Issues

Obsolete documents remain in use at workstations — Paper-based systems are particularly vulnerable. Operators print a work instruction and keep the copy at their station for months after it's been revised. Implement controlled copy stamping with expiration dates, or move to electronic-only access at points of use.

Change control is bypassed for "minor" changes — Teams make "editorial" changes without submitting DCRs, but editorial changes can alter meaning. Any change to a controlled document — even correcting a typographical error — should go through the change control process. The process can be streamlined for minor changes, but never skipped.

Electronic document systems don't meet 21 CFR Part 11 — Electronic records and signatures in FDA-regulated environments must comply with Part 11 requirements: audit trails, electronic signatures with unique identifiers, system validation, and access controls. Using a shared drive without these controls doesn't satisfy regulatory requirements.