How to Ask a Public Authority for the Algorithm Behind a Decision

A licence is refused, a claim is scored, an application is ranked, and the reason given is that the system decided. Asking a public authority for the algorithm behind a decision is not hopeless, but it is far weaker when framed as a demand for the software than when framed as a request for information the Act already covers.
Step 1: Work Out What Actually Exists as Information
Clause (f) of section 2 of the Right to Information Act, 2005 defines information as any material in any form, including records, documents, memos, e-mails, opinions, advices, press releases, circulars, orders, logbooks, contracts, reports, papers, samples, models, data material held in any electronic form and information relating to any private body which can be accessed by a public authority under any other law for the time being in force.
Two words in that definition carry most of the weight here. Models, and data material held in any electronic form. The definition is about material the authority holds, which means the first task is to work out what material exists rather than what the system does.
Step 2: Ask for the Documents, Not for the System
A request for an algorithm invites the answer that none is held in that form. A request for identified documents is harder to answer that way. The useful list is ordinarily: the file approving the adoption of the system, the procurement record, the tender document and the contract, the user manual or standard operating procedure, the criteria or parameters approved by the authority, any internal circular on how outputs are to be used, and any audit or evaluation report.
Each of those is a document rather than a technology, and each either exists or does not. An answer that none exists is itself a useful answer about how the decision was made.
Step 3: Separate the Decision's Own Record From the System's
Two different things are often asked for in one breath. The record of this decision, which is the file, the note, the score and the reasons; and the record of the system that produced it, which is the policy, the parameters and the contract.
Ask for both, separately and in that order. The first is usually less contested, it is often enough for the immediate purpose, and a partial refusal on the second does not delay the first.
Step 4: Expect Clause (d) and Write for It
Clause (d) of sub-section (1) of section 8 exempts information including commercial confidence, trade secrets or intellectual property, the disclosure of which would harm the competitive position of a third party, unless the competent authority is satisfied that larger public interest warrants the disclosure of such information.
Read the limbs separately, because the exemption is not a label. It requires information of that character, and disclosure that would harm the competitive position of a third party, and the absence of a larger public interest. An approved parameter, a standard operating procedure or an evaluation report may be a long way from a trade secret, and saying so in the request itself forces the authority to address the limb rather than cite the clause.
Step 5: Make the Public Interest Case in the Request
Sub-section (2) of section 8 provides that, notwithstanding anything in the Official Secrets Act, 1923 nor any of the exemptions permissible in accordance with sub-section (1), a public authority may allow access to information if public interest in disclosure outweighs the harm to the protected interests.
That provision is a route the authority may take, and it is far more likely to be taken if the case for it is already on the page. The case is strongest when it is concrete: this system decides this class of application, the affected person cannot otherwise know why, and the material sought is the criteria rather than the code.
Step 6: Narrow the Request Before the Authority Narrows It
A broad request invites a broad refusal. Where the concern is one decision or one class of decision, say so, name the period, and name the category of document. A request that can be answered by pulling three identified files will usually be answered.
Where part of a document is genuinely commercial, offer the obvious compromise in the request itself, which is the document with the commercial parts severed. An offer made early reads as reasonable; the same offer made after a refusal reads as a retreat.
Step 7: Keep the Request and the Answer Together
Whatever comes back, keep the request as sent, the acknowledgement, the reply and every document supplied, in one place and in order. Where the reply refuses in part, note which limb of which clause was invoked and whether the authority addressed the public interest question at all.
That record is what the next step in any forum is built from, and it is also the record that shows what the authority was asked and chose not to answer.
Step 8: Use What Comes Back on the Decision Itself
The purpose is rarely the documents. It is usually to understand how a particular decision was reached, and the criteria, the manual and the approved parameters often do that without any access to the system at all.
Where the material shows that the criteria applied were not the criteria approved, or that no criteria were approved, that is a point about the decision rather than about the technology, and it is a point that can be taken wherever the decision itself is challenged.
Common Pitfalls to Avoid
Asking for the algorithm: Clause (f) of section 2 is about material the authority holds, so the request should name documents.
Running two requests as one: The record of the decision and the record of the system are different asks and the first is usually less contested.
Treating clause (d) as a label: It requires commercial confidence, trade secrets or intellectual property, harm to a third party's competitive position, and no larger public interest.
Leaving the public interest to the authority: Sub-section (2) of section 8 is a route it may take, and the case for it belongs in the request.
Asking too widely: Name the decision or class of decision, the period and the category of document.
Offering severance only after a refusal: The same offer made in the request reads as reasonable.
Key Statutory Provisions
Clause (f) of section 2 of the Right to Information Act, 2005: Information means any material in any form, including records, documents, memos, e-mails, opinions, advices, press releases, circulars, orders, logbooks, contracts, reports, papers, samples, models, data material held in any electronic form and information relating to any private body which can be accessed by a public authority under any other law for the time being in force.
Clause (d) of sub-section (1) of section 8 of the Right to Information Act, 2005: Exempts from disclosure information including commercial confidence, trade secrets or intellectual property, the disclosure of which would harm the competitive position of a third party, unless the competent authority is satisfied that larger public interest warrants the disclosure of such information.
Sub-section (2) of section 8 of the Right to Information Act, 2005: Notwithstanding anything in the Official Secrets Act, 1923 nor any of the exemptions permissible in accordance with sub-section (1), a public authority may allow access to information, if public interest in disclosure outweighs the harm to the protected interests. The Act is No. 22 of 2005. The other exemptions in sub-section (1) of section 8 were not opened for this note and are not set out here.
Sources and References
Right to Information Act, 2005, sections 2 and 8
Disclaimer: This article is for informational purposes only and does not constitute legal advice. Readers should consult a qualified legal professional for advice specific to their circumstances.


Comments