Working the Public Records Loop
The first thing you learn is that most state-level corruption hides in plain sight, buried under hundreds of vendor contracts and procurement emails that are technically public but functionally inaccessible. I spent three weeks last year tracking a single $2.4 million landscaping contract through a county clerk's office because the FOIA request form was on a PDF that couldn't be copy-pasted from. You read those forms every day. You think they're standard. They aren't. Kevin Landrigan built his career on a method that works well for the kind of state government reporting I deal with, which is to say it's not glamorous and it eats up a lot of your time. The core of it is treating public records as the primary source, not as a supplement. Most reporters I know start with a tip or a leak and then go back and find documents to prove it. Landrigan tends to do the reverse. He builds the case from the ground up by pulling records first, then following whatever trail they create. It's slower in the short term. It tends to produce stories that hold up better when people try to dig into them. Here's how the process actually works when you're sitting at your desk on a Tuesday afternoon.
Starting with the Procurement Trail
State governments run on contracts. If you want to find something untoward, you start with the procurement database. Every state has one, though some make it harder to navigate than others. The Florida system is relatively transparent. Mississippi requires you to wade through multiple portals before you find anything useful. Iowa has their records buried inside a legacy system that still runs on something from the late 1990s. You learn the quirks of each one through repeated exposure. I've found that the best starting point is usually the statewide vendor list, cross-referenced with the contract award dates. Look for patterns where the same company wins contracts repeatedly in different counties or departments. Look for contracts that were awarded without competitive bidding. Those sole-source awards are where the red flags multiply. A sole-source contract isn't automatically suspicious, but when you see three of them to the same company within a twelve-month window across different agencies, you start paying attention.
Reading Between the Contract Lines
The actual contract documents contain more information than most people give them credit for. I'm not talking about the cover page with the dollar amount and the signatures. I mean the exhibits, the amendments, the change orders. A single contract for IT consulting services might have been amended seven times, each amendment pushing the total cost higher. The original bid was $85,000. The final outlay was $340,000. Nobody outside the agency knew those amendments existed because they weren't highlighted in any press release. Change orders are where the money walks. That's the first place I look. If a state agency issues a contract and then files amendments that increase the scope or the budget, you request those amendment documents. The justification for each change should be on file. Sometimes it's thorough. Sometimes it's a single paragraph that says "increased scope due to evolving requirements." That's the kind of language that tells you someone didn't think the original request was going to get questioned.
Get the Full Details
Following the Money Through Meetings
Meeting minutes are another underused tool. I've written about two dozen stories over the years that started because I noticed something in a meeting transcript that didn't get covered anywhere else. A board voted 4-1 on a vendor selection. The one dissenter asked a question about the company's prior relationship with the agency director. The question went unanswered in the minutes. Two months later, I pulled emails through a separate request and found that the vendor's CEO had donated to the director's PAC six weeks before the vote. This is the tedious part. Meeting minutes are often published weeks or months after the actual session. The agenda packets that go with them are a separate request. If you're working on a deadline, this timeline can kill your story before it starts. That's why the Landrigan approach of building from records first matters. You're not racing to publish on a tip. You're building a foundation that you can report from when you're ready.
The Request Process Itself
Public records requests are deceptively complicated. The form might look simple. The actual process involves understanding exemptions, redaction policies, and appeal procedures that vary by state and sometimes by agency. I once requested email correspondence from a state education department and got back a box containing forty-seven pages, all of them heavily redacted. The redactions covered names, dollar amounts, and entire paragraphs. When I appealed, the agency revised the redactions but kept the same structure. The third appeal got me two more pages of unredacted text. That text contained the key detail I needed. Appeals take time. They also create a paper trail that can become part of your story. An agency fighting to keep documents secret is more newsworthy than the documents themselves sometimes. I learned early on that the act of requesting, being denied, and appealing can expose institutional habits that tell you something about the culture you're investigating.
Watching for the Common Mistakes
Beginners in this work tend to make the same errors repeatedly. They request too broadly and get overwhelmed by volume. They request too narrowly and miss the document that would connect everything. They assume that what's online is complete, when in fact many states maintain parallel paper records that never made it into the digital system. They also tend to trust the first response they get. The first response is almost always incomplete. Agencies will give you what they can comfortably hand over before they figure out what you're really looking for. Another mistake is focusing on the wrong level of government. State-level corruption doesn't always stay at the state level. County commissions, school boards, and municipal councils handle money that originates from state allocations. If you're only looking at the governor's office or the state legislature, you're missing entire layers of the spending apparatus.
What This Approach Doesn't Do Well
The records-first method has real limitations. It requires access to functioning public records laws. In states where the legislature has weakened FOIA provisions or where agencies routinely deny requests on vague grounds, this approach hits a wall. I've worked in jurisdictions where a single request could take six months to process and still come back mostly blank. The legal right to request doesn't mean the practical ability to obtain. It also doesn't work for every type of corruption. Wire fraud, election interference, and personal criminal activity don't always leave traces in procurement documents. When you're dealing with those issues, you need sources inside the operation, not just paperwork. The records will fill in the details after you get a tip, but they won't generate the tip for you. The method also demands patience that the news cycle doesn't reward. A story built entirely from public records can take three to six months to develop from initial request to publication. Most editors won't support that kind of timeline for a story that hasn't broken anywhere else. That's a structural problem in modern newsrooms, not a flaw in the method itself, but it's real and it limits how much you can rely on it.
What I Do When the Records Run Dry
When the paper trail hits a dead end, I pivot to public sources that aren't technically records requests. Court dockets, business filings, campaign finance databases, and professional license records all exist outside the FOIA system and often contain information that state agencies would rather keep separate. A business entity search can reveal that a vendor incorporated three months before receiving a contract. A campaign finance report can show a donation from that same vendor to the official who awarded it. These are public sources, but they're not organized in a way that makes correlation easy. You have to do the connecting yourself. The work isn't exciting. It's repetitive, it's slow, and it's full of dead ends. But the people who do it well tend to be the ones who stick with it. The stories that matter most are the ones nobody else is looking for because they don't fit a convenient narrative. They're just numbers in a procurement database that don't add up the way they should.
