Why RTIs sometimes take longer than the 30-day statutory window

Even though the RTI Act 2005 mandates a 30-day response, real-world delays are common. Understanding the typical bottlenecks helps us draft the RTI so these causes are minimized from the start — and escalate faster when they occur.

• Missing or incomplete supporting documents in the file. The PIO cannot release information about a matter if the underlying file is incomplete. Our drafting explicitly asks for the file-completion status, forcing disclosure.
• PIO transferred, retired, or on long leave — file not reassigned. When the originally notified PIO is unavailable and the department has not formally reassigned the PIO role, RTIs get stuck. Our advocates cite Section 5(4) to demand immediate deemed-PIO action.
• Jurisdictional confusion between offices. Some matters touch multiple offices (for example, property matters that span SRO + Tehsildar + Municipality). Our drafting addresses all relevant PIOs in parallel to prevent "not my department" deflection.
• Inter-departmental correspondence pending. The PIO may need information from a sister department. Under Section 6(3), the receiving PIO must transfer the application within 5 days if it concerns another public authority — we explicitly invoke this section to avoid silent forwarding.
• File physically misplaced at the office. Surprisingly common with older matters. An RTI asking specifically for the file's physical-tracking movement (who last handled it, where it currently is) forces the department to either locate or formally acknowledge the loss — which in itself triggers reconstruction.