Permanent Records Accession Transfer Checklist (NARA)

This checklist covers the steps needed to prepare permanent federal records for accession transfer to NARA at the end of their scheduled retention period. It typically includes record verification, folder or box inventory, metadata review, packaging, labeling, approval checks, and final transfer readiness. It is meant for the handoff process, not for routine records management.

Use it whenever a permanent records series reaches the point where transfer to NARA is due. In practice, that may be annual, quarterly, or event-driven depending on the agency’s records schedule and transfer volume. It should not be set as a generic recurring task unless the recurrence matches an actual transfer cadence.

The DRI is usually a records officer, records manager, or designated program owner who knows the series and its disposition rules. IT, legal, and the originating office may need to support verification steps, especially when records are electronic, mixed-format, or require chain-of-custody review. The checklist should make clear who owns each checklist item.

Yes, it is designed to support the transfer workflow described in 36 CFR Part 1235 by prompting the team to verify records eligibility, completeness, and transfer readiness. It does not replace agency counsel, records schedules, or NARA guidance. Use it as an operational control to reduce missed steps and prevent noncompliant transfers.

Common mistakes include transferring records before the retention period ends, sending incomplete series, using inconsistent box or file identifiers, and skipping metadata validation. Another frequent issue is failing to confirm that the physical and legal custody transfer package matches the approved accession documentation. This checklist makes each of those checks explicit and independently verifiable.

Yes, and it should be. Permanent records transfers often need different checklist items for paper boxes, digital files, media, or hybrid series, so you can add or remove steps based on format. Keep each checklist item atomic so a reviewer can answer yes, no, or N/A without ambiguity.

An ad hoc process often depends on memory, email threads, and last-minute coordination, which makes it easy to miss approvals or packaging requirements. A checklist creates a repeatable runbook with clear verification steps, making the transfer easier to audit and easier to hand off between staff. It also helps separate blocking issues from non-blocking cleanup items.

Yes. Many teams link it to records inventories, document management systems, approval workflows, or task tracking tools so the transfer status is visible in one place. It can also be paired with a Kanban board to limit work in progress across multiple accession packages and avoid overloading the records team.