Policy writing guidance

Write the rule so it can be found.

A policy has one job: get the reader to the right answer without a second read. These are the habits that make a manual scannable, the wording that makes an obligation unambiguous, and the mistakes that quietly cost people time in every revision.

Fix a clause now Documentation standards

Open binder and steel rule on a workbench under flat daylight, the working surface for drafting a policy clause

A clause is drafted, ruled, and re-ruled. Everything below is that work.

Drafting guidance

Write for the reader who is in a hurry

Assume the reader is looking for one clause and will skim everything else. That changes how you open a section. Lead with the condition, then the requirement. "If a purchase exceeds the approval threshold, the department head approves it before the order is placed." The reader who only needs the threshold finds it in the first six words. The reader who needs the whole rule keeps reading. Both get what they came for.

This ordering is not a stylistic preference. It is the difference between a manual people consult and a manual people avoid. When the condition leads, the reader can decide in one glance whether the rest of the clause applies to them at all, and a policy manual reads faster for everyone who opens it.

Buries the answer

"Reimbursement requests for travel costs incurred during approved trips should be reviewed by the appropriate department prior to payment."

Leads the answer

"For travel on an approved trip, the department reviews the reimbursement before payment."

Clear, simple, succinct: what that means in practice

Three demands that hold up in any organization's manual, whether the document runs two pages or two hundred. They are not slogans; each one has a measurable effect on how fast a reader can act.

Short sentences

One obligation per clause, and the actor named. "The finance team reviews reports monthly" beats "Reports are reviewed on a monthly basis," because the first version tells the reader who does it and the second only tells them it happens.

Passive voice as a signal

Passive voice is not banned; it is a warning light. When a clause hides its actor, the step usually has no agreed owner yet. Rewrite it with a named role, or leave a note for the team that the owner is still unresolved.

One idea per clause

A clause that carries two conditions and an exception will be misread at least once. Split it. A longer table of contents is a small price for a manual where each clause does one thing and can be cited on its own.

Scannability: headings, key terms, and structure

A scannable document lets a reader find a section from the table of contents in one glance, and a clause within a section without reading the whole section. Four habits carry most of that work.

Clause

Habit

Why it works

Front-load

Front-load the noun

Put the searchable noun first in the heading.

Use "Travel Expense Limits," not "Reimbursement of Costs Incurred During Approved Travel." The reader searches for the noun, not your phrasing.

Repeat

Repeat key terms exactly

Same words, every time, everywhere in the manual.

If the policy says "approval threshold," do not call it a "spending cap" two sections later. Consistency is a scannability tool, not a stylistic preference.

Mirror

Mirror the heading in the text

The clause should use the words its heading uses.

A heading that promises "Approval Thresholds" and a body that only mentions "limits" forces the reader to translate. Repeat the heading's nouns in the first sentence.

Number

Number conditions, not prose

Give each condition its own line.

Three conditions buried in one sentence get read as two. A numbered list of conditions keeps each one visible and separately citable when a policy is reviewed.

White space as a writing decision

Writers tend to treat white space as the designer's problem. It is not. Every wall of text you leave unbroken is a decision to make the reader work harder, and the fix usually belongs to the writer, not the layout.

Break a paragraph when the subject changes, even when the change is small. Give conditions their own numbered line instead of burying them mid-sentence. The practical result is a page that reads as orderly rather than dense.

One clear-space unit, in eighths

Before

Employees requesting time off exceeding five consecutive business days must submit the request to their direct supervisor no fewer than fourteen calendar days before the first day of the requested absence, unless the absence is covered by an approved leave arrangement, in which case the leave arrangement's own notice period applies.

After

For time off longer than five business days, submit the request to your supervisor at least 14 days before the first day off. If approved leave already covers the absence, that leave's notice period applies instead.

Two lines instead of four. The condition leads, the actor is named, and the exception has its own sentence so a reader can stop before it if it does not apply.

Draft problems

Common beginner mistakes

Three problems show up constantly in first drafts. Each one is fixable in an afternoon, and each one costs readers time until it is fixed.

Mixing policy and procedure in one document

The rule gets buried under steps that belong in their own procedure file. Split them: the policy states what must be true, the procedure states how the work is done, and each can be revised without dragging the other along.

Defining a term once, then renaming it

The term is defined in section 1 and then called something else from section 4 onward. A reader who searches the defined term finds nothing after the fourth page. Pick one phrase and hold it for the life of the document.

Exceptions before the rule they modify

The reader learns the edge case before the standard, then has to hold both in mind while working out which one applies. State the rule, then state the exception, then point back to the rule.

Review pass

How drafts are checked

How experienced reviewers evaluate a draft

An experienced reviewer reads the manual's table of contents first, then picks one obligation at random and traces it to its owner, its evidence, and its exception. If any of those links is missing, the draft goes back.

The same pass checks that no clause depends on knowledge from a document the reader has not been told about. This pattern is faster than reading cover to cover and it catches the same problems, which is why it works for every revision rather than only the first.

See how drafts are reviewed

Owner

Every obligation names a role, not a department. A role can be reached; a department can be everyone and therefore no one.

Evidence

Each clause points to what proves the step happened: a record, a signed form, a log entry. If nothing proves it, the step cannot be reviewed.

Exception

Every rule that has an exception names it nearby, so the reader does not learn the edge case from the person who approves the work.

References

Clauses that lean on another document name it, so a reader never has to guess which manual answers the rest of the question.

A worked rewrite

Original

In the event that an employee wishes to request time off for a period exceeding five consecutive business days, such request should be submitted to their direct supervisor no less than fourteen calendar days prior to the first day of the requested absence.

Rewritten

For time off longer than five business days, submit the request to your supervisor at least 14 days before the first day off.

Same rule, two lines instead of four, and the actor is named. This is the level of editing a policy manual benefits from, and it is the level a reviewer can check in a single pass.

Stack of blank stapled procedure pages squared on a steel bench beside a fine liner pen

Rewriting is not rewriting the rule. It is removing everything standing between the reader and the rule.

Browse the policy library

Writing questions we hear most

Short answers to the drafting decisions that come up in almost every revision cycle.

Send a writing question

How long should a single clause be? +

Long enough to carry one obligation and short enough to read in one pass. If a clause needs two conditions and an exception, it is usually two clauses. Length is a symptom; the real question is whether the reader can act on it without asking someone.

Should we define terms in a glossary or in place? +

Do both, and keep them identical. Define the term the first time it appears, then repeat that exact definition in the glossary. A glossary that disagrees with the body text is worse than no glossary, because the reader cannot tell which version the reviewer used.

Can we use tables for approval thresholds? +

Yes, when the reader needs to compare values across a set of cases. A table beats a paragraph for thresholds, tiers, and limits. Keep the column headers in the same words the prose uses, and put the unit in the header rather than repeating it in every cell.

How often should a manual be rewritten? +

Rewriting whole manuals on a schedule rarely improves them. Review clauses when the process they describe changes, and run a shorter consistency pass across the manual afterward so new wording does not drift from the terms already in use.

Where do procedure steps belong? +

In a procedure document that the policy points to. The policy states what must be true and who owns it; the procedure states the order of the steps. Keeping them apart lets a team change a step without reopening the rule it serves.

How do we name the person responsible? +

Name the role, not the individual, and use the same role name the organization chart uses. "The department head approves it" survives a staff change; "Jane approves it" has to be edited the month someone leaves.

Keep going from here

Three routes are the usual next step, depending on whether you are fixing wording, structuring a manual, or asking about a clause that has already been drafted.

Standards

About Kaspelon