Reviews
Part of What separates a policy from a standard, a procedure and a guideline?
Policy template format: numbering, header block, exception tables and change notes
Policy template format: clause numbering that stays citable, a header block that answers who a policy applies to, exception tables, page setup and a version and change block.
A policy is read twice in its life by most people: once when it is issued, and once when they are about to do something and want to know if they are allowed. The second reading is the one the layout has to serve, and it is a search, not a read.
What a policy should say is in the policy templates overview. This page is about numbering, page setup, and the mechanics that let someone find one clause in a hurry.
What to take away
- Number every clause. An unnumbered policy cannot be cited, and a policy nobody can cite gets restated badly by whoever is quoting it.
- Put scope and effective date above the first statement, not in a preamble at the end.
- One statement per numbered clause, so it can be quoted, changed, or complied with on its own.
The clause numbering scheme
Decimal numbering, two levels, and no more.
Clause Numbering Rules
Rule
- Number belongs forever
- Never reuse withdrawn numbers
- New statements at end
- Stable citation over logical order
- One numbering scheme
- Headings and clauses together
- Two levels only
- Deeper means a procedure crept in
What it means
- Number belongs forever
- New statements at end
- One numbering scheme
- Two levels only
A complete section of a travel policy, with real wording, looks like this:
3 Expenses incurred while traveling
3.1 Travel is booked through the company travel agency unless
the budget holder approves a written exception.
3.2 Costs are reimbursed against an itemized receipt.
3.3 Where a receipt is unavailable, the budget holder may approve
the claim on a written explanation of the cost.
The rules that make this work over a document's life:
- A number, once issued, belongs to that statement forever. If the statement is withdrawn, leave the number out rather than reusing it. Two people quoting clause 3.2 from different years should not be quoting different rules.
- New statements go at the end of their section as the next number, even when the logical place is in the middle. Logical order is worth less than stable citation.
- Never number the headings and the clauses in different schemes. One sequence, headings numbered, clauses numbered under them.
- Keep the depth at two levels. A 4.3.2.1 in a staff-facing policy is a sign that a procedure has crept in, which the SOP templates page treats as a separate document for good reason.
The header block
Everything a reader needs to know before the first statement, in a fixed block:
Header Block Fields
- Titlenoun phrase naming the subject
- Applies toroles, sites, exclusions
- Effective froma date
- Versionan integer
- Ownera role
- Review triggerevent plus backstop date
- Related documentsnamed with references
| Field | What goes in it | Why it is above the text |
|---|---|---|
| Title | A noun phrase naming the subject, not a code | People search for the subject |
| Applies to | The roles, sites, or entities covered, and any excluded | Half of all policy questions are "does this apply to me" |
| Effective from | A date, for example 1 March 2027 | A policy with no effective date is hard to enforce |
| Version | An integer, for example 3 | So a printed copy can be checked against the live one |
| Owner | A role, for example "Finance Manager" | Roles survive staff changes |
| Review trigger | An event, and a backstop date | Calendar-only reviews find nothing |
| Related documents | Named, with their own references | Stops the policy absorbing a procedure |
Nothing else belongs above the first statement. A mission paragraph at the top pushes the operative text below the fold and gets skipped by everyone twice.
Writing a statement so the layout can hold it
Format and wording are not separable here. A clause that runs to four lines cannot be laid out well because it is doing several jobs.
Statement Writing Rules
- One obligation per clause
- Put the actor first
- Conditions before the obligation
- Fixed must, may, does not apply
- No nested exceptions
The Plain Writing Act of 2010 requires US federal agencies to write clearly, and plainlanguage.gov publishes the guidance for it. A policy written to that standard is easier to lay out because each sentence is shorter than the column it sits in.
Tables that carry the exceptions
Where a policy has more than two conditions, a table beats prose and beats nested clauses. Three columns usually do it: the situation, what applies, and who decides.
Exception Table Structure
Situation
- Ordinary case
- Default clause
- Named exception
- Alternative clause
- Anything not listed
- Default or stop
What applies
- Ordinary case
- Automatic
- Named exception
- Role
- Anything not listed
- Role
Who decides
- Ordinary case
- Named exception
- Anything not listed
| Situation | What applies | Who decides |
|---|---|---|
| Economy airfare for a trip under four hours | Clause 3.1, booked through the company travel agency | Nobody, it is automatic |
| Business-class fare for a flight over eight hours | Clause 3.1 exception, with a written reason | Budget holder |
| Any case not listed here | Clause 3.3, or a stop until the budget holder rules | Budget holder, named by role |
The last row is the one that gets left out and the one people need. A policy without an "anything else" line makes every unlisted case a private judgment. The figures in the example are illustrative.
Page setup for printed and posted copies
Set the page to the paper size your staff use, US Letter or A4. A common starting point is margins of at least 2 cm (about three-quarters of an inch), body type of 11 point or larger, and a line length of roughly 60 to 75 characters. These are typographic defaults, not standards, so test one printed page before adopting them.
Printed Copy Checks
- Footer identity on every page
- No orphaned headings
- Legible without color
- Visible superseded marker
Two pages is a good target for a staff-facing policy, and four is a warning. When a policy runs long it has usually absorbed a procedure, a standard, or a set of definitions that belong in a referenced document.
For anything that will be printed or posted:
Footer identity on every page. Title, version, effective date, page x of y. Loose pages circulate.
No orphaned headings. A section heading at the foot of a page with its first clause overleaf is how a clause gets missed.
Legible without color. Use a word or a symbol alongside any color coding. Section 508 of the Rehabilitation Act and the WCAG 2.2 guidelines both require that color not be the only way information is conveyed.
A visible superseded marker. Old printed copies survive for years. Make the version obvious from across a room.
The version and change block
Put it at the end, not the front, and keep it short.
Change Note Quality
Weak note
- Content
- Updated
- Reader use
- No answer
- Placement
- Front
Strong note
- Content
- Which clause, how behavior differs
- Reader use
- Tells if a habit is wrong
- Placement
- End, kept short
Version Effective What changed
3 1 March 2027 Clause 3.1: business-class fares now need a written reason
2 1 March 2026 Clause 3.2: receipts must be itemized
1 1 March 2025 First issue
"Updated" is not a change note. A reader consults this block to find out whether a habit of theirs is now wrong, and only a statement of the difference answers that. The same discipline shows up in the policy templates checklist, which treats the change note as part of the approval rather than an afterthought.
A layout pass before it goes out
- Can a reader tell in ten seconds whether the policy applies to them?
- Is every statement numbered and separately quotable?
- Does any clause contain two obligations?
- Is there a row or a clause for the case nobody listed?
- Does the footer identify the document on every page?
- Is the effective date above the first statement and in the footer?
Where the document then has to live, and how staff will actually find it, is a separate problem covered in the notes on choosing policy software.
