Designation of Public Information Officers

The right declared in Section 3 of the Right to Information Act, 2005 would be an empty promise if there were no human being inside the bureaucracy obliged to receive a citizen's request and answer it. Section 5 supplies that human being. It commands every public authority to designate Public Information Officers (PIOs) and Assistant PIOs, fixes the time within which the designation must happen, and builds a chain of personal responsibility that runs from the counter clerk up to the officer who actually holds the file. For the judiciary and CLAT-PG aspirant, Section 5 is the operational hinge of the entire statute: it converts the abstract duty in Section 4 and the substantive right in Section 6 into a named, accountable, penalty-bearing functionary. This chapter unpacks every sub-section of Section 5, the “deemed PIO” fiction in sub-sections (4) and (5), and the leading decisions—CBSE v. Aditya Bandopadhyay and J.P. Agrawal v. Union of India—that tell us what a PIO is, and is not, expected to do.

Why a Designation Provision Exists at All

The architecture of the Act, traced in our note on the introduction, object and scheme, moves in three steps: it confers a right (Section 3), it imposes proactive and reactive disclosure duties on bodies (Sections 4 and the obligations of public authority), and it then needs a mechanism through which a flesh-and-blood official actually processes individual requests. Section 5 is that mechanism. Without a designated officer, a citizen filing a request for obtaining information under Section 6 would have nobody to address it to, no time-limit running against any identifiable person, and no one against whom the penalty under Section 20 could bite.

The provision therefore performs three distinct functions simultaneously. First, it is an allocative rule: it tells every public authority to spread PIOs across all its administrative units so that a citizen anywhere can find a local point of contact. Second, it is a temporal rule: the designation had to be completed within one hundred days of the enactment of the Act, a deadline that signalled Parliament's intent that the machinery be up and running almost immediately. Third, and most importantly for litigation, it is an accountability rule: by naming an officer and attaching duties to that office, it creates the locus on which the Information Commissions later hang penalties and disciplinary recommendations.

The Text and Structure of Section 5

Section 5 is short but tightly engineered, with five sub-sections that move from designation, to assistant designation, to the duty of assistance, to the “borrowing” of other officers, and finally to the deeming fiction that makes those borrowed officers liable. Sub-section (1) requires every public authority to designate, within one hundred days of enactment, as many officers as Central Public Information Officers or State Public Information Officers as may be necessary “in all administrative units or offices under it” to provide information to persons requesting it.

Sub-section (2) adds a second tier. Without prejudice to sub-section (1), every public authority must designate an officer at each sub-divisional or other sub-district level as a Central Assistant Public Information Officer or State Assistant Public Information Officer, whose function is to receive applications and appeals and forward them “forthwith” to the PIO, the first appellate authority under Section 19(1), or the relevant Information Commission. The proviso to sub-section (2) is examinable in its own right: where an application or appeal is given to an Assistant PIO, a period of five days is added in computing the response time under Section 7(1). Sub-sections (3), (4) and (5) deal respectively with the PIO's duty to render reasonable assistance, the PIO's power to seek the assistance of any other officer, and the consequence that any officer whose assistance is sought is, for the purpose of contraventions of the Act, treated as a PIO.

Sub-section (1): The Core Designation Duty

Sub-section (1) is the spine of the section. Three of its phrases repay close reading. The first is “every public authority”—a term whose contours are set out in our note on the definitions of public authority, information and PIO under Section 2. Only a body that qualifies as a public authority is obliged to designate PIOs at all; the ambit of Section 5 is therefore parasitic on Section 2(h). The second is “as many officers…as may be necessary”: the number of PIOs is not fixed by the statute but left to the public authority's assessment of need, the implicit standard being that information must be reasonably accessible to requesters across the body's geographic and administrative spread. The third is “in all administrative units or offices under it”, which prevents a large department from designating a single PIO at headquarters and forcing every citizen to route requests through one bottleneck.

The designation is of an officer, and in practice the designation attaches to a post rather than to a named individual, so that the function survives transfers and retirements. The hundred-day deadline in sub-section (1) was a one-time transitional command tied to enactment; bodies that newly become public authorities are expected to designate PIOs as part of complying with the Act from the moment they fall within its scope. A failure to designate at all does not extinguish a citizen's right—the Commissions have consistently treated the head of the office as answerable in the absence of a designated PIO, a principle reinforced by the appellate scheme in Section 19.

Sub-section (2): Assistant PIOs and the Five-Day Rule

The Assistant PIO is frequently misunderstood, and the distinction is a favourite of examiners. An Assistant Public Information Officer is not a junior PIO with power to decide requests. The Assistant PIO is a receiving and forwarding post, designed for the sub-divisional and sub-district level so that a citizen in a remote area need not travel to the district or State headquarters merely to lodge a request. The Assistant PIO's statutory duty is to receive applications and appeals and forward them “forthwith” to the appropriate destination—the PIO under Section 5(1), the senior officer who is the first appellate authority under Section 19(1), or the Central or State Information Commission.

Because forwarding consumes time, the proviso to sub-section (2) grants the system a buffer: where an application or appeal is given to an Assistant PIO, “a period of five days shall be added” in computing the response period specified under Section 7(1). The thirty-day clock in Section 7(1) therefore effectively becomes thirty-five days when the entry point is an Assistant PIO. This is a concession to administrative reality, not a penalty on the applicant, and it must be read together with the parallel five-day transfer window in Section 6(3) discussed in the note on the disposal of request. The crucial examination point is that the Assistant PIO bears no decision-making responsibility and ordinarily incurs no penalty for refusal—the duty to decide, and the liability for wrongful refusal or delay, rest on the PIO.

Sub-section (3): The Duty to Render Reasonable Assistance

Sub-section (3) provides that every PIO shall deal with requests and “render reasonable assistance to the persons seeking such information”. This obligation is not decorative. Read with Section 6(1), under which a person who is unable to make a request in writing may seek the PIO's help to reduce an oral request to writing, sub-section (3) makes the PIO a facilitator rather than a gatekeeper. The duty of assistance is amplified for persons with disabilities by Section 7(4), which obliges the PIO to provide appropriate assistance to enable access to information held by the authority.

The Delhi High Court gave this facilitative conception its sharpest articulation in J.P. Agrawal v. Union of India (Delhi High Court, W.P.(C) No. 7232 of 2009, decided 4 August 2011). The Court held that a PIO is “not a mere post office” who passively relays whatever a subordinate hands over. The PIO must apply his or her mind, analyse the material placed before him or her, and then either disclose the information sought or record cogent grounds for non-disclosure. The judgment described the PIO as the “pivot” for enforcing the implementation of the Act, holding that it is to the PIO that the application is submitted and the PIO who is responsible for ensuring that the information sought is provided within the statutory time-frame. The duty of “reasonable assistance” in sub-section (3) is thus an active, mind-applying duty, not a clerical one.

Sub-sections (4) and (5): The Deemed-PIO Fiction

Sub-sections (4) and (5) are the most litigated part of Section 5 and the heart of its accountability design. Sub-section (4) empowers a PIO to seek the assistance of “any other officer as he or she considers it necessary for the proper discharge of his or her duties”. The PIO who does not personally hold a file is not thereby excused; the statute expects the PIO to reach into the department and obtain the material. Sub-section (5) supplies the teeth: any officer whose assistance has been sought under sub-section (4) shall render all assistance, and “for the purposes of any contravention of the provisions of this Act, such other officer shall be treated as a Central Public Information Officer or State Public Information Officer”.

This is the “deemed PIO” rule. Its effect is that the officer who actually causes a delay or wrongful withholding—the custodian of the record from whom the PIO sought help—can be visited with the same liability as a PIO, including the penalty under Section 20. The deeming fiction prevents the original PIO from being scapegoated for a default that occurred deeper in the hierarchy, and equally prevents the real defaulter from sheltering behind the fact that he was never formally designated. The Information Commissions have repeatedly held that a deemed PIO shares responsibility with the designated PIO, and that where the Commission can identify the officer at whose level the delay actually occurred, the penalty may be imposed on that deemed PIO.

Sub-section (4) must be carefully distinguished from the transfer power in Section 6(3). Under Section 6(3) the PIO transfers an application—or part of it—to another public authority that holds the information, and the PIO's responsibility largely ends with the transfer and intimation to the applicant. Under Section 5(4), by contrast, the information is held within the same public authority; the PIO does not transfer the request away but instead collects the material from a colleague, and remains answerable for the eventual response. Confusing the two is a common error: Section 6(3) is inter-authority, Section 5(4) is intra-authority.

The PIO Distinguished from the First Appellate Authority

Section 5 designates the officer of first instance. It does not designate the appellate machinery. The first appeal under Section 19(1) lies not to a separately designated officer but to “such officer who is senior in rank to the Central Public Information Officer or State Public Information Officer” in each public authority. Two consequences follow. First, the first appellate authority is defined by rank relative to the PIO, so the validity of the appellate designation depends on the underlying Section 5 designation having been properly made. Second, the same individual cannot wear both hats on the same request: the officer who decided the request as PIO cannot sit in appeal over his own decision, because Section 19(1) requires the appellate officer to be senior in rank to the PIO.

This relationship is why Section 5 and Section 19 are read together in practice. A public authority typically issues a single office order designating, for each unit, both the PIO under Section 5(1) and the first appellate authority under Section 19(1), the latter being a named senior post. The Assistant PIO under Section 5(2), as noted above, is neither—it is purely a conduit, with no power to decide a request and no role in deciding an appeal beyond forwarding it onward.

The Limits of a PIO's Duty: CBSE v. Aditya Bandopadhyay

If J.P. Agrawal defines the active duties of a PIO, the Supreme Court's decision in Central Board of Secondary Education v. Aditya Bandopadhyay, (2011) 8 SCC 497, defines the outer boundary of those duties. The Court held that the obligation under the Act is to provide access to existing information—information already held by, or under the control of, the public authority, or which is expected to be preserved or maintained under law. Where the information sought is not part of the record of the public authority, and is not required to be maintained under any law, rule or regulation, the Act casts no obligation on the authority to collect or collate such non-available information.

From this the Court drew the much-cited propositions that a PIO is not supposed to create information that does not exist, is not required to interpret information or furnish opinions, need not solve the problems posed by applicants, and need not answer hypothetical or speculative queries. The duty under Section 5(3) to deal with requests and render reasonable assistance is therefore a duty in relation to information as defined in Section 2(f)—recorded material in existence—and not a duty to generate fresh material on demand. For aspirants the synthesis is clean: J.P. Agrawal says a PIO must apply his mind and cannot be a post office; Aditya Bandopadhyay says that even a mind-applying PIO is not obliged to manufacture, compile or interpret information that the authority does not already hold.

Time-Limits That Run Against the PIO

Designation under Section 5 is what makes the time discipline of the Act enforceable, because the clock runs against an identifiable officer. Under Section 7(1), the PIO must, as expeditiously as possible and in any case within thirty days of receipt of the request, either provide the information on payment of the prescribed fee or reject the request for one of the permitted reasons. Where the information sought concerns the life or liberty of a person, Section 7(1) compresses this to forty-eight hours.

Two adjustments to this baseline flow directly from Section 5. First, where the request is lodged through an Assistant PIO under Section 5(2), the proviso adds five days, so the effective limit becomes thirty-five days. Second, the cost of delay is severe and personal: under Section 7(2), if the PIO fails to decide within the period under Section 7(1), the request is deemed to have been refused; and under Section 20(1) the Information Commission may impose a penalty of two hundred and fifty rupees per day, subject to a ceiling of twenty-five thousand rupees, on a PIO who, without reasonable cause, delays the furnishing of information beyond the limit. Because of the deemed-PIO fiction in Section 5(5), this penalty can fall not only on the designated PIO but on the deemed PIO whose default caused the delay. The mechanics of how a request travels through these limits are developed further in the note on the disposal of request.

Designation as the Foundation of Personal Accountability

The genius of Section 5 lies in the way it personalises accountability. By compelling the designation of a named officer, and by deeming custodial officers to be PIOs for the purpose of contraventions, the section ensures that every default has an owner. Section 20(1) authorises the Information Commission, while deciding a complaint or appeal, to impose the per-day penalty on the PIO for refusing to receive an application, for malafidely denying a request, for knowingly giving incorrect, incomplete or misleading information, for destroying information that was the subject of a request, or for obstructing the furnishing of information—always subject to the PIO being given a reasonable opportunity of being heard and to the burden of proving reasonable and diligent action lying on the PIO.

Section 20(2) goes further and empowers the Commission to recommend disciplinary action against the PIO under the service rules applicable to him where he has, without reasonable cause and persistently, failed in his duties. Section 5(5)'s deeming fiction means that an officer who never agreed to be a PIO, but whose assistance was sought under Section 5(4) and who then sat on the file, is exposed to precisely this penalty and recommendation regime. This is why J.P. Agrawal's insistence that the PIO recommend remedial action against a defaulting custodian, rather than merely passing on a deficient response, fits the statutory scheme: Section 5(4) strengthens the PIO's hand within the department, and Section 5(5) ensures the defaulter cannot escape.

Practical Designation Issues Before the Commissions

Several recurring problems arise from defective or absent designation, and they are worth knowing as application-style questions. The first is the no-PIO-designated scenario: where a public authority has failed to designate a PIO at all, the Commissions treat the head of the office or department as the de facto PIO, so that the citizen's right is not defeated by the authority's own default. The second is the wrong-PIO scenario: where an application reaches a PIO who does not hold the information but it is held elsewhere within the same authority, the correct course is to invoke Section 5(4) and collect it, not to reject the application; rejection or silence exposes the PIO to penalty.

The third is the multiple-authorities scenario, where the information is held by a different public authority; here Section 6(3) governs and the PIO must transfer the application, or the relevant part of it, within five days and inform the applicant. The fourth is the blame-the-subordinate defence, decisively rejected in J.P. Agrawal: a PIO cannot escape liability by pointing to a subordinate's failure, because the PIO is the pivot and must apply his own mind. Running through all four is the lesson that designation under Section 5 is not a formality but the load-bearing wall of the Act's enforcement structure, working hand-in-glove with the substantive right to information and the procedural route for a request for obtaining information.

Exam Synthesis and Common Traps

For revision, fix the following hierarchy in mind. The PIO (Section 5(1)) receives and decides requests and is the locus of liability. The Assistant PIO (Section 5(2)) only receives and forwards, triggering the extra five days under the proviso read with Section 7(1). The first appellate authority (Section 19(1)) is an officer senior in rank to the PIO and is not separately designated under Section 5. The deemed PIO (Section 5(5)) is any officer whose assistance the PIO sought under Section 5(4) and who is then treated as a PIO for contraventions.

The traps most often set are these: confusing Section 5(4) (intra-authority collection, PIO remains liable) with Section 6(3) (inter-authority transfer, responsibility shifts); assuming the Assistant PIO can refuse a request (it cannot decide at all); assuming the same officer can be both PIO and first appellate authority on the same request (Section 19(1) forbids it); and over-reading J.P. Agrawal to suggest a PIO must create or compile information, which Aditya Bandopadhyay squarely denies. Hold both cases together—the PIO must apply his mind to existing information, but is not obliged to generate information that does not exist—and most Section 5 problems resolve themselves. For the doctrinal foundation, revisit the Right to Information Act hub and the chapter on the obligations of public authority, which together explain why the designated officer matters.