FERMI: The Federal Electronic Records Modernization Initiative

The Federal Electronic Records Modernization Initiative, commonly abbreviated FERMI, is a federal program led by the National Archives and Records Administration (NARA) to streamline and standardize how executive branch agencies acquire and operate electronic records management (ERM) capabilities. Rather than asking every agency to independently define what an ERM system must do, FERMI provides a common foundation: a shared set of functional requirements, standardized procurement language, and supporting resources that agencies can reuse. The goal is to reduce duplicative effort, improve the quality of records management across government, and accelerate the long-running federal transition away from paper and toward fully electronic recordkeeping.

FERMI emerged from a broader policy push to make the federal government manage all of its records electronically. That push set expectations that agencies manage permanent and temporary records in electronic formats and move away from transferring paper to the National Archives. FERMI is the practical, market-facing piece of that strategy: it tries to make it easier and more consistent for agencies to buy and deploy compliant technology and services. Understanding FERMI is therefore central to understanding the modern federal compliance and standards landscape for recordkeeping.

Why FERMI Was Created

For decades, federal agencies approached ERM procurement in isolation. Each agency wrote its own requirements, evaluated products against its own criteria, and negotiated its own contracts. This produced wide variation in capability and maturity, made it hard for vendors to build to a predictable target, and forced agencies to repeatedly reinvent the same analysis. It also complicated NARA’s oversight role, because there was no common yardstick for what “good” ERM looked like across the enterprise.

FERMI addresses these problems by treating ERM as a shared government-wide need rather than a series of one-off agency projects. By publishing common requirements and acquisition materials, NARA aims to:

• Lower the cost and effort of acquiring ERM solutions for individual agencies.
• Improve consistency and quality of records management practices government-wide.
• Give the marketplace a clearer, more stable target to build toward.
• Support the policy goal of managing federal records in electronic form.

The Universal ERM Requirements

The centerpiece of FERMI is a set of functional requirements describing what an electronic records management capability should do, often referred to as the Universal ERM Requirements. These requirements are organized around the core records lifecycle functions that any compliant system must support: capturing records and their metadata, maintaining records and protecting their integrity, supporting retention and disposition according to approved schedules, enabling transfer of permanent records to the National Archives, and providing appropriate access and reporting.

Importantly, the Universal ERM Requirements are intended to be technology-neutral and outcome-focused. They describe capabilities and expected behaviors rather than prescribing a particular software architecture or product design. This framing reflects the reality that records are increasingly created and managed across many systems—email, collaboration platforms, line-of-business applications, and dedicated repositories—rather than in a single monolithic records application. The requirements are meant to be applied wherever records actually live.

The Shift Away From DoD 5015.2

For much of the 2000s and 2010s, the de facto federal benchmark for records management software was the Department of Defense standard known as DoD 5015.2, which defined detailed functional requirements and was paired with a formal product testing and certification program. Many agencies required 5015.2 certification in their acquisitions, and NARA had historically endorsed it as a baseline.

A significant development in the FERMI story is that NARA moved away from relying on DoD 5015.2. In 2022 NARA revoked its endorsement of the 5015.2 standard, signaling that the older, certification-based, system-centric model no longer matched the modern records environment. The Universal ERM Requirements developed under FERMI are positioned as the successor reference point. The rationale is that requirements should reflect how records are created and managed today—distributed across diverse cloud and on-premises systems—rather than assuming a single certified records repository. Agencies and practitioners who built their expectations around 5015.2 should understand that NARA now points to the FERMI requirements as the current guidance.

Acquisition Tools and Shared Resources

Beyond the requirements themselves, FERMI provides supporting materials designed to make procurement easier. These have historically included standardized statements of work or solicitation language that agencies can adapt, use-case descriptions that frame common scenarios, and crosswalks that connect requirements to underlying records management policy and law. The intent is that a records officer or contracting team can start from a vetted, reusable baseline rather than drafting acquisition documents from a blank page.

These resources sit within NARA’s broader body of records management policy and guidance, and they are meant to be used alongside—not instead of—statutory and regulatory obligations. FERMI does not replace the Federal Records Act framework, NARA’s regulations, or approved records schedules; it operationalizes them by helping agencies buy and configure systems that can actually meet those obligations.

What FERMI Means for Practitioners

For records managers, IT staff, and acquisition professionals, FERMI changes the starting point for ERM projects. Instead of asking “what should our requirements be,” agencies can begin with the Universal ERM Requirements and tailor them to their environment. When evaluating solutions, the relevant question shifts from “is this product certified to a specific standard” toward “can this capability satisfy the functional requirements across the systems where our records live.”

A few practical takeaways follow from this:

• Treat the Universal ERM Requirements as the current reference baseline, and do not assume DoD 5015.2 certification is the controlling criterion.
• Map requirements to your actual systems, recognizing that records may be managed in place across multiple platforms rather than in one repository.
• Use FERMI’s acquisition materials as a reusable foundation, while still grounding decisions in the Federal Records Act, NARA regulations, and your approved schedules.

FERMI is best understood not as a single product or rule but as an ongoing modernization effort: a coordinated attempt to give the federal government a common, durable, and technology-neutral way of defining, acquiring, and operating electronic records management. As recordkeeping technology continues to evolve, the FERMI requirements are expected to evolve with it, remaining the federal reference point for what compliant electronic records management should accomplish.