Capstone Email in Federal Agencies

Email has long been one of the most difficult record types for federal agencies to manage. It is voluminous, generated continuously, and mixes substantive policy discussions with routine logistics and personal trivia. For decades, agencies relied on a “print and file” model or on individual employees deciding, message by message, whether a given email was a record worth preserving. That approach proved unworkable at scale: it was inconsistent, burdensome, and left enormous gaps in the documentation of agency activity. The Capstone approach was developed to solve this problem by shifting the unit of decision away from individual messages and toward the role of the account holder.

Capstone is a role-based, account-level method for managing email as a federal record. Rather than asking employees to classify each message, an agency designates certain accounts—typically those of senior officials and other key positions—as “Capstone” accounts whose email is captured and preserved as permanent records. The remaining accounts are generally scheduled for temporary retention and eventual disposition. This article explains the model, its policy foundation, and the practical considerations agencies weigh when adopting it.

Origins and Policy Foundation

The Capstone approach grew out of a broader federal push to move records management from paper-centric processes to electronic ones. The National Archives and Records Administration (NARA), working with the Office of Management and Budget, set goals directing agencies to manage all email in an accessible electronic format and to eliminate the practice of printing email to paper for recordkeeping. To make those goals achievable, NARA needed a method that did not depend on millions of individual filing decisions.

Capstone answered that need by offering a simplified, defensible way to schedule email. NARA issued bulletins describing the approach and developed a General Records Schedule covering email managed under Capstone. Because the General Records Schedules apply government-wide, an agency that adopts the Capstone GRS can schedule its email without drafting and submitting a custom schedule for NARA approval, which substantially lowers the barrier to compliance. Agencies that prefer a tailored approach may still propose agency-specific schedules.

How the Role-Based Model Works

The core idea is that the value of an email correlates more reliably with the position of the account holder than with the content of any single message. Senior leaders’ accounts tend to capture the most significant policy deliberations, decisions, and institutional memory, so designating those accounts as permanent captures the substantive record without requiring message-level review.

In practice, an agency typically:

• Identifies Capstone accounts based on position, such as agency heads, principal deputies, senior advisors, and others whose work documents agency mission and decisions.
• Designates those accounts as permanent, so their email is transferred to NARA after a defined period for archival preservation.
• Schedules remaining accounts as temporary, with retention periods that allow for legal, business, and accountability needs before disposition.
• Captures email automatically at the account or system level, reducing reliance on individual employee judgment.

Account designations are not static. As employees move into or out of covered positions, the agency updates its Capstone account list so that the role—not the individual—drives the records outcome.

Benefits and Trade-offs

The principal benefit of Capstone is feasibility. By eliminating message-by-message classification, it makes comprehensive email capture realistic at federal scale and produces more consistent, defensible outcomes. It also preserves the historically valuable record—senior officials’ correspondence—that researchers and oversight bodies most often seek.

There are trade-offs. Because designation is role-based, some substantive records created by non-Capstone employees may fall under temporary schedules, and some non-substantive material in Capstone accounts will be preserved permanently as a consequence of the simplified approach. Agencies accept this imprecision as the price of a workable system, and they remain responsible for ensuring that records needed for litigation, audit, Freedom of Information Act requests, or other obligations are retained regardless of an account’s Capstone status. Properly maintaining the account list and applying holds when required are therefore essential safeguards.

Implementation Considerations

Adopting Capstone is as much an organizational task as a technical one. Agencies must decide which positions qualify, document those decisions, and keep the list current through personnel changes. They must also configure their email and records systems to capture messages reliably, apply retention rules, and support search, retrieval, transfer to NARA, and disposition.

Email rarely exists in isolation, so a Capstone program should align with the agency’s wider electronic records strategy, including metadata practices, security and access controls, and handling of attachments and linked content. Litigation holds and other legal duties override routine disposition, and the system must be able to suspend deletion when a hold is in place. Many agencies measure their systems against recognized records management functional requirements when selecting or configuring tools.

Relationship to Modern ERM Requirements

For years, agencies and vendors looked to the Department of Defense’s 5015.2 standard as the benchmark for electronic records management functionality. NARA had recognized that standard for federal use, but it revoked its endorsement of DoD 5015.2 in 2022. NARA now points agencies toward the Universal Electronic Records Management (ERM) Requirements developed through its Federal Electronic Records Modernization Initiative (FERMI). These requirements describe the capabilities—capture, maintenance, disposition, transfer, and related functions—that ERM systems should support, and they apply to email managed under Capstone just as they do to other electronic records.

This shift reinforces the direction Capstone embodies: managing records by function and lifecycle rather than by legacy product certification. Agencies evaluating or maintaining a Capstone email program should frame their requirements around the Universal ERM Requirements and the relevant General Records Schedules, and should consult current NARA policy and guidance, which continues to evolve. For broader context on how email management fits within the federal recordkeeping landscape, see the federal records topic hub.