Ch4. Tables, Attachments, and Final Checklists — Formatting Official Documents Correctly

Principles for Using Tables and Lists

When to Use a Table

A table is more effective than prose in the following situations:

Comparison: comparing two or more items across multiple attributes
Multi-dimensional data: information where rows (items) and columns (attributes) intersect
Schedules and procedures: when date, owner, and description must be shown simultaneously

Poor use: creating a table for a single item or a simple enumeration. Tables resolve complexity — use them only when complexity is present.

Table Formatting Principles

┌──────────────────────┬──────────────────────┬───────────────────┐
│ Training Topic       │ Date / Time          │ Location          │
├──────────────────────┼──────────────────────┼───────────────────┤
│ Workforce Competency │ Mon., Sep. 1, 2025   │ Main Auditorium   │
│ Organizational Culture│ Tue., Sep. 2, 2025  │ Main Auditorium   │
└──────────────────────┴──────────────────────┴───────────────────┘

Number and title the table above it: Table 1. Training Schedule
Right-align numbers within cells
Left-align or center text within cells
Place units in the column header, not in every cell

Attachment (Enclosure) Formatting

How to List Attachments

In a formal U.S. government or professional memo, list enclosures after the signature block.

Enclosures:
  1. FY 2025 Training Plan (1 copy)
  2. Participant Registration Form (1 copy)

For a single attachment:

Enclosure: FY 2025 Training Plan

Principles:

List each enclosure with a number, descriptive title, and copy count
Placed after the signature block and any copy-to lines
In formal federal correspondence, the word “Enclosure” is preferred over “Attachment” (both are acceptable)

Attachment Quality

Attachments are part of the official record.

File-naming convention: YYYYMMDD_DocumentTitle_v1.pdf (e.g., 20250901_TrainingPlan_v1.pdf)
Include page numbers on documents longer than five pages
Readability: legible font size (minimum 10pt), consistent margins, aligned tables
Remove internal drafting notes and tracked changes before attaching

Post-Approval Processing

Draft → Issued Document Workflow

Once a document has received final approval, it moves through the following steps:

Confirm approval date: the date the final authorizing official signed
Assign document number: agency code – office – fiscal year – serial number
Add addressee information: recipient agency name and point of contact
Set effective date: same as or later than the approval date
Finalize format: attach official seal, wet signature, or electronic signature (PKI / HSPD-12 credential)

Records Retention and Transfer

Federal records are managed under the Federal Records Act (44 U.S.C. Chapter 31) and National Archives and Records Administration (NARA) General Records Schedules.

Retention Period	Document Type
Permanent	Laws, major policy decisions, agency establishment documents
30 years	Major program decisions, budget formulation records
10 years	General policy documents, audit-related records
5 years	Routine administrative processing documents
3 years	Routine public inquiries and correspondence
1 year	Routine daily communications

Agencies must follow their agency-specific NARA-approved records schedule. Unauthorized destruction is a federal violation.

Electronic Document Systems

Federal Document Management Platforms

Modern federal agencies process, approve, and transmit official documents primarily through electronic document management systems (EDMS).

Key platforms:

MAX.gov: OMB’s federal collaboration and document portal
eOPF (Electronic Official Personnel Folder): OPM’s personnel records system
ITAS / GovTrip / Concur: travel and expense authorization
SharePoint / M365 Government Cloud: widely used for internal drafts and document routing

Electronic Approval Features

Full approval workflow completed online without paper
Approval routing is managed and tracked in the system
Real-time status visibility for all parties in the routing chain
Official transmission (to external agencies) also handled within the system

Electronic signatures: PKI-based digital signatures (under HSPD-12 / FICAM standards) carry the same legal authority as wet signatures for federal documents.

Common Formatting Errors in Official Documents

Error 1: Inconsistent Heading Hierarchy

I. Background
   A. Purpose: [correct]
   3. Target Audience: [mixed — incorrect]

→ Use a consistent, sequential heading hierarchy. Federal documents commonly follow the outline format (I → A → 1 → a) or the decimal format (1 → 1.1 → 1.1.1).

Training begins July 1st, 2025 — inconsistent
Training begins July 1, 2025 — correct (U.S. government standard)
Training begins 2025-07-01 — acceptable in data contexts (ISO 8601)

Agencies typically follow AP Style or their own style guide. Pick one and apply it consistently throughout the document.

Final Pre-Dispatch Checklist

Check all official documents against the following before transmitting:

Header

Issuing agency name and address correct
Addressee fully specified (agency, office, name, title)
Subject line: concise (10–15 words), accurately describes content

Body

Heading hierarchy consistent throughout (I → A → 1 → a)
Dates: consistent format (e.g., July 1, 2025)
Numbers: Arabic numerals with units

Closing

Signature block complete (name, title, agency, date)
Enclosure list complete and accurate
Copy-to list (cc:) includes all required recipients

Overall

Passive voice minimized; clear subject in each sentence
No unexplained acronyms (spell out on first use)
Proofread for spelling, grammar, and punctuation

Learning Checklist

Identify situations where a table is more effective than prose, and vice versa
Format an enclosure list correctly for a federal memo
Describe the five-step workflow from draft to issued document
Name at least three NARA retention categories and their durations
Apply the pre-dispatch checklist to catch formatting errors in a sample document