top of page

Government Records Are Messy

  • Writer: Britt Turner
    Britt Turner
  • Jun 13
  • 1 min read

Most discussions about records and information governance focus on federal or private-sector frameworks. Those are complex, but relatively structured.


Local government is where things get messy.


FOIA does not apply to municipal records. For that, you need state law, and those laws vary widely. Just the acronyms can be confusing: FOIL, OPRA, APRA, FOAA, CPRA, GRAMA, IPRA, PIA, Sunshine Law, Open Records... even the baseline is hard to track.


Then come the state-by-state nuances:

  • Access restrictions.

  • Varying timelines.

  • Unique exemptions.

  • Commercial purpose clauses.

  • Identification requirements.

  • Submission methods.


Different laws. Different capacity levels. Inconsistent systems. Overlapping responsibilities. A wide range of interpretations about what counts as a record and how it should be handled.


Within one singular municipality, I’ve seen situations where:

  • the same type of record is handled differently across departments;

  • staff are unsure what is subject to disclosure;

  • systems do not align with legal requirements; and

  • expectations exceed available resources.


And forget about retention and disposition.


This is where information governance stops being theoretical and becomes operational.


A practical starting point is clarity: define what constitutes a record in your environment, align that definition across teams, and make sure staff understand how it applies in real workflows.


To truly embrace the spirit of transparency, add a public education component and make points of contact for submissions and appeals easy to find. I know the worry is that this will create more volume, but clarity often reduces confusion, duplicate requests, and avoidable escalation.


Without that foundation, everything else becomes harder.


This is one of those areas where complexity doesn't go away. It just needs to be managed more intentionally.

Recent Posts

See All
Recordings Are Not Documentation

A 60-minute meeting recording is not a meeting summary. A transcript is not a procedure. A Teams recording is not a training resource. And "it's in the recording somewhere" is not a documentation stra

 
 
 
Digital Transformation & Process Design

Organizations often invest in new tools to fix existing problems. Sometimes the tools help. Sometimes they expose what’s already broken. When workflows are unclear, ownership is inconsistent, or stand

 
 
 
Meetings That Should've Had an Email

“This meeting should’ve been an email.” But what about the meetings that needed an email? I can’t count the number of times I’ve participated in a meeting where the meeting happens and… that’s it. Tha

 
 
 

Comments


CONNECT

  • LinkedIn
bottom of page