Quick Reply: A Punjab SIC Full Bench settled five questions on who may argue your RTI hearing: any person — including a non-Advocate — may appear for an information-seeker, if the Commission authorises it; the representative may charge for the appearance; a formal Vakalatnama is not compulsory. The decision PDF is attached below.
In one line. Any person, including a person who is not an Advocate, may appear on behalf of an applicant or a Public Information Officer before an Information Commission, provided the Commission has authorised the appearance. The representative may charge a consideration.
What that means in practice.
In an order of the Full Bench of the Punjab State Information Commission, which deliberated and decided the following issues:
The decision is available here: Download Decision
1. **Name the representative in writing** — a simple signed authorisation from the appellant; the Full Bench treats a formal Vakalatnama as unnecessary, but the authorisation should be on record. 2. **Ask the Commission's leave before the hearing starts** — appearance is permitted "provided the Commission authorises it", so move the application first, not after objection. 3. **PIO side has the same latitude** — a departmental officer or an Advocate may represent the PIO; expect the hearing to proceed on records either way. 4. **Fees charged by a non-Advocate are not illegal** under this ruling — agree them beforehand, in writing.
The ruling is a State Commission's Full Bench decision — persuasive, not binding, elsewhere; the CIC has its own practice on representatives. File the authorisation regardless; it removes the objection everywhere.
No — RTI proceedings are not court litigation; the record and the law carry the appeal. A representative helps when you cannot attend or the case is heavy with documents.
Name of appellant, name of representative, appeal/complaint number, and the act being authorised — appearance and arguments on the appellant's behalf — signed by both.
Last reviewed on: 27 August 2026. Junk description rebuilt and typos fixed; the practical authorisation sequence and FAQ added.