Kaspelon Documentation Office
About the Kaspelon Documentation Office
The Kaspelon Documentation Office publishes policy manuals, procedure documents, and documentation standards for organizations in the United States.
What we do
We produce and maintain the policy and documentation content on this site, and we apply the same standards to it that we recommend to our readers.
That means every published document here has a stated review interval, a version note, a named owner on our side, and a stable name. If a document is superseded, the replacement is linked. If it is withdrawn, that is visible too.
review interval
Every document states when it comes up for its next scheduled review, so a reader knows whether they are holding current guidance.
version note
Revisions are recorded as notes in place. You can see what changed without comparing two copies by hand.
named owner
Each document carries the role on our side responsible for keeping it accurate, so questions have somewhere to land.
The library is the product, and its hygiene is the work. We treat filing and naming as seriously as wording, because a manual that cannot be navigated has stopped doing its job even if every clause in it is well written.
Who this is for
Organizations of roughly a dozen to a few hundred people, most without a dedicated writer or an in-house style guide.
Many of our readers maintain the policy manual alongside another full-time job. The person keeping the document set current is often an operations lead or an HR generalist who inherited the folder and now has to make it defensible.
Every piece of guidance here is written for that person, not for a documentation department. That shapes the tone of what we publish: examples are drawn from ordinary workplaces, instructions assume no prior framework, and nothing is written for an audience that already knows the vocabulary.
We keep the reading level even across the library. A procedure document should not require a different set of skills than the policy it implements, and neither should a page of standards explaining how the two connect.
How we approach policy writing
We favor plain language, short clauses, and structural clarity over formal tone. A policy that sounds official and reads badly is failing at its only job.
Ruling a page by hand is how most of our drafting starts. The pen is a check on the sentence: if a clause needs a second reading, the line gets redrawn.
Our approach draws on published guidance in the field, including Queen Mary University of London's policy writing recommendations and UniversalClass's formatting advice, and on how modern documentation products present complex material without clutter. We adapt those patterns to the workplace manual, where the reader is complying rather than troubleshooting.
That adaptation matters more than it sounds. A help center reader arrives curious; a manual reader arrives with a task and a deadline, and often with a supervisor waiting. Instruction-first writing, headings that name the action, and short paragraphs all serve that reader better than any amount of polish.
our working habits
- Short clauses, one obligation each.
- Headings that name an action, not a topic.
- Rules and tables where a list would ramble.
- Readable at 16px on a phone screen.
Editorial principles
Four rules govern what we publish. They are listed in the order we apply them when a document is submitted for review.
one
No invented facts
Every example, figure, and citation in our writing traces back to something we can verify inside our own editorial process.
two
No legal advice
We describe how to write a policy, not what your policy must say. Questions about your own obligations belong with your counsel.
three
No decoration over substance
If a section does not help a reader act, it does not ship. This applies to our own site as much as to the manuals we write about.
four
Corrections are welcome
Reader corrections get logged like any internal revision request, with the same review path. That last rule is why the contact page exists.
What we don't publish
We don't publish legal opinions, jurisdiction-specific compliance certifications, or promises about outcomes. We also don't offer a custom manual-writing service, and we won't imply that applying our standards makes a document legally sufficient.
No legal opinions or interpretations of specific regulations.
No compliance certifications or jurisdiction-specific seals.
No promises about what a document will achieve once adopted.
No custom drafting service, and no ghostwriting of your manual.
We don't publish anything we cannot cite or verify within our own editorial process. If that makes us less exciting to work with, it also makes us reliable.
Why the site looks like this
A policy library is read under time pressure, often on a phone, often in a browser tab competing with eleven others. Persistent navigation, restrained typography, and generous white space serve that reader.
We are not against visual design. We are against anything that competes with the text for attention. Restraint here is a reading decision, and it is the same decision we ask of the manuals we write about.
conventions we apply
The documentation standards page spells out the type scale, heading names, table rules, and naming conventions behind everything we publish here.
Documentation standardshow a document reaches this site
The path is short and the same every time. It is also the path we suggest readers copy for their own manuals.
-
Draft against a named reader
Every piece starts with the person who has to act on it, not with the topic.
-
Cut anything that does not instruct
Preamble survives only if it changes how a clause is read.
-
Check the structure, not just the prose
Headings, tables, and clause numbering get the same scrutiny as sentences.
-
File it with its review date
Publication is the midpoint. The document is not finished until it is scheduled.
Contact and feedback
Questions, corrections, and document requests go through the contact page. We read every message and route it appropriately, though we cannot promise a same-day reply.
If you are reporting an error, include the document title and the section number, and we will log it into the same queue used for internal revisions. That is the whole feedback loop, and it works.
Send a question or correctionthe office
Kaspelon Policy & Documentation
1600 Pennsylvania Avenue NW
Washington, DC 20500
Monday to Friday, 9:00 AM – 6:00 PM Eastern Time