Transparency Mechanisms, and a PIO Under Pressure

The full machinery of information sharing beyond RTI, and a case in which a Public Information Officer is pressed to suppress what the file plainly shows.

The wider machinery

RTI is the most discussed instrument and not the only one. A complete answer places it among the others.

Formal mechanisms include proactive disclosure under the Act, citizen charters as examined in Chapter 19, annual reports and audited accounts, questions answered in the legislature, and the reports of the Comptroller and Auditor General, which are laid before the legislature and become public documents.

Digital mechanisms include departmental portals, online status tracking, open data platforms, e-procurement systems that publish tenders and awards, and centralised grievance systems through which a citizen can file and follow a complaint.

Informal mechanisms include press briefings, official social media, community meetings and public broadcasting. These reach further than formal channels and carry a risk worth naming: information released informally is not authoritative, can be selective, and creates no record, so it should supplement rather than replace formal disclosure.

Why the portal is not the same as transparency

A caution that recurs throughout this book. Publishing large volumes of material does not by itself create transparency, and can defeat it.

Information buried in an unsearchable file, published in a format that cannot be analysed, released after the moment it could have influenced anything, or scattered across pages nobody can navigate, satisfies a formality and informs nobody. The test is not whether the information was published but whether a reasonably diligent citizen could find, understand and use it.

A case: the PIO under pressure

An officer serving as Public Information Officer receives a request seeking records of expenditure on a local infrastructure project. The file shows serious irregularities: payments for work not verifiably done, and approvals granted out of sequence. Officers who would be implicated, and a contractor with local influence, press her to deny the request or to release a partial version omitting the relevant papers. She is told, without anything being put in writing, that her next posting depends on her judgement here.

Classify first, as Chapter 15 directed. This is not a dilemma. There is no competing good on the other side; the pressure asks her to breach a statutory duty to protect people from the consequences of their own conduct. The difficulty is entirely in the cost of doing right, which makes it a temptation with a price attached.

Working the options

Denying the request outright would require citing an exemption that does not apply, which is a false statement in a statutory capacity and exposes her to penalty on appeal, with the added feature that the Commission’s order would make the concealment public.

Releasing partial information while omitting the material papers is the most tempting course because it looks like compliance. It is also the most dangerous, since it is knowingly misleading, and the omission will be apparent to anyone who obtains the file later. Severability permits withholding genuinely exempt portions; it does not permit removing the inconvenient ones.

Delaying until the deemed-refusal period expires is a refusal by another route, and is treated as such on appeal.

The correct course is to supply the information the Act requires, applying exemptions only where they genuinely apply and stating which have been applied and why, so that any withholding is visible and appealable rather than concealed.

Doing it defensibly

Method matters as much as the decision, and Chapter 18 supplied the pattern. Depersonalise the response: the Act requires disclosure and she is not able to depart from it, which is a statement about the statute rather than about anyone’s conduct. Put the position in writing to her superior before releasing, so the matter becomes institutional rather than a private stand.

Record the approaches made to her, contemporaneously and factually. Where an inducement or threat is explicit, report it to the appropriate vigilance authority, since the character of the matter has changed. And release within the statutory period, because delay would convert a defensible position into a breach.

Two observations complete the answer. Her statutory role protects her: a PIO acting within the Act is on considerably stronger ground than an officer exercising discretion, and the personal penalty provision cuts in her favour, since it is refusal rather than disclosure that attracts sanction. And the systemic point, which Chapter 15 requires: the irregularities were discoverable only because someone asked, which is an argument for proactive publication of expenditure and measurement records so that detection does not depend on a citizen happening to file a request.

Chapter 23 turns to accountability itself, the mechanism that decides whether anything follows from what disclosure reveals.

Information sharing within government

The chapter has treated disclosure to citizens, and the syllabus phrase covers something further: sharing between parts of the administration. Failures here are less visible and often more consequential.

Departments hold data that other departments need and frequently do not share, through legal uncertainty, protectiveness about a resource they regard as theirs, or simple incompatibility of systems. The citizen then supplies the same information repeatedly, and the state acts on partial pictures, verifying separately what it already knows collectively.

Two cautions apply to the obvious remedy. Convenience is not a lawful basis for sharing personal data, and information collected for one purpose should not migrate to another without a proper basis, which is the purpose-limitation principle Chapter 17 applied to firms and which binds the state at least as strongly. And the more data is consolidated, the greater the harm from a single breach, so security obligations rise with integration.

Transparency as a habit, not an event

A final framing worth carrying into any answer. The officers who handle disclosure best are not those who comply most carefully with requests; they are those who work as though the file will be read.

That habit produces recorded reasons that make sense to a stranger, decisions whose basis can be stated, and files that do not need to be curated before release because nothing in them requires concealment. It is also, as Chapter 16 observed, a quality control on the decision itself, since reasoning written for an outside reader is reasoning that has been tested.

The practical instruction is therefore simple and demanding: decide every matter as though the file were already public. An officer who does this has very little to fear from any information request, and an administration built of such officers would need the Act far less than one that resists it.