Story Time
The following story is a work of fiction designed to illustrate common scenarios regarding public records requests.
In the small, close-knit community of Willow Creek, Mike was a retired accountant who, seeking a quiet way to stay engaged with his community, volunteered for the non-voting, advisory role on the local Road District’s citizen oversight committee. His reputation in town was that of a numbers man, meticulous to a fault. The Willow Creek Road District operated on a modest budget, funded by local property taxes, responsible only for maintaining three paved roads and about a dozen miles of gravel surface.
Mike attended every meeting, listening patiently as the three elected trustees—Martha (the chair), Bill, and Greg—debated gravel costs and snowplow schedules. Mostly, the board operated smoothly. But one evening, while reviewing the summary financial report provided during the meeting, Mike noticed a consistent line item: “Vendor Payment: $4,200” every quarter for “Consulting Services.”
It struck him as odd. Willow Creek was small. What consultants were they hiring?
At the next meeting, during the public comment section, Mike raised his hand. “Martha, Bill, Greg,” he began, “Regarding the Vendor Payments for consulting services, I’d like to exercise my right as a resident and a committee member to review the supporting documentation for these expenses.”
Martha, a woman who prized efficiency and disliked deviations from the agenda, sighed slightly. “Mike, the funds are accounted for in the summary sheet we provide every quarter. The total is correct.”
“I don’t doubt the total is correct, Martha,” Mike replied politely. “I just want to see the actual invoices, contracts, perhaps canceled checks, that justify those payments. Standard accounting procedure.”
Martha shared a look with Bill, the treasurer, who shrugged subtly. “We can provide you with the necessary information, Mike,” Martha said, trying to diffuse the situation. “We’ll have it ready next week.”
A week later, Mike stopped by the district’s small office, a room shared with the town clerk. The clerk handed him a single sheet of paper. It was a simple printout on plain white printer paper, clearly created on a basic word processing program. It had a date, the name of a vendor (“Roadway Solutions LLC”), a dollar amount, and a line that read, “For services rendered.” There was no letterhead, no invoice number, no signature, no description of the actual services beyond the generic title.
Mike held the paper up to the light, confused. “This isn’t an invoice. This is just a typed statement saying a bill was paid. Where’s the actual bill from the vendor? Where’s the proof the work was done?”
The clerk, a kind woman who was just following orders, nervously pointed to a seal stamped at the bottom. “That’s… that’s what the board gave me to give you. They said it verifies the expense.”
Mike wasn’t satisfied. In his professional life, real financial documentation was a robust ecosystem of verification.
Real records, he knew, looked very different:
- A formal Invoice: A legitimate invoice would be on the vendor’s professional letterhead, contain a unique invoice number, the date of service, a detailed breakdown of the work performed (e.g., “Consultation regarding culvert replacement options, 10 hours @ $250/hr”), the vendor’s tax ID, and contact information.
- A Signed Contract or Scope of Work: For a recurring $4,200 payment, there should be a formal contract signed by both the vendor and the district chair detailing the agreement’s terms and deliverables.
- Proof of Payment: A canceled check image from the district’s bank statement, showing the endorsement by the vendor, or a bank transfer confirmation receipt with a transaction ID.
- Deliverables: If they were consulting on roadwork, there should be physical reports, engineering studies, or meeting minutes resulting from that consultation.
The single sheet of paper the board provided offered none of this. It was fundamentally unverified, a simple assertion of fact with zero supporting evidence.
Mike attended the next board meeting, the single piece of paper in hand. “Martha, this document you provided is insufficient,” he stated, maintaining his calm, professional demeanor. “It doesn’t provide the detail required for proper oversight. I need the actual invoices and contracts.”
Bill, the treasurer, frowned. “We’ve given you the information, Mike. You have the amount and who it went to. We don’t appreciate you questioning our integrity.”
“It’s not about integrity, Bill, it’s about transparency and accountability to the taxpayers,” Mike responded firmly. “Public funds require public verification.”
“We consider the matter closed,” Martha declared, banging her gavel lightly. “The paperwork you received is what we are providing. The district considers that sufficient disclosure.”
Mike persisted. He sent formal letters citing state public records laws. His requests were met with silence, or a repeated copy of the same single sheet of paper. The board stonewalled him, grew defensive, and eventually told him they would no longer entertain his requests during public meetings, claiming harassment.
Frustrated but committed to the principle, Mike realized he was at an impasse. The informal channels were exhausted. He had to escalate.
He found a lawyer willing to take on government transparency cases. The lawyer filed a formal lawsuit against the Willow Creek Road District for violating the state’s Open Records Act.
The lawsuit turned the quiet town upside down. Neighbors took sides. The board members felt personally attacked, while many residents started asking Mike questions in the grocery store line, curious about what the board was trying to hide.
The legal process was slow and expensive for the small district, which had to hire specialized legal counsel using taxpayer money to fight a taxpayer’s request. During the discovery phase of the lawsuit, the court ordered the Road District to produce all relevant documentation regarding “Roadway Solutions LLC” for the past two years.
When the documents were finally submitted to the court and Mike’s lawyer, they were eye-opening. There were no detailed invoices or reports because “Roadway Solutions LLC” was a P.O. Box owned by Greg’s cousin, and the consulting work was non-existent. The quarterly payments were being funneled for personal use. The typed paper provided to Mike was simply a forgery created to deflect scrutiny.
The lawsuit didn’t just force transparency; it uncovered embezzlement. The three board members faced criminal charges. Martha, Bill, and Greg resigned in disgrace. A special election was called.
Mike didn’t run for a board seat. He was too old for the politics. But the new board members, keenly aware of the scandal that brought them into office, made sure their first act was to adopt a robust, transparent accounting system, ensuring that every single invoice, contract, and canceled check was easily accessible online for any resident to see.
It was an expensive, contentious way to get a look at the books, but in the end, the simple, unverified piece of paper couldn’t withstand the truth of real records, and Willow Creek learned a hard lesson about the importance of accountability.