Review and Maintenance
How policy documents are reviewed and kept current
A policy document is only as good as its last revision. This page describes how documents in the Kaspelon library are reviewed, versioned, and retired, and how a reader can flag something that no longer matches reality.
A review cycle that does not need rescuing
The review cycle is deliberately undramatic. A process that only works when someone remembers to chase it stops working the month attention moves elsewhere. So the rules are written down, the owner is named, and the calendar does most of the remembering.
Two things move a document back into the queue: the scheduled interval elapsing, or an event that changes the facts underneath it. Everything else on this page describes how those two triggers are logged, versioned, and closed out.
The review interval
Every document has an owner and a date it comes due
Every document in the library carries a stated review interval, typically twelve months, and a named review owner. When the interval elapses, the document enters the review queue whether or not anything has changed underneath it.
The reviewer reads the document against current practice, confirms it still matches how the work is actually done, updates the version note, and moves on. Nothing about this step requires an audience.
- The confirmation date moves
- A document reviewed with no changes still receives a fresh confirmation date. The interval resets from the day the review closed, not from the day the document was last edited.
- The version number does not
- Because the text is identical, the version stays where it was. A reader who checks the version note can see that the document was looked at and found correct, which is a different claim from a revision.
- The owner is still named
- The review owner stays attached to the document even through intervals where nothing changed. An unowned policy drifts, and a policy that drifts gets cited wrong.
A confirmation date lets a reader tell the difference between a document that is accurate and a document nobody has opened in two years. Those look identical until someone prints the date.
Events that move a document out of turn
Scheduled reviews catch slow drift. Events catch the sudden kind. Any of the following triggers an out-of-cycle review for the affected documents, and the review owner does not wait for the calendar to come around.
Trigger
A new regulation
When an external rule changes, every document that references it is pulled for review at once. The reviewer checks each clause against the new text and revises only what the change actually touches.
Trigger
A change to the process
When the underlying work changes — an approval step added, a form retired, a handoff moved — the procedure documents that describe it are revised in the same pass, so the manual and the work do not diverge.
Trigger
A merger or migration
A merger, acquisition, or system migration usually invalidates several documents at once. Those reviews run together, because the documents changed for the same reason and their version notes should say so.
Event-driven reviews are usually faster and narrower than scheduled ones. The reviewer already knows what changed, so the work is confirming that the document reflects it rather than rereading the whole manual for surprises.
Version notes
What changed, when, and why it changed
Every revision ships with a version note. The note is short and it names the substance. A reader checking whether their printed copy is still current should be able to see the difference in one pass.
Version notes also do the quiet work of letting a review owner reconstruct their own reasoning months later. That is worth more than it sounds when a question comes back and the person who wrote the clause has moved teams.
A note that says nothing
Updated for clarity
A reader cannot tell what moved. If they printed the clause last quarter, they still do not know whether their copy is current, so they have to open the full document and compare it line by line.
A note that carries the change
Approval threshold raised from $500 to $750
The reader knows immediately whether the copy in their hands needs replacing. The note also tells the next reviewer what to check if the threshold moves again.
Version notes are not a summary of the document. They are a record of the difference between this version and the one before it.
Reporting an outdated document
If a clause no longer matches the work, say so
Readers find drift faster than reviewers do, because readers are the ones applying the clause. If something in the library no longer matches how the work is actually done, report it through the contact page.
- Include The document title, as it appears in the library.
- Include The section or clause the problem sits in.
- Include What you observed that the document does not reflect.
That is enough to act on. You do not need to propose replacement wording, and you do not need to know which owner holds the document. Routing is the office's job, not the reporter's.
Where reports go
Reports are logged and routed to the same queue as an internal revision request. A reader's note and a manager's note follow the same path from there.
The office does not skip review because a report came from outside. It does not jump the queue either. Both of those would make the review interval meaningless, which is the one thing the process is built to protect.
By email
[email protected]Office hours
Monday to Friday, 9:00 AM – 6:00 PM (Eastern Time)
Open the contact pageSuperseded and withdrawn
Nothing is deleted from the library
Readers cite policies in emails, contracts, and training material. A citation that leads nowhere is worse than a citation that leads to a clear retirement notice, so old versions stay where the link expected them to be.
Archive notices
Replaced by a successor
The old version stays in the library marked superseded, with a link to the document that replaced it. A reader who lands on the old text is one click from the current one.
Retired with no successor
The document moves to the archive marked withdrawn, with the withdrawal date on the record. The notice states plainly that there is nothing to replace it, so no one keeps searching for a version that does not exist.
Cited but out of date
Where a superseded document is still referenced from a training deck or a contract, the archive notice carries the reference forward. The link keeps working; the reader just arrives at the right version.
Archived documents are not maintained. They are preserved exactly as they stood on the day they were retired, so a question about what a rule used to say has a real answer.
What the review process does not do
Revision is not the same as activity
It does not rewrite documents that are working. It does not add sections because another organization has them in theirs. It does not chase a review interval down to the day when the review owner is mid-cycle on a higher-priority document.
The goal is a library that stays trustworthy over years. A library that looks busy is a different thing, and it is usually the one that stops being read.
The fixed conventions the review process protects are set out on the documentation standards and information architecture pages. Review keeps those conventions honest; it does not renegotiate them each cycle.
Questions readers ask about review
Short answers to the questions that come back most often. If yours is not here, the contact page is the right route.
How long does a review take once it is queued?
It depends on the document, not on the queue. A single procedure with a narrow scope can close in one sitting; a manual that spans several departments takes longer because the reviewer has to confirm each clause with the people who apply it. The interval is what sets the deadline, not the estimate.
Can I see the version note before I print a copy?
Yes. The note is part of the published document, not an internal log kept behind it. Check the version note against the copy in your hand before you rely on it, especially if the copy is more than a few months old.
What happens if I report something that turns out to be correct?
Nothing bad. The reviewer confirms the clause still matches practice and moves on, exactly as they would for a scheduled review that found no change. There is no penalty for a report that does not lead to a revision, and no log of reports that is used against a reader.
Why keep documents nobody references anymore?
Because references outlive the documents they point to. Contracts, audits, and training records keep citing a clause long after it was retired. Keeping the archived version reachable with a clear notice answers the question without reopening a document that no longer applies.
Does a review ever change the review interval itself?
Occasionally, and only as a deliberate decision. A document tied to a volatile process may be shortened to a tighter interval; a stable reference document may keep a longer one. Changing the interval is itself a versioned change, so the reason stays on the record with everything else.
Where to go next
Keeping the library current is a standing job
If you are checking whether your own copy of a document is still valid, start with the version note. If you have found something the library has not caught up with, the contact page routes it into the same queue as everything else.
Office
1600 Pennsylvania Avenue NW, Washington, DC 20500
Monday to Friday, 9:00 AM – 6:00 PM (Eastern Time)