Maharashtra Right to Public Services Act: Portal Guide

Quick answer: The Maharashtra Right to Public Services Act, 2015 gives citizens a legal right to receive notified services within a fixed time, with three levels of appeal and penalties of up to Rs 5,000 per case for erring officers. Departments meet these duties best with a system that tracks every application's deadline, alerts officers early and links appeals to the original file.

Under the Maharashtra Right to Public Services Act, 2015, every notified application in a government office carries a clock. If the service is delayed or wrongly rejected, the citizen can appeal, and the designated officer can be penalised. Yet many departments, municipal corporations and zilla parishads still track these deadlines in registers, spreadsheets or disconnected systems.

The result is predictable. Officers learn about a missed deadline only when an appeal arrives, and reports for senior officers and the State Commission take days to compile. This guide explains how the Act works, what a Right to Public Services portal must do, and a practical plan to build or upgrade one.

How the Maharashtra Right to Public Services Act Works

District administration pages describe the Act as in force since 28 April 2015. Before designing any software, it helps to be clear on the framework the system must support:

• Notified services. Each department notifies the services it provides under the Act, with a stipulated time limit for each service.
• Designated officers. A named officer is responsible for delivering each service within the time limit.
• Appeals. If a service is delayed or rejected without proper grounds, the applicant can file a first appeal and then a second appeal with senior officers. A third and final appeal lies before the Maharashtra State Commission for Right to Services.
• Penalties. District administration pages state that an erring officer is liable to a penalty of up to Rs 5,000 per case.
• Oversight. The State Commission monitors implementation, with commissioners for the revenue divisions of Konkan, Pune, Nashik, Nagpur, Amravati and Chhatrapati Sambhajinagar.

Citizens can apply for many notified services through the state's Aaple Sarkar portal, the RTS Maharashtra mobile app and Aaple Sarkar Seva Kendras. Any departmental system should work alongside these channels, not compete with them. Always confirm the current list of notified services, time limits and appeal rules with the department and official sources, because they are updated from time to time.

Where RTS Compliance Breaks Down in Offices

Most RTS delays are not caused by unwilling officers. They come from gaps in how applications are tracked:

• Counter applications that are never entered into any system, so nobody watches their deadline.
• The clock counted from the wrong date, for example from scrutiny instead of receipt of a complete application.
• Time limits hard-coded in software, so every notification change needs a developer.
• Rejections recorded without reasons, which weakens the office's position in an appeal.
• Reports built only for head office, leaving field officers without a daily view of their own pending cases.

Each of these has a direct fix in the system design and rollout plan below.

What a Right to Public Services Portal Must Do

An RTS-ready system is more than an online application form. Its core job is to make sure no application silently crosses its deadline.

Service master with time limits

A central list of every notified service, its time limit, required documents, fees if any, the designated officer and the appellate officers. When a notification changes, an administrator updates the master once and every new application follows the new rules.

Automatic deadline tracking

The moment a complete application is received, the system calculates its due date and shows the remaining days to the officer handling it. Colour-coded queues such as within time, due soon and overdue help staff prioritise.

Alerts and escalation

Reminders by dashboard, SMS or email go to the designated officer before the due date. If the deadline passes, the case is flagged to the supervisor automatically.

Reasoned decisions

When an application is rejected, the system should require the officer to record reasons. This protects the office in an appeal and gives the citizen a clear explanation.

Appeal management

First and second appeals should be linked to the original application, so appellate officers see the full history, documents and timeline in one place, with hearings, orders and outcomes recorded. The same pattern works well for a grievance management system.

Citizen status updates

Applicants should be able to check status with an application number and receive updates at key stages. This alone reduces visits and phone calls to the office.

Manual Tracking vs RTS Software: A Comparison

Task	Registers and spreadsheets	RTS tracking system
Deadline calculation	Done by hand, easy to get wrong	Automatic from the service master
Warning before due date	Depends on someone checking	Alerts to the officer and supervisor
Counter applications	Often outside any tracking	Entered at the counter on the same clock
Rejection reasons	Inconsistent or missing	Mandatory field before a decision is saved
Appeals	Separate files, history hard to trace	Linked to the original application
Reports for review meetings	Compiled manually over days	On-screen and downloadable at any time
Changes to time limits	Staff must remember new rules	Updated once in the master

Integration with Aaple Sarkar and Other State Platforms

Most departments do not start from scratch. They already have some services on Aaple Sarkar, a departmental application for others, and paper processes for the rest. The steps below are the core of a sound integration plan.

1. Map every channel. List where applications come in today: Aaple Sarkar, departmental portals, service centres and physical counters.
2. Agree on data exchange. Where integration is permitted and technically available, use documented APIs to receive applications and send back status. Where it is not, provide a simple back-office screen to enter counter applications so they are tracked on the same clock.
3. Use a single application ID. Every application, whatever its channel, should have one reference that follows it through processing and appeal.
4. Reuse existing identity and document services. Use services approved by the state rather than building new ones.
5. Plan time for approvals and testing. Integration usually needs coordination with the state's IT agencies and the department's own IT cell, so build this into the schedule.

Reports That Officers Actually Use

RTS compliance depends on visibility. Senior officers need to see problems before they turn into appeals. Useful reports include:

• Applications received, disposed within time, disposed late and pending, by service and by office.
• Overdue cases by designated officer and by age.
• Rejection rates by service, with common reasons.
• First and second appeals filed, decided and pending.
• Monthly trends, to spot seasonal peaks such as admission or scheme deadlines.

Reports should be available on screen and as downloads, so offices can prepare returns for review meetings without manual compilation.

Planning the Build: A Practical Checklist

• Start with the service list. Collect all notified services, timelines and officers before design begins.
• Standardise workflows. Many services follow similar steps, so a configurable workflow engine avoids building each one separately.
• Design for Marathi and English. Labels, notices and SMS messages should be available in both languages.
• Follow government web guidelines. Accessibility, security and hosting requirements apply from day one. Our GIGW 3.0 compliance checklist covers the main points.
• Protect citizen data. Apply role-based access, audit trails and encryption, and collect only the documents each service needs.
• Train staff early. Designated officers and clerks should practise on a test system before launch.
• Phase the rollout. Begin with high-volume services in one office, fix issues, then extend across the district or department.

RTS tracking often sits next to other office systems. Linking it with e-Office file movement and a wider citizen services portal avoids duplicate data entry.

Frequently Asked Questions

What is the Maharashtra Right to Public Services Act?

It is a 2015 state law that requires notified public services to be delivered within stipulated time limits, names a designated officer for each service and gives citizens a right to appeal against delay or wrongful rejection.

How many appeals can a citizen file under the Act?

There are three levels. First and second appeals go to senior officers in the department, and the third and final appeal lies before the Maharashtra State Commission for Right to Services.

What is the penalty for delay under the RTS Act?

District administration pages state that an erring officer is liable to a penalty of up to Rs 5,000 per case. Confirm current rules with official sources.

Where can citizens apply for notified services online?

Many notified services are available through the Aaple Sarkar portal and the RTS Maharashtra mobile app, along with departmental portals and Aaple Sarkar Seva Kendras.

Can a department build its own RTS tracking system?

Yes, for internal processing and monitoring, provided it works with official state platforms and follows applicable government IT guidelines.

How Affix Center Can Help

Affix Center works with government departments and local bodies on portals, workflow systems and dashboards. Our e-governance services and product engineering team can help you map notified services, design deadline tracking and appeal workflows, integrate with existing channels and build the reports officers need.

If your office is planning or upgrading a Right to Public Services system, contact us to discuss your requirements.