Compliance documentation engine

Policies that hold together — and prove it.

Clausery treats a policy as a structured set of numbered clauses, not a text blob. Numbering, definitions, and cross-references stay correct automatically as documents evolve — so the policy set stays continuously consistent, versioned, and regulator-ready.

Free workspace · No payment details · Import a Word or PDF policy in minutes

Built for regulated organisations — financial services, insurance, ISO 27001 environments.

Information Security PolicyIn effect · v2.1.0
1Purpose
1.1This Policy defines how Information Security is governed across the Group.
1.2It is approved by the Supervisory Board and reviewed every two years.
2Scope
2.1The Policy applies to all Staff and to the processing governed by the Risk Management Policy, 3.1.
References — Risk Management Policy, 3.1 (resolved live — renumbering never breaks it)
Framework coverageISO 27001DORAGDPRNIS2Financial servicesInsurance

Why not a word processor

A document is a structure, not a file.

Clauses with identity

Every clause has a stable identity; display numbers are derived from structure. Reorganise a document and everything renumbers — while references and definitions keep pointing at the right clause.

One vocabulary

Terms are defined once in a central glossary and detected across every document. Change a definition and each committed document that uses it is flagged and re-versioned for review.

Nothing changes silently

Committed documents only move by versions — semantic versioning, row-by-row diffs, and author attribution down to the clause. What an auditor asks for is what the system already keeps.

Competitive position

Not another GRC clone. The documentation engine underneath compliance.

Clausery is for regulated companies that need policies, procedures, approvals, terms, references, and audit exports to stay consistent as a living documentation set.

More precise than broad GRC

General compliance platforms are strong at integrations, controls, evidence, and trust centers. Clausery goes deeper where the actual policy language lives: clauses, approvals, references, definitions, and exact approved versions.

Stronger than a document repository

Word, SharePoint, Confluence, and Notion can store policies, but they do not know when a renumbered clause breaks a reference, when a definition changes meaning, or which approved wording an auditor must see.

Built for audit defensibility

Every approved version is frozen as it was approved. Diffs show who changed what, cross-links resolve to the right clause, and glossary changes propagate into review instead of drifting quietly.

Structure

Write in clauses. Numbering takes care of itself.

The editor works clause by clause: indent, reorder, and nest sections and the numbering re-derives instantly. Because links and definitions target the clause itself — never its number — reorganising a policy is safe.

3Roles and responsibilities
3.1The Management Board owns this Policy and approves exceptions.
3.2The Head of Information Security maintains the control set.
3.2.1Controls are reviewed after every material incident.moved — was 4.2
3.3Internal Audit verifies adherence on the annual plan.

Clause 4.2 was moved under section 3.2 — every reference to it now reads 3.2.1, automatically.

Control

Every change on the record.

Committed documents move only by versions. Compare any two versions clause by clause — what was added, changed, or removed, and by whom, with their role. Approval flows end at the board delegate when a document requires board sign-off, and review periods warn before anything quietly expires.

Draft→In review→Board approval→In effect
Compare versionsv2.0.0 → v2.1.0
2.3added· added by Jane Sokk (Head of Risk)

Access rights are recertified quarterly by the system owner.

2.4changed· changed by Admin User (Chief Information Officer)

Privileged access requires a second approval and expires after 90 days.

5.1removed· removed by Jane Sokk (Head of Risk)

Shared administrator accounts may be used where technically required.

Consistency

One glossary. Zero drift.

Define a term once and Clausery detects it in every document — confirm or dismiss each occurrence. When a definition changes, every committed document that uses the term is re-versioned and flagged for review. Cross-document references behave the same way: renumber the target and every citing document updates and gets flagged.

Staff

Glossary term

Every natural person who works for the Group under an employment or authorisation agreement, including board members.

alias: employeealias: personnel

Definition changed — integrity propagation

  • Information Security Policyv2.1.1 · in review
  • Remote Work Procedurev1.3.1 · in review
  • Acceptable Use Standardv3.0.1 · in review

And the rest of the lifecycle

From imported legacy files to audit-ready exports.

Clausery covers the path in: your existing PDF and Word policies become structured documents with nothing silently altered — and the path out: versioned, presentable files an auditor can hold.

Faithful import

Upload existing PDF or Word policies. Structure and numbering are detected, and every transformation is surfaced as a warning — imported content is never silently dropped or rewritten.

Audit-ready export

Export any version as PDF or Word with numbering, references, and the definitions panel intact — the artifact you hand to an auditor matches what the system enforces.

Coverage and gap analysis

Check the documentation bundle against framework requirement catalogs and see what is covered, partial, or missing — before the auditor does.

ISO 2700182%
DORA64%
NIS271%

Organizations and roles

Work across multiple organizations with one focused context at a time. Role-based access separates superadmins, org administrators, members — and board delegates for final sign-off.

It explains itself

Every page carries a guided walkthrough that runs the first time you open it and replays from the ? in the top bar. An empty workspace is explained with clearly-marked sample rows — never saved, gone when the tour ends.

Getting started

From nothing to a structured policy in one sitting.

No credit-card wall and no sales call to get started. Your first imported policy shows you exactly what you're buying — before you have spoken to anyone.

  1. 1

    Create a workspace

    Name, work email, password. No payment details, no sales call, no procurement paperwork. You are inside the product in under a minute.

  2. 2

    Import a policy and see it structured

    Upload one of your existing Word or PDF policies. Within minutes it's numbered clauses, detected definitions, a version history, and an ISO 27001 coverage report — that's the moment Clausery makes sense.

  3. 3

    Ask for the full trial

    One button from inside the workspace. A real person reviews it and opens up 14 days with ten documents and your whole framework — everything you already built carries over.

Put your policies in order.

Structured clauses, one vocabulary, a full audit trail — from the first imported policy to the version an auditor signs off.

Start free

Get in touch

Questions? Talk to a person.

Two clicks tell us most of what we need, and a real person replies within one business day. You don’t have to wait for us to try it, though — start free in under a minute and import a policy now.

  • · Free preview workspace — one document, no payment details, no call
  • · Import your existing PDF & Word policies on day one
  • · Framework coverage: ISO 27001/27701/42001, DORA, GDPR, NIS2, PCI DSS and financial-services requirements
A real person replies within one business day. No newsletters, no automated sequences. We handle your details as described in our Privacy Notice.