Shadows of Transparency: Signaling Transparency-Impeding Behavior Using Public Data

Imagine the government as a giant, glass-walled office building. The idea behind "Freedom of Information" (FOI) laws is that the glass should be perfectly clear, allowing citizens to look inside and see exactly what the people in charge are doing. This transparency is supposed to keep the government honest.

However, the authors of this paper argue that just because the building has glass walls doesn't mean you can actually see what's happening inside. Sometimes, the people inside the building use clever tricks to make the glass look clear while actually blurring the view, fogging it up, or hiding the important documents behind a curtain.

This paper is about building a "Smoke Detector" for government transparency. Instead of waiting for someone to complain that they can't see inside, the researchers created a system that uses the government's own public data to spot these "fogging" tricks automatically.

Here is how they did it, broken down into simple concepts:

1. The Problem: The "Formal" vs. The "Real"

The government follows the rules on paper. They answer your questions and send you files. But the way they send those files can make them useless.

• The Analogy: Imagine you ask a chef for a recipe. They send you a photo of a handwritten note on a crumpled napkin that is covered in coffee stains. Technically, they gave you the recipe (compliance), but you can't read it (no real transparency).
• The Paper's Claim: Most studies only check if the government answered the request. This paper looks at how they answered.

2. The Nine "Fogging" Tricks

The researchers looked at past studies and identified nine common ways governments subtly block transparency. Think of these as nine different ways to fog up the window:

1. Obstructive Formatting: Sending files as scanned images (like a photo of a document) instead of editable text. It's like sending a picture of a menu instead of the text; you can't search for the word "soup."
2. Excessive Redaction: Blacking out so much text that the remaining words make no sense. It's like a "Where's Waldo?" book where someone has blacked out the whole page except for Waldo's hat.
3. Catch-All Exemption: Using a vague legal excuse (like "state security") to hide almost anything, even when it's not actually secret.
4. Narrow Reading: Pretending your question is very specific so they only have to show you one tiny, useless page.
5. Overbroad Reading: Pretending your question is huge so they dump thousands of irrelevant pages on you, burying the good stuff in the noise.
6. Stale Release: Waiting so long to send the answer that the news is already old and useless.
7. Renamed Units: Changing the name of a department or a file type after you ask about it, so a new search finds nothing.
8. Document Suppression: Stopping the creation of certain records entirely after they were exposed once.
9. Reclassification: Suddenly labeling a document as "Top Secret" just because you asked to see it.

3. The Solution: The "Digital Detective"

The researchers realized that when governments use these tricks, they leave digital footprints in the public data. They built a system to measure six of these nine tricks using a massive dataset of over 15,000 Dutch government requests.

They created six "Smoke Alarms" (Indicators):

• The "Machine-Readability" Alarm: Checks if files are text or just pictures. (Did they send a photo of a napkin?)
• The "Blackout" Alarm: Measures how much of the text is covered in black ink.
• The "Vague Excuse" Alarm: Tracks how often they use the "State Security" excuse.
• The "Tiny Answer" Alarm: Counts how many requests get a tiny, 1-2 page response (Narrow Reading).
• The "Data Dump" Alarm: Counts how many requests get a massive 600+ page response (Overbroad Reading).
• The "Slow Motion" Alarm: Measures how many days it takes to get an answer.

4. What They Found

They tested these alarms on different Dutch government ministries (like Health, Defense, Finance).

• The Results: The alarms went off differently for different ministries.
  • Some ministries were great at sending readable files but terrible at waiting too long to answer.
  • One ministry (Health) was flagged for using a lot of "blackouts" and vague excuses.
  • Another (Defense) had a history of sending files as unreadable images, though they improved over time.
• The Key Insight: You can't judge a single ministry in isolation. The power of this tool is comparison. It's like a speedometer: seeing that one car is going 200 mph and another is going 50 mph tells you something important, even if you don't know exactly why.

5. Did It Work? (The Expert Check)

The researchers didn't just trust their own math. They showed their "Smoke Alarms" to three groups of experts:

1. Journalists (who investigate the government).
2. Researchers (who study transparency).
3. Civil Servants (government workers).

The Verdict:

• Journalists loved it. They said, "This helps us decide which government department to investigate first."
• Civil Servants said, "This is a good mirror. It shows us why one department is doing things differently than another."
• Researchers agreed it helps spot patterns over time.

The Catch: The experts warned that these alarms are signals, not proof. A high "blackout" score doesn't prove a ministry is corrupt; it just means, "Hey, look here, something is weird, let's investigate." It raises questions rather than pointing fingers.

Summary

This paper introduces a new way to watch the government. Instead of just checking if they answered the door, this tool checks how they handed you the package. By turning messy public data into simple charts, it helps citizens, journalists, and watchdogs spot when the government is trying to fog up the window, allowing for better comparisons and smarter investigations.