Practice this in 30 seconds. Use our free RTI Assistant — AI-driven drafting, First Appeal, Second Appeal in one place.
In one line. If you want to know how to write an RTI application that works, write it to request records that exist — not answers, not explanations, not “why.” This single shift fixes most rejections. The rest of this piece shows you how, from someone who has read thousands of replies.
You spent a Sunday afternoon writing your Right to Information application. You walked to the post office. You paid Rs. 10. You posted it by Speed Post. You kept the receipt like a lottery ticket.
Thirty days later, a reply came. Two lines. “The matter is under process. You are advised to wait.”
Or worse — no reply at all.
You were polite. You asked a clear question. You even said “please.” And still, nothing.
I have seen this happen to thousands of people. I have also sat on the other side of the desk — training Public Information Officers (PIOs) and First Appellate Authorities for twenty-five years. I know why this happens. And I know the one fix that works.
I started working on Right to Information in the late 1990s, before the Act was even passed. When the RTI Act, 2005 came in, my work moved from advocacy to training.
I have trained PIOs in central ministries, state departments, police, and municipal corporations. I have trained First Appellate Authorities. I have spoken to thousands of citizens, activists, and journalists.
Everywhere, I noticed the same thing. Most rejections are not about secrets. They are about how the question is written.
A PIO is not a friend you can chat with. A PIO is a clerk with a rule-book. If your question does not fit the rule-book, the answer is no. That is how it has always been.
Here is the whole lesson in one line:
Ask for records, not answers.
The RTI Act, in Section 2(f), defines “information” as any material on record — files, notes, data, emails, reports, logs. The Act does not cover answers to your questions.
If you ask “Why did you reject my application?”, you are asking for an answer. The PIO has no duty to give you one. The Act does not cover it.
But if you ask “A certified copy of the file-noting that recorded the reasons for the rejection of my application dated ,” now the PIO must reply. The record either exists or it does not. If it exists, the PIO must share it — or explain which exemption applies, with a specific reason.
You moved the question from “answer” to “record.” That is the whole trick.
Here is how the same need looks — first the wrong way, then the right way.
Do you see the shift? Each “right” version points at a record that must exist somewhere in the file. The PIO cannot say “no such information is held” — because such information is always held.
This is how to write an RTI application that cannot be easily rejected.
There are two reasons.
Section 2(f) of the RTI Act defines information as material on record. Section 2(i) defines record as any document, file, or data held by a public authority.
You are entitled to records. You are not entitled to explanations.
When you ask a “why” question, the PIO has a lawful escape. The clerk can say: “No such information is held on record.” Technically, that is correct. Your application fails.
When you ask for a record, the escape is gone. The PIO either hands over the record, or cites a specific exemption — Section 8(1)(a) through (j), or Section 9, or Section 24. Any other refusal is invalid. See our full guide on the grounds for rejection.
Imagine a PIO's morning desk. Twenty RTI applications, all asking “Why?” Each one makes the PIO think, write, and defend. The safest reply is a short, non-committal one.
Now imagine twenty applications asking for specific records. The PIO pulls the file, photocopies the sheet, and mails it. The work is easier, and the law is satisfied.
PIOs are human. They respond to easy tasks. The records-not-answers shift makes your application the easy one.
Before you post any RTI application, run these four checks.
If your draft passes all four checks, post it. If not, rewrite.
Here is something I learned from sitting in training rooms with PIOs.
A PIO reads your RTI in under a minute. They look for three things:
If your application does not answer question 2 with a clear “yes,” the PIO has no duty to do the work of figuring out what you want. They will send a holding reply. You will be back where you started.
Make it easy for the PIO to say yes. That is the whole game.
When your RTI reaches a PIO's desk, you want them to think: “This is simple. Pull the file. Mail the copy. Done.”
You can read the full decision-framework a PIO uses in our PIO RTI Reply Guide, and the wider training material at the PIO / FAA Knowledge Base.
Even with a perfectly drafted RTI, you may get a weak or silent reply. That is not the end.
The appeal path is the second half of the system. Many people give up after the first rejection. Do not. That is exactly what weak PIO replies count on.
After twenty-five years of watching RTIs succeed and fail, I can tell you the difference between the winners and the losers in one sentence.
The losers ask for answers. The winners ask for records.
Write your next application as if the PIO is a clerk with a file-cabinet and a photocopier. Tell that clerk which drawer, which file, which page.
That is how to write an RTI application.
Your next application does not have to fail. Rewrite it before you post it. Ask for records, not answers.
Last reviewed: 21 April 2026.