Differences
This shows you the differences between two versions of the page.
| — | cpd:pio:m6-understanding-application-pio-pov [2026/07/11 00:08] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{htmlmetatags> | ||
| + | metatag-description=(How a PIO should read an RTI application, | ||
| + | metatag-keywords=(read RTI application, | ||
| + | metatag-robots=(index, | ||
| + | metatag-og: | ||
| + | metatag-og: | ||
| + | metatag-og: | ||
| + | ====== M6, Understanding the RTI Application, | ||
| + | |||
| + | //Module 6 of 10. Reading time about 35 minutes. End-of-module quiz unlocks Module 7.// | ||
| + | |||
| + | A PIO who reads an application well will draft a defensible reply with half the effort of one who reads it poorly. This module is about that first pass through the page. You will learn to separate the genuine information request from a fishing expedition, to find third-party triggers, to apply the no-reason rule honestly, and to interpret the request without rejecting unfairly. | ||
| + | |||
| + | ===== The PIO is an interpreter, | ||
| + | |||
| + | The temptation, especially under workload pressure, is to read the application narrowly, reject what is unclear, and ask the applicant to refile. The CIC has consistently treated this approach as obstruction. The PIO is an interpreter of the request, not a gatekeeper of the right. | ||
| + | |||
| + | When you receive an application, | ||
| + | |||
| + | ===== A typology of RTI applications ===== | ||
| + | |||
| + | ==== Type 1, the specific factual request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 2, the policy-document request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 3, the comparative or statistical request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 4, the personal grievance request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 5, the third-party request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 6, the tender / contract request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 7, the inquiry / vigilance file ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 8, the wide net or fishing expedition ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 9, the constitutional or political request ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ==== Type 10, the security or intelligence overlap ==== | ||
| + | |||
| + | " | ||
| + | |||
| + | ===== The no-reason rule, section 6(2), and what it really means ===== | ||
| + | |||
| + | ==== The bar ==== | ||
| + | |||
| + | "An applicant making request for information shall not be required to give any reason for requesting the information or any other personal details except those that may be necessary for contacting him." | ||
| + | |||
| + | ==== What the bar does NOT prevent ==== | ||
| + | |||
| + | The bar prevents the PIO from demanding a reason as a precondition to processing. It does NOT prevent the PIO from considering the apparent purpose of the request as a relevant fact in the section 8(2) public interest analysis. | ||
| + | |||
| + | For example, where an applicant has stated in the application itself that the purpose is journalistic investigation into a public scandal, that statement may be considered in the section 8(2) override. Where the applicant has not stated a purpose, you cannot demand one, but you can consider the inherent public interest in the subject matter. | ||
| + | |||
| + | ==== Common section 6(2) violations to avoid ==== | ||
| + | |||
| + | - Asking, "Why do you want this information?" | ||
| + | - Asking, "What is your interest in this matter?" | ||
| + | - Asking, "Are you a journalist or an activist?" | ||
| + | - Asking, "Will you publish this?" | ||
| + | - Asking for identity proof beyond what is needed to deliver the reply. | ||
| + | |||
| + | The CIC has imposed costs on PIOs who insisted on identity proof, purpose statements, and " | ||
| + | |||
| + | ===== Identifying the third party at the application stage ===== | ||
| + | |||
| + | ==== Explicit third-party triggers ==== | ||
| + | |||
| + | - The application names a specific individual. | ||
| + | - The application asks for personnel records of a named or describable officer. | ||
| + | - The application asks for commercial information of a named company. | ||
| + | - The application asks for documents submitted by a specific party (returns, applications, | ||
| + | |||
| + | ==== Implicit third-party triggers ==== | ||
| + | |||
| + | - " | ||
| + | - " | ||
| + | - " | ||
| + | - " | ||
| + | |||
| + | In each implicit case, section 11 procedure must be considered. Where the third party is a class (all bidders, all recipients), | ||
| + | |||
| + | ==== Mass third-party class, the proportionality balance ==== | ||
| + | |||
| + | Where the application seeks records of a hundred or a thousand third parties, individual notices are unworkable. The PIO may issue a public notice inviting objections by a date, treat absence of response as no objection, and proceed. Document the notice and the responses received. | ||
| + | |||
| + | ===== Reading between the lines without rejecting unfairly ===== | ||
| + | |||
| + | ==== Identify the underlying question ==== | ||
| + | |||
| + | Many applications are worded as multiple sub-questions when the underlying request is one document. Identify the underlying document and supply it. Do not punish the applicant for verbose drafting. | ||
| + | |||
| + | ==== Identify the documentary anchor ==== | ||
| + | |||
| + | For every query, ask, what document or record can supply the answer? If a document exists, supply it. If multiple documents exist, list them and supply or invite inspection. | ||
| + | |||
| + | ==== Identify the natural authority ==== | ||
| + | |||
| + | If your authority is not the natural keeper of the records, section 6(3) transfer applies. Do not reply with "this information is not available with us" when in fact another arm of the same Government holds it. | ||
| + | |||
| + | ==== Identify the timeline embedded in the request ==== | ||
| + | |||
| + | If the application asks for the latest information, | ||
| + | |||
| + | ==== Identify the urgency ==== | ||
| + | |||
| + | If the application mentions an upcoming court hearing, a medical emergency, a pending appointment, | ||
| + | |||
| + | ===== A worked decoding of a real application ===== | ||
| + | |||
| + | Application text: | ||
| + | |||
| + | "Sir, I am a senior citizen and have applied for pension in 2021. Please supply: (1) the file noting on my pension claim, (2) the names of officers who handled the file, (3) the reasons for delay, (4) the action being taken to expedite my pension, (5) the comparative status of other pension applications filed in 2021 with similar service profiles, (6) the inspection report of the audit team on pension processing." | ||
| + | |||
| + | PIO's analytical reading: | ||
| + | |||
| + | - Item 1, file noting on the applicant' | ||
| + | - Item 2, names of officers who handled the file. Disclosable under settled CIC orders. Names of officers are part of public-functioning information. | ||
| + | - Item 3, reasons for delay. Disclosable from the file noting. | ||
| + | - Item 4, action being taken. Disclosable. This is also a grievance trigger, the PIO should ensure the public grievance mechanism is invoked in parallel. | ||
| + | - Item 5, comparative status. The request is for third-party pension applicants' | ||
| + | - Item 6, audit inspection report on pension processing. Disclosable as held by the authority. Section 8(1)(j) does not apply to the audit team's findings as such. | ||
| + | |||
| + | A PIO who reads the application this way will draft a clean reply within thirty days. A PIO who labels the request a fishing expedition and rejects it will pay a section 20 penalty. | ||
| + | |||
| + | ===== Distinguishing a complaint, a representation, | ||
| + | |||
| + | ==== An RTI request ==== | ||
| + | |||
| + | Asks for information that is held in the records of a public authority. The relief sought is the supply of records. | ||
| + | |||
| + | ==== A complaint ==== | ||
| + | |||
| + | Asks for redressal of a grievance, action against an officer, or a decision on a substantive matter. The relief sought is action, not information. | ||
| + | |||
| + | ==== A representation ==== | ||
| + | |||
| + | Asks for a policy change or a discretionary act of the authority. The relief sought is a discretionary decision. | ||
| + | |||
| + | When a single application carries all three, sever and reply on the RTI portion within thirty days. Acknowledge the complaint and representation portions and route them to the appropriate mechanisms. Do not reject the whole document because part of it is a grievance. | ||
| + | |||
| + | ===== Mindset shift, from rejection to reasoned disclosure ===== | ||
| + | |||
| + | The PIO's natural reflex, under workload pressure, is to find a reason to reject. Train yourself in the opposite reflex. For every item, ask first, "Can I disclose with redaction under section 10?" If yes, do so. Only when severability is impossible should you reject the item, and even then, with reasons. | ||
| + | |||
| + | This mindset shift is the single most important professional habit for the working PIO. It costs nothing, it builds public trust in the authority, and it protects you under section 20. | ||
| + | |||
| + | ===== Closing note for Module 6 ===== | ||
| + | |||
| + | This module gave you the analytical framework to read any RTI application. In Module 7 you will put this together with the drafting framework from Module 4 and the exemption framework from Module 5 to write your own PIO replies, which will be evaluated by an AI rubric trained on RTI Wiki. | ||
| + | |||
| + | ===== Cross-links you can use ===== | ||
| + | |||
| + | For citizen-side reading on how to draft a good RTI, see [[https:// | ||
| + | |||
| + | ===== Disclosure ===== | ||
| + | |||
| + | This module is part of the RTI Wiki PIO Certification Course. The course is a Learner Certificate programme. It is NOT accredited by any government or statutory body. The drafting exercises in Module 7 are evaluated by a Large Language Model trained on RTI Wiki content, not by human evaluators. Scores are indicative knowledge measures, not legal advice. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | //Now take the M6 quiz to proceed to M7.// | ||
| + | |||
| + | ===== Understanding RTI application from PIO's perspective (2026) ===== | ||
| + | |||
| + | - **Step 1: How does a PIO process an RTI application? | ||
| + | - **Step 2: Comparison table — PIO decisions and legal basis.** (a) Full disclosure: (i) condition: information not exempt, (ii) timeline: 30 days, (iii) fee: Rs 2 per page, (b) Partial disclosure: (i) condition: part exempt under Section 8, (ii) timeline: 30 days, (iii) action: sever exempt portion under Section 10, (c) Rejection: (i) condition: exempt under Section 8/9, (ii) timeline: 30 days, (iii) action: reasoned order with specific subsection, (d) Transfer: (i) condition: information held by another authority, (ii) timeline: 5 days under Section 5(4), (iii) action: transfer to correct PIO, (e) Third party: (i) condition: information relates to third party, (ii) timeline: 40 days (10+30), (iii) action: Section 11 notice. | ||
| + | - **Step 3: Common challenges PIOs face.** (a) Vague applications — difficult to identify requested information, | ||
| + | - **Step 4: How applicants can help PIOs respond faster.** (a) Be specific — cite exact document/ | ||
| + | - **Step 5: E-E-A-T signals.** (a) Sources: dopt.gov.in, | ||
| + | - **Step 6: Practical tips.** (a) understand PIO's perspective to draft better applications, | ||
| + | |||
| + | See [[https:// | ||
| + | |||
| + | {{tag> | ||