Protocol numbering

Unique, permanent IDs on every document — the identifier that makes your library audit-ready.

Every governed document needs a permanent identifier that doesn't change when the title is revised, the owner moves on, or the version increments. That identifier is the protocol number — and it's the reference every auditor, every investigator, every cross-reference between documents will use. docs365.ai assigns one automatically at creation, using a syntax you control (prefix, sequence, year, department), and the number stays with the document for the rest of its lifecycle.

Stage 1 · Create Business: Included Enterprise: Included Premium: Included Diamond: Included

✓

Illustration placeholder

At a glance

What you get

Four qualities make protocol numbering a genuine document-control capability rather than a glorified counter: it's automatic, unique, structured, and permanent. Each one prevents a specific failure mode.

Automatic on creation

The number is assigned the moment a document is instantiated — authors never pick it.

Customizable syntax

Prefixes, sequences, year segments, department codes — configured per document type.

Findable and referenceable

Every search and cross-reference in the product resolves by protocol code.

Permanent through the lifecycle

The number persists across versions, revisions, and archival — the immutable handle for audit.

How it works

From creation to permanent identifier

Protocol-code syntax is configured per document type during implementation. After that the product manages the sequence — authors never pick a number, and collisions are impossible because the sequence is managed centrally, not by individual users.

Implementation defines the syntax

Each document type gets its protocol pattern — e.g. SOP-QC-2026-0001 — configured during onboarding.

Document is created from template

The author instantiates a new document; the next number in the sequence is allocated automatically.

Number is bound to the document

The protocol code populates the cover page, the metadata fields, and every downstream reference.

Code survives all changes

Revisions, version bumps, re-approvals, archive — the protocol number stays the same forever.

Before / after

What changes when this is on

Manual document IDs — "SOP-QC-v3-final-2.docx" — are the single most common source of document-control chaos. Every failure mode below comes from organizations that tried to impose a naming convention without system enforcement. Protocol numbering removes the possibility.

Without it

With intranet.ai

✗ Authors invent their own naming conventions; no two documents follow the same scheme

✓ Every document of a given type follows the same structured pattern — no exceptions

✗ Two authors accidentally assign the same ID to different documents; audit trail breaks

✓ The sequence is managed centrally; collisions are mathematically impossible

✗ "Which SOP was that again?" becomes a search problem across filenames

✓ Everyone refers to the same code — ISO 9001 clause 8.5 compliance becomes concrete

✗ A document is renamed and the audit trail loses track of its history

✓ The protocol code is the permanent handle; the title can change, the code doesn't

Availability

Plan availability

Protocol numbering is a core lifecycle feature included on every plan. Customization of the numbering syntax (prefix rules, sequence reset on year change, department-specific patterns) is available end-to-end; higher-tier plans simply package more of that configuration into the base onboarding.

business

enterprise

premium

diamond

✓ Included

Protocol numbering is a core feature on all DMS plans. Custom numbering syntax is available on every tier; the depth of configuration scales with the implementation-hour budget included in each plan.

Keep exploring

Related features

Protocol numbers are one of several identifiers and metadata fields that make a document findable and governable. These three features complete the "document identity" layer.

Stage 1 · Create

Document templates

Every document starts from a controlled, approved template — consistency baked in from the first keystroke.

Stage 1 · Create

Custom metadata

Every document carries the attributes your organization cares about — searchable, filterable, governable.

Stage 4 · Govern

Audit log

Every action, every approval, every version — captured against a named user, accessible in 30 seconds.

Deep dive

Read the full narrative

For the buyer who wants the full detail — compliance context, edge cases, adjacent workflows.

Customizable syntax, auto-generated at creation, written inside the document body.

ISO 9001, FDA 21 CFR Part 11, and most regulated-industry frameworks share the same expectation: every document must have a unique identifier that allows unambiguous reference. A SOP can be renamed; its file path can change; its title can be edited. What cannot change is its protocol code. That’s the anchor auditors reference when they ask for the history of a specific document.

docs365.ai assigns a protocol code to every document at the moment of creation, automatically.

How the protocol code is composed

The protocol code is built from configurable parts. A typical composition:

Area or department code (e.g., QA, IT, HR)
Document-type code (e.g., SOP, POL, WI)
Unique identifier — SharePoint’s internal unique ID for the document

The result might look like QA-SOP-0042 for the 42nd Quality SOP, or IT-POL-0017 for the 17th IT policy. Customers pick the composition pattern that fits their existing numbering scheme — or define a new one at implementation time.

Written into the document body, not just the metadata

The protocol code appears both as a filterable metadata column on the library and written directly into the document body (typically in the header or on the first page). Why both? Because the metadata column drives filtering, reporting, and navigation — while the in-document placement means the code travels with the document as a PDF, as an email attachment, or printed out for a shop-floor posting.

Customizable via supported syntax

The protocol code format is customizable at configuration time. Customers with established numbering conventions — inherited from a legacy ISO-certified QMS, a regulatory submission process, or a specific site naming scheme — can define composition patterns that match. The syntax covers the standard patterns customers typically need.

Unique and persistent

Once assigned, the protocol code is fixed to that document for its lifetime. A new revision (minor or major) keeps the same protocol code; only the version number changes. When the document is archived, the protocol code stays with the archived version — retrievable if an auditor asks for the exact version in effect on a specific date.

Why this matters

Three practical reasons:

Audit evidence. When a surveyor asks “what was the state of SOP-QA-0042 on 14 March?”, the protocol code gives you an unambiguous handle on which document to reference.
Cross-system references. Training records, deviation reports, change-control documents often reference an SOP by its protocol code. Because the code is stable, those references don’t break when the document is renamed.
ISO 9001 clause 8.5 compliance. Unique identification is explicitly required. Not delivering it is a finding.

Template-driven creation — the protocol code is written at creation, from the template.
Custom metadata — the protocol code is one system-owned metadata field among several.
Audit log — every action on the document is tied to its protocol code.

Lifecycle stage: Create →

Deep dive · Pillar guide

The active document lifecycle on SharePoint Online

Why passive document management fails — and what an explicit four-stage lifecycle looks like in practice inside a Microsoft 365 tenant.

22 min read · 5,200 words

Read the full guide

See this feature running on your documents

Thirty minutes. No cost. No obligation. We'll walk through how protocol numbering fits into your current document-governance practice.

Book a free assessment or see all features