The Archive's Blind Spot: When Public Records Are Designed to Be Unreadable

We spend a lot of time worrying about how to preserve digital information, but we rarely stop to ask a more fundamental question: is the information we’re preserving actually readable? I’m not talking about file corruption or obsolete formats. I’m talking about a more insidious problem—records that are technically public and perfectly preserved, yet designed from the outset to be functionally useless to human readers.

Consider the modern PDF statement. You’ve likely encountered them: utility bills, bank summaries, or government notices that arrive in your digital inbox. They are, by any official measure, a public record delivered to you. But open one. What do you find? Often, it’s a labyrinth of abbreviated field names, coded identifiers, and data presented in a dense, tabular format that only makes sense to the database that generated it. The information is all there, preserved in a stable format, yet its meaning is locked away. It is a record created for a machine’s audit, not a person’s understanding.

This is a quiet erosion of readability, a shift from documents intended for human consultation to data outputs intended for machine processing. The artifact is saved, but the context—the narrative, the explanation, the simple story of the transaction—is absent. An archivist a century from now could perfectly preserve this PDF, but without the proprietary key to its cryptic codes, it would be as inscrutable as a cuneiform tablet without a Rosetta Stone. The record exists, but its purpose and meaning do not survive.

This creates a profound blind spot in our digital memory. We are excellent at saving the ‘what’—the bits and bytes—but we are often neglectful of the ‘why’ and the ‘how’ that make those bits meaningful. It prioritizes the fact of record-keeping over the act of communication. The document fulfills a legal requirement for disclosure while failing the practical human requirement for comprehension.

The challenge, then, for those of us interested in true preservation, isn’t just to advocate for open formats and robust storage. It’s to advocate for records designed with legacy in mind—records that explain themselves. It’s to champion the inclusion of plain-language summaries, glossaries for codes, and metadata that describes not just the file’s technical specs but its intellectual structure. Because the goal of preservation shouldn’t just be to save data. It should be to save understanding.

Notes & further reading

A few pages I came back to while writing this: