Where RTI compliance actually fails
The Right to Information Act 2005 created an obligation that most public authorities are capable of meeting. The information usually exists. Somebody in the office knows where it is. What goes wrong is almost never a refusal to disclose; it is the process around the disclosure.
A typical failure looks like this. An application arrives in the dak. It is entered in an inward register and sent to a section that turns out not to hold the information. Eight days later it reaches the right section. The officer who can answer it is on leave. The response is drafted on day twenty six, signed on day thirty two and dispatched on day thirty four. The applicant files a first appeal, the Commission observes on delay, and nothing in that sequence involved a decision to withhold anything.
Automation addresses exactly this. It does not change what is disclosable, who decides, or who is accountable. It changes whether anyone can see, on any given day, which applications are at risk and who is holding them.
The lifecycle to be modelled
An RTI case has a recognisable shape, and a system is only useful if it models the whole of it rather than the receipt and the dispatch.
- Receipt. The application arrives online, by post or over the counter. A unique case number is issued at receipt, and the receipt date is the date the statutory clock starts from.
- Fee. The application fee is recorded, and any additional fee raised for copying or inspection is tracked separately with its own communication and receipt.
- Allocation. The case is allocated to the Public Information Officer responsible, and internally to the section that holds the record.
- Transfer, where applicable. Where the information is held by another public authority, the transfer is recorded with its date.
- Response. The reply is drafted, reviewed, approved and issued, with the sections of the Act relied on recorded where information is withheld.
- First appeal. Where the applicant appeals, the case moves to the First Appellate Authority with its own timeline, hearing record and decision.
- Second appeal. Where the matter proceeds to the Information Commission, the status, hearings and directions are tracked against the same case.
- Closure. The case is closed with the complete record retained, including everything that was communicated and when.
Statutory timelines and the clock
The Act sets specific periods, and the consequence of missing them falls on individuals rather than on the institution in the abstract. The system should therefore treat the clock as a first class object rather than as a reminder.
Three behaviours matter more than any other feature:
- The clock runs from receipt, automatically. Not from allocation, not from when the section acknowledged it. Every day the application spends in transit is a day consumed.
- Escalation happens before the limit, not after. A notification on day thirty one is a record of failure. A notification on day twenty to the PIO and on day twenty five to the supervising officer is a chance to act.
- Appeals carry their own clock. A first appeal is not a continuation of the original case timeline; it is a separate period with its own deadline and its own escalation path.
Where the information sought concerns the life or liberty of a person, the Act requires a response within forty eight hours. That case type should be flagged at registration and treated as a distinct queue, because a forty eight hour obligation cannot be managed inside a thirty day workflow.
Internally, the useful discipline is to give each internal step its own deadline that adds up to less than the statutory period. If the section has ten days to provide records and the PIO has five days to draft, the office has fifteen days of buffer rather than a single thirty day cliff.
Roles, queues and separation
The Act assigns duties to specific roles, and the system should reflect them rather than flattening everyone into a single user type.
- Assistant Public Information Officer. Receives applications and appeals and forwards them, with the forwarding date recorded.
- Public Information Officer. Holds the substantive obligation to provide information or to refuse it with reasons. This is the queue that carries the statutory deadline.
- Holding sections. Provide the records the PIO needs, against internal deadlines that are tracked separately from the statutory one.
- First Appellate Authority. Hears and decides first appeals, with hearings scheduled and decisions recorded on the case.
Visibility should be restricted by role. Applicant details and case papers are seen by those handling the case, not by everyone with a login. This is not only good practice; it is part of handling personal data proportionately under the Digital Personal Data Protection Act 2023.
Exemptions, transfers and third parties
Where information is withheld, the decision should record the specific provision relied on rather than a general statement that the information is exempt. Recording the section applied has two effects: it forces the decision to be made deliberately, and it gives the First Appellate Authority something concrete to consider.
Transfers deserve particular attention because they are a common source of avoidable delay. The Act limits how long an authority may take to transfer an application to the authority holding the information, and the receiving authority timeline runs from its own receipt. Recording the transfer with its date is what allows an office to demonstrate that the delay occurred elsewhere.
Where the information relates to a third party, the third party has to be given an opportunity to make a representation before disclosure, and that consultation runs on its own sub timeline. A case that has entered third party consultation should be visibly distinct from one waiting on an internal section, because the management action required is completely different.
Reporting, returns and proactive disclosure
Once the lifecycle is recorded, reporting stops being a compilation exercise. The reports that matter operationally are simple:
- Applications pending, by age band, by PIO and by section.
- Applications approaching or past their statutory limit, as a live list.
- Disposal rate and average time to respond, by period.
- Appeals filed, appeals allowed, and the reasons recorded.
- Fee collected and additional fee raised, with receipts reconciled.
Annual returns and Commission queries then draw on the same data rather than requiring each section to submit numbers that never quite add up.
Section 4 of the Act places a proactive disclosure obligation on every public authority: to publish specified categories of information and to update them. Tracking what has been published, when, and when it is next due for review turns that obligation into a maintained list rather than an exercise repeated whenever it is raised.
Implementing without disrupting the office
RTI work does not stop while a system is introduced, so the sequence matters.
- Start with registration. Bring receipt, fee and allocation into the system first, and leave drafting where it is. Within a few weeks the office has a real pendency picture for the first time.
- Add the clock and escalation. Once registration is reliable, switch on deadline tracking and escalation. Expect the first month of escalations to be uncomfortable; that is the backlog becoming visible rather than being created.
- Bring in internal sections. Give holding sections their own queue and their own internal deadline, so the PIO stops chasing by telephone.
- Extend to appeals. Model the First Appellate Authority queue, hearings and decisions, then second appeals before the Commission.
- Then reporting. By this point the data supports it, which is the right order. Reporting introduced first only formalises incomplete records.
MeltX RTI Management models this lifecycle, and it sits alongside the other modules in the MeltX government track, which matters because a large share of RTI applications ask about assets, property, enforcement action and expenditure that other modules already hold in a maintained form.
This article describes the general operation of the Right to Information Act 2005. Public authorities should follow the text of the Act, the rules applicable in their jurisdiction and the directions of the relevant Information Commission, which take precedence over anything written here.