Transparency Impact Review¶

A periodic effectiveness review — instantiates Transparency for Accountability

Periodically asks whether all the disclosure is actually producing accountability, and at what burden, rather than just accumulating published volume.

A Transparency Impact Review periodically steps back from all the disclosure machinery and asks the one question that ultimately matters: is any of this actually producing accountability, and at what cost? It is the meta-mechanism — it produces no disclosure of its own; it evaluates whether the decision logs, reports, dashboards, channels, and registers are read, understood, used to ask real questions, and followed by correction — and weighs that against the burden they impose. Its distinguishing role is turning transparency from an output measured in volume into an outcome measured against its purpose, catching the gap between "we published a great deal" and "anyone was held to account."

Example¶

An agency that spent two years building an award-winning open-data portal runs an impact review. It finds impressive volume — thousands of datasets, millions of downloads — but almost no line from the data to any consequential question, correction, or changed decision; meanwhile the disclosure work consumes a real chunk of staff time and the plain-language summaries nobody asked for go unread. The review's finding isn't "publish more" but "publish differently": retire the datasets nobody uses, redirect the freed effort to the two disclosures that actually drove accountability (the on-time-performance record riders cite, the contract log a watchdog uses), and add a challenge channel where the data raises questions. It measures accountability produced, not pages posted — the antidote to open-washing.^[1]

How it works¶

The distinguishing move is that it evaluates the disclosure system against its stated purpose and its burden, on a cadence. It traces whether disclosures reach and inform an audience, whether questions and challenges actually flow and get answered, and whether corrections result — then sets that against the cost and any harms (privacy load, noise, gaming). Its output is a re-allocation: what to keep, cut, simplify, or add, judged by accountability yield rather than by volume.

Tuning parameters¶

Outcome metrics — what counts as accountability produced (questions asked, errors corrected, decisions changed) vs. proxy volume (views, datasets). Outcome metrics are honest but harder to measure.
Burden accounting — how fully the costs (staff effort, privacy exposure, noise) are counted against the benefits. Fuller accounting resists disclosure-for-its-own-sake.
Review cadence — how often the system is reassessed. Frequent catches drift; infrequent is cheaper and less disruptive.
Independence — whether reviewers are the people who run the disclosures. Independent review is more honest, but costlier and more threatening.
Scope — one mechanism at a time vs. the whole disclosure portfolio. Portfolio scope catches redundancy and gaps; narrow scope is more tractable.

When it helps, and when it misleads¶

Its strength is that it is the corrective for transparency that has become decorative — distinguishing disclosure that changes outcomes from disclosure that merely accumulates, and freeing effort spent on unread volume.

Its failure mode is that the review is easily run backwards — commissioned to certify an existing transparency program rather than test it, cherry-picking the flattering metric (downloads, awards) over the outcome one. And measuring the wrong thing entrenches the wrong thing: count volume and you get more volume. The discipline is to fix the outcome metrics and the purpose before the review, count burden honestly, and give the review enough independence that it can conclude "cut this," not just "do more."

How it implements the components¶

transparency_effectiveness_and_burden_review — its entire substance: assessing whether the disclosure produces accountability and whether its benefits justify its costs.
transparency_purpose — it makes the declared purpose the yardstick, judging the system against what the disclosure was for rather than against how much was published.

It produces none of the disclosures it assesses — the Public Decision Log, Plain-Language Transparency Report, dashboards, channels, and registers are its subject, not its output — and it does not grant reviewers their access (Independent Oversight Portal).

Instantiates: Transparency for Accountability — it closes the loop, checking whether the disclosure chain actually yields accountability.
Consumes: the outputs of the other mechanisms, which are the evidence it evaluates.
Sibling mechanisms: Plain-Language Transparency Report · Public Decision Log · Process Status Dashboard · Public Comment & Question Channel · Rule & Criteria Register · Redaction & Withholding Ledger · Independent Oversight Portal

References¶

[1] "Open-washing" (by analogy to greenwashing) is the practice of using the appearance of openness or transparency for reputational credit without the substance — publishing volume that produces no real accountability. It is precisely the failure this review exists to detect. ↩