> For the complete documentation index, see [llms.txt](https://docs.rplpeptides.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rplpeptides.com/docs/glossary/documentation-terms/version-control.md).

# 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.

## Related Terms

* [Revision](/docs/glossary/documentation-terms/revision.md)
* [Document ID](/docs/glossary/documentation-terms/document-id.md)
* [Document Traceability](/docs/glossary/documentation-terms/document-traceability.md)

## 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).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rplpeptides.com/docs/glossary/documentation-terms/version-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.