Plain-language policy documentation, organized for the work
Yulmeris publishes policy references, style guidance, and documentation standards for people who write, review, or cite official material in U.S. public-sector and compliance settings. Most policy problems are findability problems first: the rule is written down somewhere, but the path to it is unclear.
Start where your task starts
You probably arrived with one of four jobs
Cite an immigration rule, pick a writing standard for a team, restructure a long guidance page, or track a rulemaking docket. The library is arranged around those jobs rather than around issuing agencies, because a compliance writer needs the answer, not the org chart.
Each reference page explains what the source covers, how it is organized, and the limits of what it can settle. If your question is about a specific case decision or a live filing deadline, this library points you to the authoritative source instead of standing in for it.
- Cite an immigration rule Start with the USCIS Policy Manual reference, then follow the citation pattern to the volume and part you relied on.
- Pick a writing standard Compare the HMRC content style guide, the Buckinghamshire Council style guide, and the ARPANSA Style Manual side by side.
- Restructure a guidance page Move the actionable step above the background, and keep the legal context a reviewer still expects.
- Track a rulemaking docket Follow the Regulations.gov walkthrough for docket tracking and public comment workflows.
One catalog, four jobs, and a review date on every entry.
What the library holds
Agency manuals, federal circulars, and government style guides
The catalog covers agency policy manuals, federal circulars, and government style guides. Regulations.gov gets its own walkthrough because comment workflows are a distinct skill from reading a manual.
USCIS Policy Manual
A centralized repository of immigration policy rather than a single numbered standard, so the entry focuses on how the volumes and parts are arranged and how to name the section you actually used.
Open the USCIS Policy Manual referenceBudget and internal control
OMB Circular A-11 covers budget submission guidance; OMB Circular A-123 covers internal control documentation. Different readers, different obligations.
Government style guides
The HMRC content style guide, the Buckinghamshire Council style guide, the ARPANSA Style Manual, and the Digital.gov directory of agency style guides.
How a reference page is built
Every entry follows the same skeleton so you can scan it in under a minute. The order never changes, which means you can jump straight to the part you need on any page in the library.
One example: the entry on Digital.gov's style-guide collection notes that the page is a directory rather than a single standard, and that its metadata shows a 2026 update against a 2017 publication date. That distinction changes how you cite it.
See documentation standards-
1
What it is and who issues it
The issuing body and the instrument type, stated plainly before any analysis begins.
-
2
How it is organized
Whether the source behaves like a numbered hierarchy you can point at, or a searchable repository you have to query.
-
3
How to cite it without mangling the reference
The workable citation shape for that document family, with a consistent pattern you can carry across a project.
-
4
Where it stops being authoritative
The boundary of the source, written out so you know when to go back to the issuing agency instead of leaning on a summary.
Plain language without losing precision
Plain language and legal precision compete for the same sentence
The practical rule is to keep the obligation exact and strip everything around it. Write that the agency must publish the notice within 30 days, rather than dressing the same obligation in abstract phrasing.
Style guides in this library converge on the same habits: sentence case for headings, active voice, everyday words over jargon, and numbered steps when order matters. The ARPANSA Style Manual goes further and distinguishes tone for informal internal notes versus external documentation.
Compare writing standardsWhere teams usually go wrong
Three failure patterns show up again and again in documentation reviews. None of them require a legal background to avoid, and all three are cheaper to fix before a reviewer finds them.
Citing a superseded version
The most common mistake is citing a superseded version of a manual because the citation was copied from an older memo. Checking the volume and part against the current source takes a minute and prevents a reviewer flag.
Treating a style guide as policy
The HMRC content style guide is explicit that content style and software implementation language are separate concerns. A style guide sets how you write; it does not create an obligation.
Background before the first step
A long guidance page that opens with three paragraphs of background before the first actionable step loses the reader who already knows why they are there. Task-first structure fixes it, and the documentation standards page explains how to do that without losing the legal context a reviewer expects.
Structure and hierarchy
Policy documents carry their own hierarchy, and your cross-references should respect it. A circular has sections and appendices; a policy manual has volumes and parts; a web page has headings that screen readers navigate.
When you link between them, name the target precisely enough that a reader who prints the page can still find it. A link that says only the document title leaves a printed reader with nowhere to go.
- Circular
- Sections plus appendices, cited by section number and appendix letter.
- Policy manual
- Volumes and parts, cited by volume, part, and chapter so the reference survives a printout.
- Web page
- Real heading levels that assistive technology can navigate in order.
Accessibility as a formatting constraint
Accessibility rules shape policy pages more than most writers expect
Descriptive link text, real heading levels instead of bold text, tables with header rows, and alt text that states the document rather than its appearance. Sentence case headings help scanning and screen-reader pronunciation.
These are formatting decisions, but they change how you write the sentence above them, which is why the style and standards comparison treats accessibility and readability as one topic rather than two.
Compare writing standardsUpdates and currency
A reference page that does not say when it was checked is only half useful
Official guidance changes, so Yulmeris pages carry the review date for the source material they describe. The USCIS Policy Manual entry, for instance, reflects a September 2025 date with an October 2025 update recorded in the page metadata.
When you spot a stale link or a quoted rule that has moved, the contact page is the fastest route to a correction.
Report an outdated referenceWho this is for
Compliance writers, agency communications staff, policy analysts, and contractors who draft documentation against federal or state guidance. It is also used by teams that are new to government writing and need a defensible starting standard before they publish.
You do not need a legal background to use the library, but you do need to treat the source documents as authoritative and this site as a map.
Choosing between overview-first and task-first
Overview-first suits readers who must understand scope before acting: auditors, counsel, program managers. Task-first suits readers who already know why they are on the page and need the next action.
Most policy sites need both on the same page, with the overview short enough to scroll past. The documentation standards page covers when to split them into separate pages instead of stacking both at the top.
Overview-first
Scope and boundaries stated early, then the actions. Best when approval depends on someone understanding what the document can and cannot settle.
Task-first
The next action opens the page, with context folded in. Best when the reader arrived from a search with one thing to finish.
Questions we get before people start reading
Three answers cover most of what visitors ask before they open their first reference page.
Is this an official government website?
No. Yulmeris is an independent documentation hub that describes official sources and links to them. The source documents remain authoritative.
Can I cite this site instead of the original policy manual?
Cite the original. Use these pages to find the right document, understand its structure, and format the reference correctly.
Do you cover state and local guidance?
The library includes local examples such as the Buckinghamshire Council style guide for comparison, but its main focus is U.S. federal policy documentation and writing standards.
Find the reference that matches your task, then take the cross-reference with you
Start in the policy library if you know the document family, or read the documentation standards first if you are setting a house style for a team. Corrections and stale links go to the contact desk, and the working hours are Monday to Friday, 9:00 AM to 6:00 PM Eastern Time.
- [email protected]
- Phone
- +1 202-457-6857
- Address
- 1600 Pennsylvania Avenue NW, Washington, DC 20500