Ep. 16 No Legitimate Concern

When an Office of Financial Management public records officer complained in writing about requests from “West and Nixon,” she didn’t just vent about workload. She accused those requests of having “no legitimate concern,” suggested there should be ways to “tighten and restrict those particular types of requests,” and contrasted them with what she called “legitimate requests.”
In this episode, Jamie Nixon breaks down why that email matters, what request OFM was actually processing at the time, and why the request at issue was plainly in the public interest: records about the 2020 deletion of roughly 1.5 terabytes of Microsoft Teams chat data during the first summer of COVID. The episode also draws on the Washington Coalition for Open Government’s 2024 report to argue that requesters are not the problem. The real problem is underinvestment, disorganization, and a government culture that treats accountability as the irritant instead of the point.
Expect AI-read public records, sharp commentary, and one public official’s bad Outlook decision becoming very public indeed.
Transcript + Source Docs:
Get the full hyperlinked transcript and all documents referenced in this episode:
thepublicrecordsofficer.com
Sign up for updates:
Join our mailing list for future episodes and investigations
thepublicrecordsofficer.com
Support the show:
We’re powered by public records and public support. Buy us a coffee https://coff.ee/thepublicrecordsofficer
About WashCOG:
The Washington Coalition for Open Government (WashCOG) fights for transparency and accountability in Washington State. Learn more:
washcog.org
Tip of the hat to the musicians who created the music used on the show: Alex Grohl, Ian Post, Jakub Pietras, lumine wave, Roberto Pravo, Solis, ...
Ep. 16 No Legitimate Concern
[AO VO] (0:00 - 0:31)
Before we start, a quick heads up. Some of the voices you'll hear reading documents in this podcast are AI-generated, but the words are real. They come straight from public records, produced by real people inside government.
Further, if you're a public employee who's been asked to bend the rules, or if you've seen something that just doesn't sit right, we want to hear from you, confidentially, off the record. Your identity stays with us. You can reach out to us at contact at thepublicrecordsofficer.com.
[Nixon] (0:33 - 1:01)
What you're about to hear is an AI-generated reading of an email sent by the Washington State Office of Financial Management's public records officer, Tina Limoth, to OFM's legal affairs counsel, Nathan Sherrard, on November 13th, 2025. Her email is in response to Sherrard's message that he was going to submit thoughts to the Attorney General's office about the AG's review and update of the Attorney General's model rules for public disclosure.
[AI VO – Lymath Email] (1:02 - 2:13)
I have some ideas about this, namely the requests we get from West and Nixon, and how those set us up for litigation and take up so much of our time when we are trying to just do our job slash due diligence, to serve the requesters who want real valid information, not just seeking to sue us, trying to trip us up instead of respecting the work that we try to do for legitimate requests. That is huge for us. They are taking away from taxpayer money and our time with their requests and intend to sue us with no legitimate concern.
I wish there could be something to tighten and restrict those particular types of requests. I had heard a few people testify about that. The volume of requests that we are trying to process in a timely manner.
The nature of the requests and how much time it takes for an agency department to stop their daily work to process a request. We are doing our due diligence. Perhaps give us more money to support public records divisions and add some more staff to support our quest for transparency within more reasonable time frames.
We can chat sometime Monday before we submit that stuff. But there are my major concerns. The PRA needs to change to protect us workers from those above so that we can really get our work done.
[Nixon] (2:14 - 2:53)
This email was sent to me by an anonymous source. So many red flags in this one short email. It begs a few questions.
What exactly was OFM working on when Tina Limoth decided to call out Arthur West and me by name? What request of mine apparently triggered Limoth to refer to it as no legitimate concern? When Limoth talks about wanting to tighten and restrict those particular types of requests, which kind of requests is she responding to exactly?
These questions, to which I will give you answers soon, matter. Because if you're going to complain that certain named requesters are trying to trip us up, and if you're going to suggest there ought to be some way to
tighten and restrict those particular types of requests,
[Nixon] (2:58 - 3:18)
and also accuse those requesters of submitting requests regarding
no legitimate concern
[Nixon]
then the public deserves to know what kind of requests had you so flustered in the first place, right? Well, hold on tight.
I'm going to tell you all about it and explain why the OFM public records officer should probably rethink her woefully thought out grievances.
[AI VO] (3:21 - 3:31)
You're listening to the Public Records Officer podcast, where we fight for your right to know. Now, here's your host, Jamie Nixon.
[Nixon]
(3:39 - 5:53)
Hello and welcome. This is the Public Records Officer podcast. I am your host, Jamie Nixon.
Let's talk today about what Tina Limoth, the Public Records Officer at the Office of Financial Management, or OFM, was actually upset about when she decided to put Arthur West and me in writing as the kind of requesters who were, in her telling, trying to trip us up, instead of making legitimate requests. Because context matters, my friends. Now, if OFM were processing some ridiculous request about office gossip, fantasy football brackets, or Ferguson's favorite castle recipe, maybe you could at least understand the emotional temptation to complain about it.
Still unprofessional, still dumb to put it in an email, but at least we'd know what the complaint was about. But that's not what was happening here. The request OFM was working on concerned one of the most important public records issues I've been investigating in Washington state government, the 2020 mass deletion of Microsoft Teams chat data in the state's shared tenant.
In June 2020, roughly 1.5 terabytes of chat data was gone. This is the first summer of COVID when state government, like the rest of the world, had been shoved into remote work and digital communication was going at warp speed. Summer 2020 was not a sleepy time for government communication.
It was not an era of handwritten memos and fun little hallway chats by the water cooler. This was the first summer of COVID. People were working from home, Teams, email chat, remote coordination, quick digital decision making.
That was the bloodstream of public work at that time. If you lose 1.5 terabytes of Teams chat data in that moment, you're not losing some trivial side chatter. You're potentially losing a huge volume of day-to-day public business.
To make this request even more public interest-oriented, it was this loss of data that made WaTech aware of the under the hood functionality issues regarding the retention of Teams chats within their tenant. It is essentially the precipitating event that leads us to the seven-day automatic destruction of Teams chats or public records, which I've highlighted in this show since episode one.
[Cuoio (WaTech)] (5:53 - 5:54)
Get it gone.
[Nixon] (5:55 - 6:28)
That is the request that OFM was dealing with when Ms. Lymath decided the real problem was me and Arthur West. Not the loss of records. Not the failure of retention systems.
Not the lack of investment in modern records infrastructure. Not the fact that government was apparently operating in a way that allowed one agency's short retention settings to help determine the fate of another agency's communications inside a shared environment. No, no, no.
The problem, according to this mindset, is the people asking questions about that stuff.
[Rose (SAO)] (6:28 - 6:31)
That's a request for information and you don't have to answer those questions.
[Nixon] (6:31 - 7:17)
That should tell you a lot about the culture that is all too pervasive within Washington state government towards the PRA and the obligations it places on the state workforce. It tells you how some people in government still think about transparency. They love the word, but they hate the obligation.
They love saying they support openness. They love press releases about accountability. They love transparency week, sunshine week, which we are in right now.
And every other week where they can pat themselves on the back and post a nice little statement about democracy and how they're defending it. But when an actual requester starts pulling on the threads that expose systemic failure, suddenly transparency becomes inconvenient, burdensome, excessive, or somehow unfair.
[Cuoio (WaTech)] (7:18 - 7:18)
Get it gone.
[Nixon] (7:20 - 7:40)
And that's where Lymath's email becomes more than just rude. It becomes revealing. And that email, she doesn't just complain about workload.
She doesn't just say the office is overwhelmed or under-resourced. She specifically calls out West and Nixon. She contrasts us against
legitimate requests.
[Nixon] (7:40 - 7:49)
She complains about our
intent to sue us with no legitimate concern
[Nixon]
and says she wishes there were ways to
tighten and restrict those particular types of requests.
[Nixon] (7:49 - 15:00)
This is not neutral language. It is not professional language. And frankly, that is not the language of somebody who understands that government transparency functions as a core democratic obligation.
That is the language of somebody who decided some requesters count and others do not. This matters because once an agency starts mentally sorting the public into legitimate and illegitimate users of the Public Records Act, the whole thing starts to rot from the inside out. Now, let me be very clear about something.
Ms. Lymath, if you're not aware of this, please listen carefully. Requesters do not have to prove that they are morally worthy to use the Public Records Act. You do not have to submit a little essay titled, Why I Deserve Transparency and Why I Deserve These Records.
You do not need to demonstrate pure motives, civic sainthood, or a complete lack of irritation toward the government. The law exists because public records belong to the public, full stop. But even if we entertained Ms. Lymath's framing for a moment, even if we accepted her challenge and asked, was this request legitimate?
Was it in the public interest? The answer is still yes, overwhelmingly and obviously yes. A major loss of government communication records during a remote work emergency period is obviously a matter of public importance.
It goes to records retention, legal holds, open government compliance, operational decision-making, and the basic question of whether public agencies are preserving the business of the people or not. That is a textbook public records issue.
In 2024, the Washington Coalition for Open Government published a report entitled Your Right to Know.
It's useful and instructive here, I think, to bring it up because it blows up this tired claim that the requesters are the problem. They are not. WashCOG's report points to systemic failures, agencies that are disorganized, undertrained, underfunded, and poorly structured for records work.
It notes that public records compliance is a core public service and should be funded like one, not treated like some optional burden stapled onto real government work. If records officers are overwhelmed, the answer is not to limit transparency. The answer is leadership, investment, staffing, better systems, better retention governance, better training, software, priorities.
The answer is most certainly not how do we tighten and restrict those particular types of requests. Reform in this area cannot equal less transparency, period. And if that is what you are proposing, you are on the wrong track.
And it is especially rich in this case because the request that issue was not some random annoyance. It was about a deletion event that should have sent shockwaves to the top levels of state government. If a mass loss of communications during COVID does not qualify as a matter worth documenting, escalating, and examining, then what the hell does?
One of the things that's become apparent to me in looking into this matter from 2020, there seems to be so little communication between the agencies you would think there'd be communication between on this matter, especially between the governor's office, WaTech, and the attorney general's office. If you're a normal person, and I realize that as a public records podcaster, I'm probably not that, you would assume an event like this would generate all kinds of high-level concern. Instead, the trail is almost non-existent.
And then, top of that, you find public officials acting like the real issue is not the missing records, but the requester's stubborn enough to notice and ask about it. Asking accountability questions like what happened, who knew what, and when, in a functioning transparency culture, these questions would not be considered some kind of harassment or burden. That's the inversion here.
That's the scam. It's a sleight of hand, right? The government under-invests in record systems, allows conditions where major failures can happen.
And then when people use the law to investigate those failures, some officials act like those people are the stressor on the system. No. The stressor is corrosive leadership, a lack of deterrent-centered enforcement.
The stressor is a political class giving lip service to transparency with no meaningful budgetary or structural commitment to it. The stressor is a culture that still treats records work like a nuisance instead of a pillar of democratic governance. And I also have to say this because I mean it.
I support public records officers who are trying to do the job right. There are good PROs in the state. I've talked about them on the show.
There are people doing honest work in a crappy system. There are records professionals who understand that the public is not the enemy and that accountability is not some kind of personal attack. And those people deserve more support than they're getting.
What they do not deserve is leadership that leaves them under-resourced, then quietly encourages them to resent the public for it. Because once you start blaming the requester, you let the people with actual power to change the system off the hook. And that to me is one of the most important things about this email.
It isn't just some nasty gram. It's an example of misdirected anger. It tells us where the frustration is being aimed and it is aimed in the wrong direction.
If you're a public official angry about the burden of records compliance, your complaint should be upstairs to agency leadership, to lawmakers, to the people who never seem to find the money for modern retention tools, proper staffing, or serious training... Not at the citizens trying to use the law in the way that it was intended to be used. And as an aside, if you truly believe someone is out to litigate, maybe don't hand them an email that makes you sound biased, dismissive, and unprofessional.
That seems like an odd tactical choice. Now I'm no grandmaster of bureaucratic chess, but putting potentially discriminatory sounding hostility toward named requesters in writing does not strike me as a powerful long-term move.
Don't poke the bear, Tina.
Especially not in Outlook.
You have now learned what other agencies have learned that these emails have a way of becoming very public. Because public records are funny that way, right?
They have a habit of wandering back into the light. And in this case, what wandered back into the light was not just one bad email. It was an entire mindset.
A mindset that says some requesters are legitimate and some are trouble. Some are the public. Some are a burden.
Some deserve service and some deserve suspicion. That mindset is poison to transparency. The problem is not the requester asking about 1.5 terabytes of missing public communications during COVID.
The problem is a government culture that still too often treats accountability as the irritant instead of the point.
[AI VO] (15:01 - 16:43)
That's it for this episode of the Public Records Officer podcast. A quick note before you go. Some of the voices you heard on the show weren't from real people.
Some were totally synthetic, AI generated to read from public records and legal depositions that are, yep, public. You'll also hear real human voices like live audio from state meetings. And the occasional passionate rant from the show's gorgeous host.
Every episode has a full transcript at thepublicrecordsofficer.com. It breaks down which clips came from humans and which came from our robot friends. Think of it like liner notes for digital democracy.
You'll also find links to the original documents and recordings we talked about, hosted on Google Drive, free and public. So if you want to fact check us, go nuts. That's kind of the point.
If this show got you fired up or even just mildly interested, check out the Washington Coalition for Open Government. They're a non-profit that fights for transparency and they've got resources if you want to help or just learn more. And hey, if you work for the state and you've seen one too many messages accidentally disappear, we'd love to hear from you, confidentially, unless you want to be famous.
The Public Records Officer podcast is a creation of Nixon and Daughter Productions, powered by good coffee, better whiskey, a microphone, a legal tab, and the apparent misguided belief that government should actually be accountable to people, which is adorable, really. Thanks for listening. See you next time.
And remember, you're not paranoid. They really did delete it.