In the Town of Farragut, there has been much discussion about Public Records, front page stories on Farragut Press. Kim Parks breaks it down in a podcast of her own, you can watch it here, or read it below, as she has given me permission to share it here.

Public records laws are designed to ensure transparency, accountability, and public trust. But one of the most misunderstood and increasingly contentious, aspects of public records compliance is not whether records are released, but how they are released.

A recent dispute involving the Town of Farragut highlights a problem that extends far beyond one town: the growing tendency to convert native electronic records into PDFs by default, often justified under the vague banner of “security” or “best practices.”

At first glance, this may sound reasonable. In reality, it risks altering the record itself.

What Are Native Email Files?

Emails are not simple text documents. When an email is created and stored, it exists as a structured electronic record, commonly in formats such as MSG or EML.

These native email files preserve:

• header information
• routing paths
• timestamps
• server data
• attachments in their original form
• metadata that establishes authenticity and context

This information is not optional or supplementary. It is part of the record as it exists and is maintained.

In professional records management, digital forensics, and litigation, native email files are preserved precisely because they provide a verifiable chain of custody and technical integrity.

What Happens When Emails Are Converted to PDF?

A PDF is a visual representation — a snapshot of what someone chose to display at a particular moment in time.

When emails are converted to PDF:

• metadata is stripped or obscured
• routing information disappears
• attachments may be separated or omitted
• contextual and technical verification becomes difficult or impossible

Once conversion occurs, the original electronic structure of the record is lost.

Ironically, while PDFs feel safer because they are familiar, they are often easier to alter without detection than native email files.

The Misunderstood Concept of “Secure Format”

Some agencies justify conversion by claiming that native electronic records are insecure because they can be “manipulated.” Technically, this claim does not withstand scrutiny.

Native email files are structured containers. Attempts to meaningfully alter them frequently corrupt the file, break headers, detach attachments, or render the file unreadable. Alteration often leaves detectable evidence.

This is why forensic professionals preserve email evidence in native format.

By contrast, once an email is converted to PDF — and its metadata removed — alterations can be far harder to detect.

What “Best Practices” Actually Mean

In disputes like this, agencies often rely on guidance from the Office of Open Records Counsel (OORC), citing its “best practices” as justification for conversion.

But best practices are exactly that: guidance.

They are advisory, not statutory.
They do not create new exemptions.
They do not override public records laws or local ordinances.

Best practices are intended to help agencies comply with the law — not replace it.

When guidance conflicts with statutory rights or the ordinance in effect at the time a request is submitted, the law controls.

When Legal Authority Drifts Into Technical Assumptions

One of the more concerning aspects of the Farragut dispute is how technical conclusions were asserted during a public meeting by the Town Attorney, Tom Hale, despite his own acknowledgment that he is not a technology expert.

That admission is significant.

Legal professionals are qualified to interpret statutes and ordinances. They are not automatically qualified to make technical determinations about electronic record integrity. When legal authority is used to assert technical certainty without adequate expertise — or without consulting qualified experts — the risk of error increases substantially.

In this case, an example involving editable Word documents was applied to native email files, even though the two formats function very differently. That category error became the basis for restricting access to records.

This is not a question of intent. It is a question of process and competence.

Public policy should not be shaped by analogy, habit, or assumption — especially when the result limits public access.

Opinion Is Not Authority

Attorneys offer opinions. That is their role.

But when opinion moves beyond legal interpretation and into technical conclusions — particularly after acknowledging a lack of expertise — those opinions should be treated with caution, not deference.

Governing bodies and the public are entitled to expect that decisions affecting transparency are grounded in law and fact, not convenience or guesswork.

Why This Issue Matters Beyond One Town

This debate is not unique to Farragut.

Journalists rely on metadata to verify timelines and authenticity.
Attorneys rely on native files to establish evidence.
Citizens rely on complete records to understand how decisions are made.

When original electronic records are routinely converted, transparency is weakened — even if unintentionally.

Public trust depends not just on access to records, but on access to accurate records.

A Simple Principle Worth Preserving

Public records laws were written to preserve access, not convenience.

If a record is created and maintained electronically, providing it in its original format preserves context, integrity, and trust. Conversion should be the exception — not the default.

Transparency is not a threat to government.
It is how credibility is maintained.