Policy Register

Compliance policy

How the organisation identifies its obligations, assigns them, checks them and reports breaches of them, across every regime it answers to.

How the register reads it

Also calledcompliance framework, compliance manual
FamilyGovernance and the management system
Document typePolicy. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted.
Folds intoThe regimes accept it folded into the information security policy; when neither is listed, the gap is counted once, under the parent.
Expected ownerLegal or the compliance officer.
Review cadenceAnnual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period).
On the gap list whennever on its own: the register recognises it and names the clauses, but no ticked regime lists it as a separate document (its parent, information security policy, is).
TemplateCompliance risk management policy.

Which standards require it, and what each expects it to contain

0 requiring clauses, 0 regimes

Shown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.

None of the eight regimes quoted here requires this document by clause. Named references, not quoted: ISO 37001, anti-bribery management systems (named; not quoted here); ISO 37301, compliance management systems (named; not quoted here).

Also governs

ISO 27001 controls this document is expected to set the rules for, beside the ones that require it: ISO 27001 5.31, ISO 27001 5.36.

Customizable template

8 sections, 0 cited to requiring clauses

With every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.

  1. Purpose
  2. Scope
  3. Roles and responsibilities
  4. Legal, statutory, regulatory and contractual requirements ISO 27001 A.5.31
  5. Compliance with policies, rules and standards for information security ISO 27001 A.5.36
  6. Exceptions
  7. Related documents
  8. Review and approval

Customise this template The template document on the compliance platform

Do this for every document on your list

Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.

Build a register

Document control procedure