Version Control¶

Definition¶

Version control is a systematic process for managing changes to documents, ensuring that the current version is clearly identified and previous versions are archived and retrievable.

Overview¶

Version control ensures that everyone uses the correct version of a document. It prevents confusion when documents are updated and maintains an auditable history of all changes.

Technical Explanation¶

Key Elements of Version Control: - Unique version identifier (number or date) - Document status (draft, current, superseded, obsolete) - Change history log - Archive of previous versions - Access control (who can modify) - Review and approval workflow

Best Practices: - Version numbers increase monotonically (1.0 → 1.1 → 2.0) - Every change is documented in the revision history - Obsolete versions are clearly marked and archived - Document filenames include version numbers

Importance in Peptide Documentation¶

Version-controlled documentation is essential for quality systems compliance. Using outdated documents (old COA format, superseded TDS) can lead to specification misunderstandings or safety issues.

Frequently Asked Questions¶

Q: How many versions of a COA might exist? A: Typically one version per batch. If a COA is reissued (correction), the new version should be clearly marked and the reason for reissue noted.

Q: What happens to old versions of documents? A: They are archived and retained per the document retention policy (typically 3–5 years for quality documents).