> 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/document-id.md).

# Document ID

## Definition

A Document ID is a unique alphanumeric code assigned to each document within a quality management system, enabling unambiguous identification and cross-referencing.

## Overview

Document IDs are the backbone of document management. Each document (TDS, COA, SDS, SOP, white paper) receives a unique ID that stays with it throughout its lifecycle, regardless of revision.

## Technical Explanation

**Document ID Structure (RPL Peptide Example):**

| Code Section | Meaning                          |
| ------------ | -------------------------------- |
| RPL          | Company prefix                   |
| TM           | Document type (Technical Manual) |
| WP           | White Paper                      |
| TDS          | Technical Data Sheet             |
| COA          | Certificate of Analysis          |
| SDS          | Safety Data Sheet                |
| -001         | Sequence number                  |

**Examples:**

* RPL-WP-PUR-001 = White Paper, Purity topic, version 001
* RPL-TM-BPC-001 = Technical Manual, BPC-157, version 001

**Properties:**

* Unique (no two documents share the same ID)
* Persistent (ID remains the same across revisions)
* Structured (encodes document type and topic)
* Searchable (enables cross-referencing)

## Importance in Peptide Documentation

Document IDs enable efficient cross-referencing within the documentation ecosystem. White papers can reference TDS documents by ID, COAs reference batch numbers, and quality system audits track document IDs.

## Related Terms

* [Revision](/docs/glossary/documentation-terms/revision.md)
* [Version Control](/docs/glossary/documentation-terms/version-control.md)
* [Document Traceability](/docs/glossary/documentation-terms/document-traceability.md)

## Frequently Asked Questions

**Q: Can I use a Document ID to find related documents?** A: Yes. The Document ID structure allows you to identify document type and topic. For example, documents with "BPC" in the ID are related to BPC-157.

**Q: Does the Document ID change when a document is revised?** A: No. The Document ID is permanent. Only the version/revision number changes. This ensures all references to the document remain valid.


---

# 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/document-id.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.