About
About Oversight Archive
Oversight Archive is an independent, anonymous group of people working together to shed light on how public agencies follow their own rules. The City of Twin Falls has our attention for now. Members gather official records through public records requests, public meetings and agencies' own postings, read them against the rules officials must follow, and publish what they show. Every claim links to the record and the page it comes from.
Why we do this
Corruption happens in both major parties and at every level of government, from the U.S. Senate to city hall. Most of it is smaller than the headlines: a raise approved without a vote, a perk extended by memo, a records request slow-walked until people give up. Federal convictions of local officials have fallen by half in a decade, and thousands of local newspapers have closed, so more depends on residents reading the records themselves.
The full story has the cases, the research and the sources.
How we work
- Official records only. Records released under public records laws, records of public meetings, documents the agency publishes itself, and laws and official guidance. Each record's page says which, with the date and where we got it.
- Tips steer, records decide. Tips and accounts we receive shape which records we ask for. They are never published as fact.
- Public office, not private lives. No home addresses, family details or medical information. We redact what agencies forgot to.
- Requesters stay private. We remove every records requester's name and contact details from the records we post, the same way for everyone. City officials and staff keep their names: what they did in public office is the point.
- We show the work. Every finding is graded, cites the record and page, names the rule at stake, and lists the innocent explanations we checked.
- Nothing altered. Every file carries a SHA-256 fingerprint. We remove only document properties such as author fields.
- No verdicts. Whether a law was broken is for prosecutors, courts and ethics bodies. A record we don't have yet could change a finding either way, and if one does we update it openly. Nothing here is an accusation against any person.
- Machine text is labeled. Transcripts and scanned-document text are made by software and contain errors. The recording or document is the record, and every citation links to it.
Why it matters: the labels
Every finding says plainly who bears the cost, using these labels:
- Public money
- Money paid outside the rules, or spent without the approvals the rules require. It comes out of the same budget as police, streets, parks and water.
- Self-dealing
- Officials setting or approving their own benefits, or benefits for the people who review them. Without an independent check, nothing stops it from growing.
- Conflict of interest
- An official acting on matters that affect their own business or finances without disclosing it, so residents can't tell whether the decision was made on the merits.
- Unequal treatment
- Rules applied to some people and not others: employees held to limits their bosses ignore, or requesters treated differently depending on what they ask for. Rules that depend on rank or favor stop being rules.
- Hidden decisions
- Decisions made without a public vote, a proper notice or minutes. The public can't question, challenge or reverse what it never saw.
- Financial transparency
- Payment lists, card statements, budgets and financial reports kept out of public view. Residents can see that money was approved, but not what it bought or who spent it.
- Records access
- Delays, gaps and denials that keep public records from the public. They don't just frustrate one requester; they keep information from everyone.
- Wasted time
- Hours spent chasing deadlines, appealing denials and refiling requests: residents' time, and the staff time taxpayers pay for.
How to read a finding
Each finding carries three separate labels. They answer different questions, so read them together.
- How firm it is
- The grade. Documented means the agency's own records show it directly. Indicated means consistent records strongly suggest it, but a key record is still missing. Open question means a gap that needs records before anyone draws a conclusion.
- Rule at stake
- What kind of rule the finding involves, from highest to lowest: federal law, state law (such as the Open Meeting Law or the Public Records Act), state ethics law (conflicts of interest and the use of public office or funds for personal benefit), and City code, policy or contract (the City Code, which collects the City's ordinances; resolutions; the employee handbook; financial policies; and employment agreements). Possibly means the records point that way but a key fact isn't established yet. Open question and Context mean no rule breach is claimed. Findings are listed with the highest level first.
- Why it matters
- The labels above, under "Why it matters": who bears the cost.
The three don't move together. A documented breach of a City policy can cost taxpayers more than a possible breach of a state law, and the level of a rule says nothing about anyone's intent. The ranking orders findings by the kind of rule involved; it isn't a judgment of how much anyone is to blame.
Why we're anonymous
So the records carry the argument, not the people who found them. Anonymity also lets us protect anyone who sends us records or accounts, whoever they are.
Join us
Holding government to its own rules shouldn't depend on any one person. If you've filed a public records request with any government (city, county, school district, special district or state agency), send us what you asked for, what came back, and the emails in between. No name is needed. If you'd rather not file yourself, every jurisdiction's page lists the records we're still seeking, with wording you can copy.
Work in government and seen something? You can tell us without telling us who you are. The secure tip line gives you a receipt code so you can answer our questions anonymously.
Submit records Speak up anonymously See the records requests
Verify a file
Every posted file has a SHA-256 fingerprint on its record page and in SHA256SUMS.txt. To check a file you downloaded, run the command for your computer, putting in the folder and file name where you saved it:
Windows (open PowerShell from the Start menu): Get-FileHash "<folder>\<file name>" -Algorithm SHA256 Example: EX-A01.pdf saved in your Downloads folder Get-FileHash "$HOME\Downloads\EX-A01.pdf" -Algorithm SHA256 macOS or Linux (open Terminal): shasum -a 256 "<folder>/<file name>" Example: EX-A01.pdf saved in your Downloads folder shasum -a 256 ~/Downloads/EX-A01.pdf
Shortcut: instead of typing the path, drag the file into the window and its full path fills in. On Windows, type Get-FileHash (with a space), drag the file in, then type -Algorithm SHA256 and press Enter. On a Mac, type shasum -a 256 (with a space), drag the file in, and press Enter.
The command prints a long string of letters and numbers. If it matches the fingerprint on the record page (capital or small letters don't matter), you have exactly the file we posted.
Corrections
If a record shows we got something wrong, or a record we couldn't find exists, we want it. Send it through the submission form. Corrections are made openly: the finding is updated, the change is dated, and the earlier version stays on the timeline.
Privacy
This site sets no cookies, runs no analytics and loads nothing from other servers. Search runs entirely in your browser. If you switch between the light and dark themes, that choice is remembered in your own browser and never sent to us.