Documentation office · United States
Official policy documentation for United States organizations
Kaspelon publishes policy manuals, procedure documents, and style guidance for organizations that need their rules to be read, not just filed. Start where your problem is.
Bench, 3pm — document work in progress
What this office publishes
Three kinds of material, each with a different job. Keeping them apart is the first thing that stops a manual from turning into a wall.
Read the documentation standardsWhat an organization requires, and why
A manual states rules, definitions, named roles, exceptions, and who owns the next review. It is the document someone cites when two teams disagree about what was agreed.
How a task is actually carried out
Step by step, by a named role, in the order the work happens. Procedural detail belongs here rather than inside the policy clause it supports.
How the set stays coherent as it grows
Formatting, naming, and review conventions applied across the whole library, so the tenth manual matches the first one.
We do not publish legal advice, compliance certifications, or jurisdiction-specific opinions. A manual reviewed here is a readable document, not a legal instrument. Your counsel still has a job.
Failure, diagnosed
Why policy documents fail
A policy fails in one of two directions. It is either so vague that two managers read the same paragraph differently, or so long that nobody finishes it. Most failing manuals are the second kind.
Pages of nested clauses, no white space, headings that all look identical, and a numbering scheme that resets in every section. The fix is usually structural before it is editorial.
-
Break long clauses into numbered items
Conditions, exceptions, and the actor each take their own line.
-
Give every section a scannable heading
A reader hunting one clause should see it before reading anything.
-
Move procedure out of the policy
Steps belong in their own document, linked from the rule they serve.
-
Keep one numbering scheme
A clause reference that only works inside one section helps nobody.
This office treats those choices as core policy work, not as decoration. Structure is what a reader feels first, and it is what decides whether the manual is used or shelved.
A hairline rule on blank paper. Most of the work is deciding where it lands.
Finding a document in a policy library
A library works when browsing and searching lead to the same page. Someone typing "expense reimbursement procedure" and someone browsing Finance then Procedures should land on the same file.
Open the information architecture pageNaming, numbering, and cross-reference practice are covered in full on the information architecture page, including how to handle a document that spans two topics at once.
Clear-space unit
Spacing is not decoration. The gap above a heading and below a clause is what tells the reader a new rule has started.
32 px above · 24 px below · 8 px baseline
Writing standards in one paragraph
Plain language, short sentences, active voice where the actor is known. One idea per clause. Numbered items when a rule has conditions. Consistent terminology, so a vendor is never a supplier three pages later. If a sentence survives removal without losing meaning, remove it.
Tables for conditions
If approval authority differs by amount or role, a table beats a paragraph of "and/or".
Headings before body
Write the heading first. If you cannot, you are not sure what the section says yet.
The full set of rules, including the typographic conventions this site applies and the formatting choices behind them, lives on the documentation standards page.
Read the documentation standardsThe review cycle
Review, versioning, and change notes
A published policy is a live document. We describe a review cycle built around a scheduled interval plus a trigger: documents are re-read on a calendar, and also whenever the process they describe actually changes.
Every revision carries a version note saying what changed, when, and why. Readers who spot a stale clause can report it through the contact page, and that report enters the same review queue as an internal revision request.
A review cycle without a queue is a wish. What matters is that every request lands somewhere a person will actually open it.
Superseded guidance
Replaced documents are not deleted. They are marked, dated, and kept where a reader who followed the old version can still find out what changed.
Archive
Retention schedules, prior format
Kept for organizations whose records still reference the old numbering.
Expense approval thresholds, withdrawn
Replaced by role-based approval language. The withdrawn version stays visible for comparison.
Numbering convention, first edition
Documents published under it remain valid until their next scheduled review.
The audience
About the audience we write for
The organizations using this material are mostly United States workplaces with somewhere between a dozen and a few hundred staff: nonprofits, professional services firms, clinics, small manufacturers, school districts.
Many have no dedicated technical writer. The person maintaining the manual is often an operations lead or an HR generalist doing this alongside other work. Copy on this site assumes limited time and no style-guide background — which changes what "good" has to mean.
The minimalist presentation question
Documentation design keeps drifting toward less. The textlog Jekyll theme sits at the stripped-down end of that spectrum: essentially typography and white space with almost nothing else. Raycast's manual shows the other edge — a product hub that still reads as considered while staying sparse.
Both prove the same point from opposite ends. Authority comes from structure and consistent restraint, not from decoration. That is the argument this site is built on.
Making compliance content approachable
Compliance material has a reputation for being unreadable, and often earns it. A quality-management framework such as Qualtivate sits exactly where policy, compliance, and operations content meet, and it presents that material cleanly. You can borrow the approach without buying anything.
State the requirement, name the owner, give the evidence expected, stop. No motivational paragraph, no legal throat-clearing in the middle, and no paragraph that exists only to sound serious.
What users expect from support documentation
Some documents answer "what are the rules" and some answer "the thing broke, what now." Help centers organized by common task and issue exist because people arrive mid-problem. A policy manual serves a different reader: someone planning or complying, not someone blocked.
Keeping those two genres separate in one library makes both easier to use. Merging them is usually how a rule gets buried under a troubleshooting thread.
For the person holding the pen
Policy-writing guidance for whoever actually writes it
The guidance we publish is short on theory. It covers scannability (front-load the condition in each clause), white space (space between sections does real work), and the habit of writing the heading before the body.
Queen Mary University of London's policy writing guidance, a formal example this office studies, recommends clear, simple, succinct language, Source Sans Pro at a minimum of 12 point, 1.5 line spacing, and left alignment. That combination is unglamorous and it works.
Our policy writing guidance page expands on how to apply it inside a United States workplace where the manual is edited by several people who do not share a style background — the situation most small teams are actually in.
Start with policy writing guidance
Ruling a line is the smallest unit of policy work, and the one most often skipped.
The test
How to judge whether your manual is any good
Hand it to someone in a different department and ask them to find two answers: who approves a thing, and what happens if it is not approved.
They find both in under a minute
The structure is working. Leave it alone and fix the next section.
They ask what a word means
The terminology is failing. Define it once, then use the same word everywhere.
They claim it says something it does not
The clause needs rewriting. Ambiguity is the reader's problem only until it becomes yours.
That is the whole test, and it catches more problems than any checklist. It also takes about ten minutes, which is why it survives contact with a real work week.
Where to begin
Three routes depending on your situation. There is no wrong entry point; there is just a slower one.
The writing guidance shows how to rebuild a single section before you touch the rest of the manual.
Naming, numbering, and cross-references are covered end to end, with worked examples of folders that stopped making sense.
Formatting and review conventions that keep the tenth manual looking like the first one.
Questions readers ask first
Short answers to the four questions that come up before anyone opens a manual — including the one about legal advice.
Is this site a source of legal advice?
No. Kaspelon publishes documentation guidance and policy formatting standards. Legal sufficiency is a separate question and belongs with your own counsel.
Do you review my organization's manuals?
The office publishes standards and guidance that anyone can apply. Corrections and document requests sent through the contact page are logged and routed to the review queue.
What is the difference between policy documentation and help-center documentation?
Policy documentation states requirements and obligations for a governed audience. Help-center documentation answers task and troubleshooting questions for users of a product or service. The two often live side by side and should not be merged into one format.
Which sections belong in a policy manual versus an internal handbook?
Manuals carry rules, definitions, roles, exceptions, and review ownership. Handbooks carry orientation material, benefits summaries, and expectations that are not enforced as formal policy. If a section would be cited in a dispute, it belongs in the manual.
The documentation office
Kaspelon publishes the standards, you keep the rules
The office exists to make policy documentation readable by the people who have to follow it. If you have found a clause that is out of date, or you need a document type we do not currently publish, send a note and it enters the same review queue as everything else.
- Office
- 1600 Pennsylvania Avenue NW, Washington, DC 20500
- Hours
- Monday to Friday, 9:00 AM – 6:00 PM Eastern Time
- [email protected]
- Telephone
- +1 202-404-8117