RTI Record Management System for Public Authorities

A good record management system is the single biggest predictor of clean RTI compliance. Departments that suffer the worst RTI complaints are those whose records are scattered, undated and undigitised. This page sets out a five-pillar system that any public authority — Central ministry, State department, municipality or university — can implement in six months.

• The 30-day clock under Section 7(1) starts from receipt; you cannot extend it because your filing system is bad.
• The Commission's standard direction in slow-disposal cases is to “computerise and index records under Section 4(1)(a)”.
• The CAG's RTI compliance audit specifically tests record management.
• A clean record system protects officers personally — they can show audit trails.
• Section 4(1)(b) suo motu disclosure depends on records being readily extractable.

• Section 4(1)(a) — duty to maintain records duly catalogued and indexed and to computerise.
• Section 4(1)(b)(vi) — statement of categories of documents held by the authority.
• Section 7(9) — supply in different forms.
• Public Records Act, 1993 — Central archiving framework (where applicable).
• State manuals of office procedure — internal record-keeping rules.

1. One central index of every file in the office, organised by department / section / year.
2. Each file has: file number, subject, opening date, closing date, current location (active / archive / digitised), retention category.
3. Index is searchable — at minimum by subject keywords, by year, by file number.
4. Index is updated weekly by the records-section officer.
5. Index is itself a record disclosable under RTI (subject to redaction of any specific exempt entries).

1. Each file is assigned a retention category at the time of opening:
   • Permanent — policy files, Cabinet papers, legal opinions.
   • 30 years — major project files.
   • 10 years — administrative correspondence.
   • 5 years — routine correspondence.
   • 3 years — receipts, day-to-day forms.
2. The retention schedule mirrors the Public Records Act and the public authority's internal manual.
3. Files reaching their retention end are reviewed before destruction by a records committee.
4. Destruction is recorded in a register that itself is a permanent record.

1. Active files (last 5 years) digitised first.
2. OCR'd PDF — searchable, not just scanned images.
3. Each page numbered and stamped before scanning so the digital and physical match.
4. Cross-reference: each physical file's cover page mentions the digital location; each digital file mentions the physical location.
5. Use a content-management system with role-based access.

1. Each retrieval is logged: who pulled the file, when, for what purpose, when returned.
2. Logs help with Section 7(1) evidence — proof that the PIO did pull the record within X days.
3. Logs help with vigilance investigations.

1. Once a year, the records committee samples 5% of files at random and verifies:
   • Index accuracy.
   • Physical-digital match.
   • Retention schedule compliance.
   • Audit trail integrity.
2. Audit findings are reported to the head of office and reflected in the Section 25 annual return.

1. Step 1. Constitute the records committee — chaired by the head of office, including the PIO, FAA and IT in-charge.
2. Step 2. Take stock — list every file the office holds and assign a retention category.
3. Step 3. Procure or commission an index database (DMS).
4. Step 4. Train all sections on file-numbering convention.
5. Step 5. Pilot digitisation with one section; iterate; roll out to all sections.
6. Step 6. Publish the catalogue (subject to redaction) under Section 4(1)(b)(vi).
7. Step 7. Audit annually.

`[Office code]/[Section code]/[Subject code]/[Year]/[Serial]`

Example: `MEA/JS-Africa/Bilateral-Kenya/2026/047`.

The convention should be:

• Stable across years.
• Searchable in the index.
• Self-describing — a person reading the file number should know roughly what it is.

• No index at all — files exist physically but no central register.
• Index in a personal Excel sheet on one officer's laptop — fails when the officer is transferred.
• Digitised but not OCR'd — search does not work.
• Retention schedule on paper but not enforced — files accumulate forever; cellars overflow.
• No audit trail — when a file goes missing, no way to trace.
• No annual audit — bad data is never corrected.

• Section 4(1)(b)(vi) statement of categories.
• Master file index (with redactions for files containing genuinely exempt content).
• Retention schedule.
• Records-destruction register.
• Annual audit report of records.

A clean record system reduces these RTIs because the data is already on the website.

The Act says “computerise records appropriate to be computerised”. For most modern offices, a DMS is appropriate.

No. Destruction must follow the retention schedule and the public authority's manual, with a records committee approval.

Classified files are still recorded in an index (with title and classification) — the contents are restricted, the existence is not.

Personal pads in officers' drawers are not records. Notings on official files are records under Section 2(f).

Weekly minimum. After every major file-creation event.

The public authority. Officers do not own files personally; transfers do not entitle officers to take files.

Official emails on official accounts are records. Maintain an email archive aligned with the file system.

• The Right to Information Act, 2005 — Section 4.
• Public Records Act, 1993.
• Department of Personnel and Training, rti.gov.in — guidance on Section 4 implementation.
• National Archives of India, nationalarchives.nic.in — model retention schedules.
• Central Information Commission, cic.gov.in — Section 4(1)(a) directions.

• Section 4(1)(b) checklist
• Annual RTI return
• RTI cell SOP
• PIO and FAA details on website
• RTI compliance audit checklist

Last reviewed: 9 May 2026.