Content governance at Paldorin Digital Policy Center
How Paldorin Digital content is governed
Policy documentation ages badly when nobody owns it. This page explains how documents get created, reviewed, updated, and retired, and who is accountable at each step. Every published document on this site has a named owner, a review interval, and a recorded history.
Every document has an owner
Each published policy, guide, or standard carries the name of a document owner: the person accountable for its accuracy and for responding when it is questioned. Ownership is a role, not a committee, so there is a single point of answer when a reader reports a problem.
Ownership transfers through the approval process and is recorded in the administration block at the end of the page, so readers can see who is currently responsible.
The documentation lifecycle
Nothing skips the review stage — including small edits.
A formatting fix and a changed requirement look similar in a diff and have very different consequences. So documents move through the same defined sequence every time, and the lifecycle applies to style and accessibility documents as much as to policy.
-
Proposal
Someone identifies a need for a new document or a change to an existing one, and the scope is written down before drafting starts.
-
Drafting
The text is written against the standard template, so structure stays predictable for readers comparing two documents.
-
Review
Affected parties check the text against how the rule actually works day to day — not against how it was imagined at the outset.
-
Approval
Formal sign-off in the Policy Handbook, which is also where ownership transfers to the person now accountable.
-
Publication
The document goes live with its owner, review date, and change history attached to it from the first day.
-
Periodic review
Scheduled checks confirm the document still reflects practice, or that a stated requirement still holds.
-
Revision
Substantive changes go back through review and approval before the page updates, so the live version is never ahead of the decision.
-
Retirement
A document no longer in force is marked retired, dated, and archived with a pointer to whatever replaced it.
Review intervals and triggers
Scheduled reviews run on a fixed interval set by the document owner and noted on the page. Between scheduled reviews, four things force an earlier look:
- A change in law or regulation that touches the same subject.
- A change in how we operate that makes the written rule out of date.
- A reported error, wherever it comes from.
- A pattern of questions from readers that suggests the text is unclear. This last one catches the failure mode where a policy is technically correct and consistently misread, so the fix is an edit to the document rather than retraining for the reader.
Review intervals are not a way to postpone work indefinitely; the date on the page is the commitment, and an interval that no longer suits the document is itself something the owner can change.
A good outcome can be no change
Most reviews close with a note that the document stands as written, plus a new review date. A review that finds nothing wrong is not wasted effort.
What the owner checks
- The document still reflects current practice.
- Referenced documents still exist under the same names.
- The compliance requirement is still stated in plain terms.
Versioning and change records
Changes are versioned and logged rather than edited in place. Readers who cite a section can see when it last changed and what moved, which matters when a document is used to justify a decision later.
We treat section headings as stable identifiers: renaming one is a version-worthy change, because external documents link to headings rather than page tops. The log lives with the document it describes, and older versions remain available on request through the Contact page.
Section headings are treated as stable identifiers.
Who reviews what
Drafters write, owners own, and reviewers drawn from affected groups check the text against how the rule actually works day to day. Legal review joins the process for anything touching privacy, contracts, or regulatory obligations. The Documentation Style Guide governs wording during review, which keeps review comments focused on substance instead of formatting arguments that a standard already settled.
Drafter
Writes the text against the standard template, keeps it in plain language, and hands it to the owner before it goes anywhere else.
Document owner
Accountable for accuracy, for the review interval, and for answering when the document is questioned. Ownership transfers through approval and is recorded on the page.
Reviewers from affected groups
Test the wording against the actual working routine, and flag the places where the written rule and the lived process have drifted apart.
Legal review
Joins for anything touching privacy, contracts, or regulatory obligations, and confirms the requirement is stated in terms the organization can stand behind.
Governs wording during review, so comments land on substance instead of sentence construction that a published standard already settled.
Reporting errors and gaps
Anyone can report a problem, inside or outside the organization. The Contact page routes messages to the document owner named on the affected page, so nothing depends on the reporter finding the right person.
A useful report names the page, the section, and what you expected to find instead. Reports are tracked to resolution, and if the fix changes a rule rather than a typo, it goes back through the approval process before the page updates.
Archiving and retiring documents
Policies do not get deleted. When a document is no longer in force, it is marked retired, dated, and kept in the archive with a pointer to whatever replaced it.
This matters for anyone who acted under the old rule and needs to show what it said at the time. A reader following a citation from last year should still find something that explains the change, not an empty page.
Interactive deletion is the one thing our governance process does not allow, because a broken link at the wrong moment reads as a cover-up even when it is not. Retirement is recorded as a version, the same way every other change is.
If you need a specific archived version, request it through the Contact page with the document name and the period you are after. Archived versions are kept with their effective dates so the request can be answered with the exact text that was in force.
Signals for the review queue
Measuring whether governance works
We track a few blunt indicators: the share of published documents carrying a current review date, the time from an error report to its resolution, and the volume of reader questions that reach Contact. None of these is a performance target to game — they are signals for the review queue.
Share of published documents with a current review date
A document that slips past its interval shows up here before a reader has to find it.
Time from error report to resolution
Typographical fixes close quickly; changes to a rule take longer because they go back through approval first.
Volume of reader questions reaching Contact
A rising volume of questions about one document is evidence the document needs editing, not that readers need retraining.
Questions readers ask
Short answers to the questions that most often arrive through the Contact page.
How quickly are reported errors fixed?
Typographical fixes are usually corrected within days. Changes to an actual rule go through review and approval first, so they take longer and land as a logged version rather than a silent edit.
Can I see an older version of a policy?
Yes. Archived versions are kept with their effective dates. Request the specific version through the Contact page and name the period you need.
Who approves a brand-new policy?
The named owner drafts it, affected parties review it, and it is approved through the formal process defined in the Policy Handbook. Ownership is recorded on the page as soon as the document goes live.
Do style and accessibility documents follow the same process?
They do. The lifecycle applies to style and accessibility documents as much as to policy, which is why a wording change in the Documentation Style Guide can affect how a policy is reviewed later.
Need a correction, or an older version?
Send the page, the section, and what you expected to find. Messages route to the document owner named on the affected page, and anything that changes a rule goes back through approval before the live page updates.
Paldorin Digital Policy Center · 1201 Wilson Boulevard, Suite 700, Arlington, VA 22209 · Monday to Friday, 9:00 AM – 6:00 PM Eastern Time