NARA’s electronic records management rule (36 CFR part 1236): system controls, email, digitization and transfer metadata, explained
Part 1236 tells federal agencies how to build records controls into their IT systems, manage email and digitize paper so the originals can be destroyed. Its latest amendment, on digitizing temporary records, took effect August 28, 2024.
The National Archives and Records Administration (NARA) sets federal records management rules in chapter XII of title 36 of the Code of Federal Regulations, and part 1236 is the part about electronic records [1]. It requires agencies to manage electronic records as part of their wider records program, to build records management and preservation into the design and operation of their information systems, and to meet added requirements for email and other electronic records [1]. Since 2019 it has also carried the standards agencies must meet when they digitize paper records and want to destroy the originals [1].
In our view, for agency CIOs and records officers this is an operations rule more than a policy one: its requirements land on system design, storage, backups, migration and decommissioning. The eCFR’s version history for the part shows its most recent amendment taking effect on August 28, 2024 [6], and NARA’s policy page, last reviewed May 1, 2026, still lists M-23-07, the OMB and NARA memorandum on the transition to electronic records, under OMB guidance [5].
Records controls built into systems
Section 1236.10 lists seven types of controls that federal records in electronic information systems need, either built into the system or provided by an external recordkeeping system [1]:
- Reliability, authenticity and integrity: records that fully and accurately represent what they attest to, protection against unauthorized addition, deletion, alteration, use and concealment, and controls such as audit trails that keep records complete and unaltered.
- Usability: records can be located, retrieved, presented and interpreted.
- Content, context and structure: the record’s own information, cross-references that show the circumstances of its creation, and the physical and logical format and relationships between data elements.
Section 1236.12 ties these controls to capital planning and the systems development life cycle. Agencies must plan the controls into the system, keep every record retrievable and usable for its NARA-approved retention period, and, where records must outlive the system, plan and budget for migrating records and metadata so they are not lost to media decay or technology obsolescence [1]. Section 1236.14 adds that migration must keep records usable until their disposition date, keep the link between records and their metadata, and cover inactive records stored off-line [1].
What counts as a recordkeeping system, and what does not
Electronic recordkeeping needs seven functions: declare records with unique identifiers, capture them, organize them against an approved records schedule, keep them secure with audit trails, manage access and retrieval, preserve them for their full retention, and execute disposition, including transfer of permanent records, deletion of eligible temporary records and holds or freezes when required [1]. The rule is direct on one point: system and file backups do not provide recordkeeping functions and must not be used as the agency’s electronic recordkeeping system [1].
Agencies must also keep inventories of their electronic information systems, review them periodically, and maintain up-to-date documentation of each system’s technical characteristics, inputs and outputs, contents, access restrictions, purpose, update rules and disposition [1].
Email and unstructured records
For email, agencies must instruct staff to preserve sender, addressee and date information, keep integral attachments, and keep full names where systems use codes or distribution lists [1]. An email system may hold the recordkeeping copy of federal records only if it has all seven recordkeeping functions, except for transitory messages with NARA-approved retention of 180 days or less, which may stay in the mail system if users do not delete them early and automatic deletion rules preserve them for the full period [1]. Agencies that let employees use a system the agency does not operate for official email must make sure those records reach an agency recordkeeping system [1]. Agencies that manage unstructured records, such as word processing and presentation files, electronically must file them in a recordkeeping system that meets the controls in section 1236.10 [1]. Our comparison of federal electronic records duties covers messaging and collaboration platforms in more detail.
Storage media for permanent records
The part still sets physical requirements for electronic media that hold permanent or unscheduled records [1]:
- storage and test areas kept at 62 to 68 °F and 35 to 45 percent relative humidity, and smoke-free;
- magnetic tape tested no more than 6 months before it is used for such records;
- an annual read of a statistical sample of tapes, with tapes showing 10 or more errors to be replaced; and
- permanent or unscheduled data copied onto tested new media before the media are 10 years old.
Digitizing paper so the originals can go
Temporary records (subpart D). An agency that digitizes temporary records to use the copies in place of the originals must capture all information and pages, make the copies usable for every purpose the originals served, protect them against unauthorized changes and keep them retrievable for the whole retention period [1]. It must validate quality and document the validation process, which NARA may review [1]. Once validated, source records may be destroyed under General Records Schedule (GRS) 4.5, Digitizing Records, without NARA approval, subject to legal restrictions such as litigation holds [1]. These rules took their current form in a direct final rule published May 30, 2024 and effective August 28, 2024, which incorporated GRS 4.5 [3].
Permanent records (subpart E). A 2023 final rule, effective June 5, 2023, added standards for digitizing permanent records so that agencies may dispose of the source records, along with transfer metadata requirements [2]. The subpart covers paper and photographic prints digitized with reflective techniques, and leaves out photographic negatives, film, micrographic and radiographic materials, and audio and video media [1]. Among its requirements [1]:
- intellectual and physical control of the records before work starts, for which the rule names an inventory as one traditional technique, recording gaps and missing records;
- integrity protection, either SHA-256 checksums recorded as technical metadata or file integrity monitoring or comparison audits;
- approved file formats, with JPEG 2000 visually lossless compression tested and capped at 20:1; and
- validation by staff separate from those who did the quality control inspections, after which the digitized versions are the permanent records.
The same 2023 rule also required agencies to review, every five years, all records schedules that are ten years old or older [2].
Transfer metadata and the electronic-only deadline
When permanent records move to the National Archives, the agency must enter transfer metadata in NARA’s Electronic Records Archives (ERA) when it creates the transfer request; mandatory fields include the transfer request number, title, inclusive dates, creating organization and record group number [1].
M-23-07, dated December 23, 2022, set the deadline these rules support. It required agencies to manage permanent records electronically by June 30, 2024 to the fullest extent possible, to transfer permanent records to NARA after that date in electronic formats with appropriate metadata, and to digitize permanent records created in analog formats before transfer starting July 1, 2024 [4]. It said that after June 30, 2024 NARA would no longer accept new transfers of analog records unless it granted a limited exception, for reasons such as cost exceeding benefit or exceptional intrinsic value in the original format [4].
Where this lands in IT operations
In our view, part 1236 turns several routine IT decisions into records decisions. Retiring a system, changing a backup regime, moving email or file shares to a cloud service, or buying a scanning contract each touches a specific section: migration planning, the ban on backups as recordkeeping, email retention controls, or the digitization standards. Agencies that keep these sections in their system life cycle checklists find the questions early rather than at decommissioning.
This explainer describes the regulation; it is not legal advice, and agencies should confirm with their records officer and counsel how it applies to them.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.