# Checklist: records controls in federal agency systems under NARA’s 36 CFR part 1236

Fourteen steps for agency records officers, CIOs and system owners: system inventories, the seven recordkeeping functions, email and personal accounts, migration and media, digitizing paper before disposal, transfer metadata, contracts and incident reports.

Checklist · Government · Platforms & Architecture. Published November 14, 2026. Last reviewed November 14, 2026.

## What part 1236 asks of agency systems

NARA’s rule on electronic records management, 36 CFR part 1236, requires federal agencies to build records management and preservation into the design, development and implementation of their electronic information systems, sets added requirements for email and other unstructured records, and sets standards for digitizing temporary records and permanent paper, photographic print and mixed-media records so the source records can be disposed of [1]. As checked on November 14, 2026, the eCFR’s version history for part 1236 gives August 28, 2024 as its latest amendment date [2], the effective date of the direct final rule on digitizing temporary records published May 30, 2024 (89 FR 46803) [3]. A Federal Register search for documents affecting part 1236 published since January 1, 2024 returns only that rule [7].

## Using the steps

The steps follow a system’s life: inventory and design, the recordkeeping functions, email and messages, migration and media, digitization, contracts and incidents. Each cites the section it rests on, and the agency is the party the rule binds; the owner under each step is a typical role, not one the rule names. Where a step, or part of one, is our suggestion rather than a requirement, it says so. Our [explainer](https://insights.moraph.com/nara-36-cfr-part-1236-electronic-records-management-explained) and the [rule register entry](https://insights.moraph.com/rules/36-cfr-part-1236) set out the rule, and the tables on [federal electronic records and messages](https://insights.moraph.com/compare/federal-electronic-records-and-messages) and [records retention](https://insights.moraph.com/compare/records-retention) put it beside NARA’s bulletins and schedules. This checklist explains the rule; it is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Keep an inventory of electronic information systems, review each against agency records procedures, and keep each system’s documentation current.** (Agency records officer with the CIO’s office) Section 1236.26(a) requires agencies to maintain inventories of electronic information systems and review them periodically as part of the reviews required by 44 U.S.C. 3506, and to submit an SF 115 to NARA where schedule descriptions or retention periods no longer reflect a system’s content and use. Section 1236.26(b) requires documentation that specifies technical characteristics, inputs and outputs, file contents, access restrictions, purpose, update rules and how disposition will be carried out [1]. Linking the records inventory to the system inventory used for security authorizations is our suggestion.
2. **Build the seven records management controls into each system, or into an external recordkeeping system the records flow to.** (System owner with the records officer) Section 1236.10 lists controls for reliability, authenticity, integrity (such as audit trails), usability, content, context and structure, and lets agencies place them in the information system or in a separate recordkeeping system [1].
3. **Make records requirements part of capital planning and the system development life cycle, including a funded plan to migrate records that outlive the system.** (CIO capital planning lead) Section 1236.12 requires agencies, as part of capital planning and the development life cycle, to plan and implement the 1236.10 controls, keep records retrievable and usable for their NARA-approved retention period, plan and budget for migrating records and metadata when retention runs past the system’s planned life, provide for transfer of permanent records under part 1235, and provide a standard interchange format where needed [1]. A records officer sign-off at design review and before go-live is our suggestion.
4. **Check that every system used as a recordkeeping system can declare, capture, organize, secure, retrieve, preserve and dispose of records, including holds.** (Records officer with enterprise architecture) Section 1236.20(b) lists these seven functions, including audit trails to track use and the ability to apply a records hold or freeze on disposition [1].
5. **Do not rely on backups as the recordkeeping system.** (Infrastructure and backup lead) Section 1236.20(c) says system and file backup processes and media do not provide the recordkeeping functions and must not be used as the agency’s electronic recordkeeping system [1].
6. **Issue staff instructions for email records: keep sender, all addressees and date, integral attachments, and full names behind nicknames and distribution lists.** (Records officer with messaging administrators) Section 1236.22(a) requires these instructions and notes that calendars, task lists and circulated drafts may also be federal records [1].
7. **Use the email system as the recordkeeping copy only where it has every recordkeeping function, and confine in-place retention to transitory email of 180 days or less with deletion rules set to match.** (Messaging administrators) Section 1236.22(c) allows transitory email with a NARA-approved retention of 180 days or less to stay in the email system if users do not delete it early and automatic deletion rules keep it until the period ends. Section 1236.22(d) otherwise bars using an email system for the recordkeeping copy unless it has all the features in 1236.20(b), and requires instructions for copying records out of a system that lacks them [1]. Testing the mail platform’s retention settings against the approved schedules each year is our suggestion.
8. **Capture records sent from systems the agency does not run, and from personal messaging accounts, in an official account or recordkeeping system.** (Records officer with general counsel) Section 1236.22(b) requires agencies that let employees use email systems the agency does not operate to preserve the records in the appropriate agency recordkeeping system [1]. Under 44 U.S.C. 2911, an officer or employee of an executive agency may create or send a record from a non-official electronic messaging account only if an official account is copied, or a complete copy is forwarded to an official account not later than 20 days after the original creation or transmission; an intentional violation is a basis for disciplinary action [6].
9. **Before retiring or upgrading a system, check whether its records must outlive it, and migrate them with their metadata.** (System owner) Section 1236.14 requires agencies to determine whether retention will exceed the system’s life and plan migration before retirement, to keep records usable and their disposition executable after conversion, to keep the link between records and metadata and capture metadata at the point of migration, and to cover non-active records stored off-line [1].
10. **Hold storage media with permanent or unscheduled records to the rule’s environment, testing and copying standards.** (Data center operations) Section 1236.28 sets storage at 62° to 68 °F and 35% to 45% relative humidity in smoke-free areas, requires testing magnetic tape no more than 6 months before use, an annual read of a statistical sample (20% or 50 media, whichever is larger, for libraries of 1800 or fewer; 384 media above that), and copying data to tested new media before the media are 10 years old [1].
11. **Before destroying paper records that were digitized, confirm the scans meet the standards, validate them, document the validation and check for litigation holds.** (Records officer with the digitization project lead) For temporary records, sections 1236.30 to 1236.36 require digitizing to the standards in 1236.32, validating under 1236.34, keeping the validation documentation for the life of the process or of the records digitized with it, whichever is longer, and considering legal restrictions such as a litigation hold before destroying sources under GRS 4.5; no NARA approval is needed to destroy scheduled temporary sources digitized this way [1]. The 2024 direct final rule brought GRS 4.5 into the regulation [3]. For permanent records, 1236.56 requires validation by staff separate from those who did the quality control inspections, and keeping project documentation until NARA confirms receipt and legal custody [1].
12. **Enter the required transfer metadata in NARA’s Electronic Records Archives when transferring permanent digital records.** (Records officer) Section 1236.58 requires transfer metadata, entered in ERA when the Transfer Request is created, with mandatory fields such as transfer title, inclusive start and end dates, creating organization, record group number, general records type and access restriction status [1].
13. **Write records ownership, delivery and technical documentation into contracts for systems and services that create agency records, including cloud and software as a service.** (Contracting officer with the records officer) Section 1222.32 requires contracts to specify Government ownership and delivery of the records needed to document contractor-operated activities, requires electronic records delivered to come with enough technical documentation to use them, and requires deferred ordering, delivery-of-data and rights-in-data clauses where needed [4]. Requiring export of records with their metadata in a usable format at contract end is our suggestion.
14. **Report any unlawful or accidental removal, defacing, alteration or destruction of records to NARA promptly, with the details the rule lists.** (Agency records officer) Section 1230.14 requires a prompt report describing the records, the office, the circumstances, the safeguards set up to prevent further loss and, where appropriate, salvage actions, submitted or approved by the official authorized to sign records schedules [5]. Adding a records check to the security incident response playbook, so a ransomware or deletion event triggers this report, is our suggestion.

## Sources

1. National Archives and Records Administration, Electronic Code of Federal Regulations. 36 CFR part 1236, Electronic Records Management (eCFR current to November 12, 2026). <https://www.ecfr.gov/current/title-36/chapter-XII/subchapter-B/part-1236> Checked November 14, 2026.
2. Office of the Federal Register, Electronic Code of Federal Regulations. eCFR version history for 36 CFR part 1236 (versioner API; latest amendment date August 28, 2024). <https://www.ecfr.gov/api/versioner/v1/versions/title-36.json?part=1236> Checked November 14, 2026.
3. National Archives and Records Administration, Federal Register. Federal Records Management: Digitizing Temporary Records (direct final rule, 89 FR 46803, May 30, 2024): document details via the Federal Register API. <https://www.federalregister.gov/api/v1/documents/2024-11910.json> Checked November 14, 2026.
4. National Archives and Records Administration, Electronic Code of Federal Regulations. 36 CFR 1222.32, How do agencies manage records created or received by contractors? (eCFR current to November 12, 2026). <https://www.ecfr.gov/current/title-36/section-1222.32> Checked November 14, 2026.
5. National Archives and Records Administration, Electronic Code of Federal Regulations. 36 CFR 1230.14, How do agencies report incidents? (eCFR current to November 12, 2026). <https://www.ecfr.gov/current/title-36/section-1230.14> Checked November 14, 2026.
6. U.S. Government Publishing Office, govinfo. 44 U.S.C. 2911, Disclosure requirement for official business conducted using non-official electronic messaging accounts (United States Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title44/html/USCODE-2024-title44-chap29-sec2911.htm> Checked November 14, 2026.
7. Office of the Federal Register. Federal Register API search: documents affecting 36 CFR 1236 published on or after January 1, 2024. <https://www.federalregister.gov/api/v1/documents.json?conditions[cfr][title]=36&conditions[cfr][part]=1236&conditions[publication_date][gte]=2024-01-01> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-nara-36-cfr-part-1236-electronic-records-controls-in-agency-systems>
Publisher: Moraph Insights
