Ch1. The Structure of Official Documents — Why Government Documents Are Written This Way

What Is an Official Document?

An official document is any record created or received by a government agency or organization in the course of conducting official business.

Whether you’re preparing for federal employment, working in a government contractor role, or studying public administration — mastering official document writing is a core professional competency. Unlike private-sector business writing, government documents must comply with established standards and formats mandated by law and policy.

Key U.S. References:

Plain Writing Act of 2010 (Pub. L. 111-274): requires federal agencies to use plain language in all public communications
Federal Plain Language Guidelines (plainlanguage.gov)
Office of Management and Budget (OMB) Circular A-11 (budget documents)
Agency-specific style guides (e.g., State Department, DoD, EPA)

Types of Official Documents

Classification by Function

Type	Description	Examples
Regulatory Documents	Rules, orders, and notices with legal effect	Federal Register notices, final rules, guidance documents
Directive Documents	Instructions from a superior unit to a subordinate	Executive orders, agency directives, policy memos
Public Notices	Information broadcast to the public	Public notices, announcements, press releases
Internal Records	Documents for internal retention and reference	Casework files, action tracking logs
Correspondence	Communication with individuals or other entities	Constituent letters, interagency letters
General Documents	All other official records	Memos, reports, requests for proposals (RFPs)

Classification by Direction of Flow

Memorandum (Memo): internal communication, typically within an agency or department
Official Letter: formal external communication addressed to individuals, organizations, or other agencies
Report: analysis or findings provided to a supervisor, leadership, or Congress
Action Memo: requests approval or decision from a superior

Basic Structure of a U.S. Government Document

Most U.S. government documents follow a Header – Body – Footer structure. Memos follow a standardized header block; letters follow a letter format.

Memo Header Block

MEMORANDUM

TO:    [Name, Title, Office]
FROM:  [Name, Title, Office]
DATE:  [Month Day, Year]
RE:    [Subject — concise, specific]

TO: recipient’s name and title
FROM: author’s name and title (initialed by hand on paper copies)
DATE: spelled out in full (May 5, 2025) or standard federal format
RE / SUBJECT: a concise statement of the memo’s topic (comparable to an email subject line — make it specific)

Body

The substantive content of the document. Organized with headings and numbered lists as needed.

Organization Sequence:

Purpose / Background (why this document exists)
Key information or analysis
Action requested or recommendations
Attachments noted (if any)

[Signature block]
Name
Title
Agency
Phone / Email

Attachments: 1. [Title] 2. [Title]

Subject Line (RE:) Principles

The subject line must allow the reader to understand the document’s purpose without reading the body.

Weak subject line: “Monthly Report Submission” → Fails to convey which report, for what period, or why

Strong subject line: “FY 2025 Q2 Training Completion Data — Submission Request” → Fiscal year, quarter, topic, and action are all clear

Subject Line Best Practices:

Use a noun phrase ending with the action type (“Request,” “Notification,” “Transmittal”)
Include key specifics (FY, program name, deadline)
Keep it to one line (under 10 words when possible)
Avoid vague filler (“Re: various items,” “Update,” “FYI”)

Numbering and List Conventions

U.S. federal documents use different list conventions depending on the agency and document type.

Standard Outline Format (OMB / Federal Register): Level 1: I., II., III. Level 2: A., B., C. Level 3: 1., 2., 3. Level 4: a., b., c. Level 5: (1), (2), (3)

Plain Language Approach (plainlanguage.gov recommendation):

Bullet points for unordered lists
Numbers for sequential steps or ranked items
One level of indentation per sub-item
Avoid nesting more than two levels deep

Example:

A. Training Program Overview
   1. Program Objectives
      a. Strengthen mission-critical competencies
      b. Improve organizational culture
   2. Target Audience

B. Training Schedule

If a list has only one item, do not use a list format — write a complete sentence.

Date and Number Conventions

Dates in federal documents: Formal: May 5, 2025 OMB/fiscal year context: FY 2025, FY25 Q2 Regulatory: effective date stated in rule text

Numbers: Spell out one through nine in narrative text; use numerals for 10 and above Example: “three agencies” but “15 employees” Always use numerals for money, percentages, measurements, and technical data

Dollar amounts: Use standard formatting with commas Example: $1,000,000 or$ 1 million (spell out for large round numbers in narrative)

Time: Use 12-hour format with a.m./p.m. in most U.S. government documents Example: 2:00 p.m. (not 14:00, unless a military or 24-hour context)

Plain Language Writing Principles

Subject-Verb Agreement and Active Voice

The most common problem in government writing: passive voice obscuring who is responsible.

Problematic: “Training attendance is expected to be completed by all personnel in accordance with the plan outlined herein.” → Who must attend? By when? Unclear.

Revised: “All staff must complete the training by June 30, 2025, as outlined in Section 3.”

Use Precise Verbs

Avoid	Use Instead
”provide notification"	"notify"
"conduct a review of"	"review"
"make a determination"	"determine"
"prior to"	"before"
"in the event that"	"if”

Sentence Length

Plain Language Act guidelines: aim for sentences under 25 words
One idea per sentence
Break long explanations into numbered steps or bullets

Document Control Numbering

All official government documents carry a document control number or tracking number to enable filing, retrieval, and audit trails.

Typical Federal Format: Agency Code / Office Symbol / FY / Sequential Number

Example: OIYO-ADMIN-FY25-0042

The tracking number links the internal draft with the final transmitted version, supporting records management obligations under the Federal Records Act and NARA (National Archives and Records Administration) requirements.

Learning Checklist

Distinguish the six functional types of official documents
Describe the header–body–footer structure of a government memo
Apply the five principles of a strong RE:/Subject line
Use the correct outline numbering levels for a formal document
Apply Plain Language Act conventions for dates, numbers, and sentence length
Identify and correct subject-verb errors and passive constructions