Digital preservation readiness checklist
Sixteen checks that show whether your digitized collection will still be complete and readable after the project ends, related to the NDSA Levels of Digital Preservation.
Checklist
Digitization creates a second collection that needs its own care. Files do not yellow or tear, but they disappear when a drive fails, a subscription lapses, or the one person who knew where everything was takes another job. This checklist asks the questions that decide whether the images, text and records from a project will still be there, complete and readable, in twenty years.
The NDSA Levels
The checklist follows the Levels of Digital Preservation published by the National Digital Stewardship Alliance (NDSA). The Levels were first created in 2013; version 2.0 was released in 2019, and version 2.1 in March 2026 with a focus on environmental sustainability. The version 2.0 matrix sets out five functional areas (Storage, Integrity, Control, Metadata and Content) across four levels: Know your content, Protect your content, Monitor your content, and Sustain your content. The quotations below are from the version 2.0 (2019) matrix.
| Checklist group | NDSA functional area | What the matrix asks for |
|---|---|---|
| Copies and storage | Storage | Level 1: “Have two complete copies in separate locations”. Level 2: “Have three complete copies with at least one copy in a separate geographic location”. Level 3: at least one copy in a location with a different disaster threat. |
| Integrity | Integrity and Control | Level 1: “Generate integrity information if not provided with the content”. Level 2: “Verify integrity information when moving or copying content”. Level 3: verify it “at fixed intervals”. Control asks you to decide, then document, who may “read, write, move, and delete content”. |
| Information and formats | Metadata and Content | Level 1: “Create inventory of content, also documenting current storage locations” and “Document file formats”. Level 3: “Monitor for obsolescence”. |
| People and plans | (around the matrix) | The matrix describes what to do to the files. These items make sure someone keeps doing it. |
Working through the checklist
Copies and storage
Two complete copies in separate places is the starting point. A third copy, with one in a different geographic area, protects against a local fire or flood. A copy that faces a different disaster threat, for example in a region with different weather and geology, goes further. List every storage medium and provider with its renewal date: drives age, and cloud contracts lapse.
Integrity
A checksum is a short fingerprint calculated from a file. Create checksums when files arrive, or verify the ones supplied with them. Check fixity on a schedule and after every move or copy, because comparing checksums is how you find out that a file has changed. Write down what happens when a check fails: which copy you restore from, and who does it. Limit write access to the people who need it. The matrix’s Level 1 also asks you to virus check all content, so the checklist includes a virus check before files enter storage.
Information and formats
Keep an inventory of what you hold and where each copy lives. Record file formats and note any at risk of becoming hard to open. Store descriptive and technical metadata with the files or linked to them, so a file can be identified without the system that made it. Packages such as BagIt bags (RFC 8493) keep files together with a manifest of their checksums.
People and plans
Name the person responsible for the files and write down what happens if they leave. Budget for storage beyond the end of the grant or project. Review this checklist once a year.
Example (fictional). At the end of a pilot box, the Aster County Historical Society receives the masters, access copies, text and records for the Okerlund family papers and the Wren Gulch Mercantile day book as a BagIt bag, with a checksum for every file and an inventory listing each name, from achs_c003_b03_f012_i004_0001_m.tif onward. The society verifies the checksums on arrival, keeps one copy on a drive at the society and one with a cloud provider in another region, and records both locations and the provider’s renewal date in the inventory. That covers the first storage, integrity and metadata items. Its open items are a fixity schedule, a written plan if the volunteer who manages the files leaves, and storage money after the pilot.
Using the checklist in a project
Run it before the project starts, to plan storage and budget, and again at handover. The storage calculator estimates how much space you need: its example of 20,000 images with 45 MB masters and three copies comes to 2.79 TB today. NDSA version 2.1 adds a focus on environmental sustainability; read it alongside the matrix when you decide how many copies to keep and how often to check them.
Our digital preservation service prepares packages like the one in the example, and the preservation handover is part of the Return stage described in how we work. The engagements page explains what a preservation handover includes. For more, see the Reading Room’s preservation and access section, or plan a preservation handover.
Send one box first.
A pilot box shows you the images, the recognized text and the catalog records before you commit a whole collection. Tell us what is in the box and what you want people to find.
Studio and contacts
24 South Weber Street, Suite 225Colorado Springs, CO 80903(719) 244-8450sales@dastok.com