Document templates

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

Controlled document management starts at the template, not at the library. If every SOP, every policy, every procedure begins from a blank Word file, you have no baseline — each author invents a slightly different structure, each version drifts, each audit turns into forensics. intranet.ai Document Management inverts that: every new document starts from a template your organization has approved once, and the template carries the metadata, the cover page, the brand styling, and the structure every downstream version will inherit.

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

✓

Illustration placeholder

At a glance

What you get

Four behaviors make templates the foundation of a defensible document library rather than a cosmetic shortcut. They're what turn "pick a Word file" into "instantiate a controlled document."

Controlled Word templates

Each document type (SOP, policy, work instruction) has its own approved template, centrally maintained.

Metadata auto-populated

Protocol code, version, effective date, and owner fill themselves from the template's field codes.

Brand and layout enforced

Cover page, headers, footers, and typography are locked at the template level — no drift.

Versioned like documents

Templates themselves are approved and versioned — so the master evolves under control, too.

How it works

From template to approved document

Templates are configured during implementation and managed centrally afterward. Authors never have to choose the right one manually — the library offers the template that fits the document type they're creating, and everything flows from there.

Implementation sets up templates

During onboarding, each document type gets its controlled Word template with metadata fields and brand styling.

Author picks document type

From the SharePoint library, the author creates a new document — the correct template is applied automatically.

Metadata fills itself in

Protocol code, version, owner, and effective date populate from the template's field codes.

Content gets authored, approved, published

The document moves through co-authoring, sequential approval, and PDF publication with the template's structure intact.

Before / after

What changes when this is on

The most common document-control failures trace back to the creation step: wrong cover page, missing metadata, formatting that drifts across versions, protocol codes entered by hand. Templates prevent each of them by design.

Without it

With intranet.ai

✗ Every SOP looks slightly different — different cover page, different font, different metadata layout

✓ Every SOP looks identical in structure because they all start from one controlled template

✗ Authors re-type protocol codes, owner names, or version numbers manually (and make mistakes)

✓ Metadata auto-populates from the template — zero opportunity for typos or omissions

✗ Brand guidelines are a PDF nobody consults; logos and headers drift across documents

✓ The template is the brand guideline — typography and layout are enforced, not suggested

✗ A new regulation changes what every SOP must contain; updating 400 documents becomes a project

✓ You update the template once, new documents inherit; existing ones surface in the expiration queue

Availability

Plan availability

Template-driven creation is a core lifecycle capability and is included on every DMS plan. The number of templates and the depth of customization expand as you move up the tiers, but the underlying capability is the same on Business as on Diamond.

business

enterprise

premium

diamond

✓ Included

All plans include template-driven creation. Enterprise and above add unlimited document types and bulk-template rollout tooling; Premium and Diamond include template design as part of onboarding.

Keep exploring

Related features

Templates are the first piece of a creation workflow that also applies protocol codes, binds metadata, and enables real-time co-authoring. These three pages cover the rest of the creation stage.

Stage 1 · Create

Protocol numbering

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

Stage 1 · Create

Custom metadata

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

Stage 1 · Create

Real-time co-authoring

Multiple editors in Word Online at the same time — with every edit, comment, and @mention captured for audit.

Deep dive

Read the full narrative

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

Every document starts from a governed Word template — version, protocol, and metadata pre-populated.

Template discipline isn’t glamorous, but it’s the single cheapest way to prevent downstream document errors. When every document in the organization starts from a governed template, the version number is correct, the protocol code is unique, the metadata is consistent, and the entire downstream governance layer — approval, publication, audit, expiration — has clean data to work with.

Templates per document type, administered centrally

Each document type — SOP, work instruction, policy, contract, training record, change control — can be bound to a Word template. Templates are administered in one place, not scattered across colleagues’ laptops. When a user creates a new document of a given type, the system clones the current template. There is no “find the right template” step, no “is this the latest template?” question.

System-written fields inside the document body

When a new document is created, the system writes the following directly into the document body — not just into the library metadata where nobody looks:

Version number. Starts at 0.1 as a draft minor version. Promoted to 1.0 when the document is approved and published.
Protocol code. A unique identifier composed from configurable parts (area code, document-type code, SharePoint’s unique internal ID). Customizable via supported syntax.
Configured metadata. Any fields the organization wants written into the document — effective date, author, department, review cadence, related-document references.

Fields can be set as editable (the author can change the value during drafting) or read-only (the system owns it — version and protocol code, for example — and the author can’t overwrite it).

Multiple templates per library are supported

A department with several SOP formats can have several SOP templates. The base product ships with one template per library configured at setup; additional templates are added as part of the implementation project.

Why this matters

The single most common cause of document errors is a human being updating the content of a document but forgetting to bump the version number. With the system writing those fields directly, the error becomes impossible. The downstream consequence — “which version of this SOP was in effect on [date]?” — becomes trivially answerable, because the metadata was correct from creation.

What this enables, downstream

Because every document starts with a protocol code, a known version, and correct metadata, the approval, publication, and governance stages have clean data to work with. The audit log has a unique ID to tie actions to. The approval flow knows who the document owner is. The expiration reminder knows when to trigger. The compliance team can filter the library by department, by document type, by effective date, or by review cadence and get an accurate picture on the first try.

Protocol numbering — how the unique document code is generated.
Custom metadata — read-only vs. editable field configuration.
Real-time co-authoring — multiple colleagues on the same document.

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 document templates fits into your current document-governance practice.

Book a free assessment or see all features