E-Governance

Right to Public Services Portal in Maharashtra: A Guide

Affix Center · · 6 min read

Right to Public Services Portal in Maharashtra: A Guide - Affix Center

Under the Maharashtra Right to Public Services Act, 2015, citizens have a legal right to receive notified public services within a fixed time. If a service is delayed or wrongly rejected, they can appeal. For a department, a municipal corporation or a zilla parishad, this means every application now carries a clock. A well-built Right to Public Services portal in Maharashtra is how an office keeps track of that clock across hundreds or thousands of files.

The challenge is that many offices still manage RTS timelines through registers, spreadsheets or separate systems that do not talk to each other. Officers find out about a missed deadline only when an appeal arrives. Reports for senior officers and the State Commission take days to compile. This guide explains what an RTS-ready system needs, how it fits with the state's existing platforms, and how to plan the build.

How the Right to Services Framework Works

Before designing any software, it helps to be clear on the framework the system must support. In simple terms:

  • 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, the applicant can file a first appeal and then a second appeal with senior officers in the department. A third and final appeal lies before the Maharashtra State Commission for Right to Services.
  • Oversight. The State Commission monitors implementation, with commissioners for the revenue divisions of Konkan, Pune, Nashik, Nagpur, Amravati and Chhatrapati Sambhajinagar.

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

What a Right to Public Services Portal in Maharashtra 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. The key functions are:

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 the notification changes, an administrator updates the master once and every new application follows the new rules.

Automatic deadline tracking

The moment an 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 case of 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. Appeal hearings, orders and outcomes must be recorded.

Citizen status updates

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

Integration with Existing 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. A good design plans for this reality.

  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 approved by the state, rather than building new ones.

Integration work usually needs coordination with the state's IT agencies and the department's own IT cell, so plan time for approvals and testing.

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
  • Trends by month, to spot seasonal peaks such as admission or scheme deadlines

Reports should be available on screen and as downloads, so offices can prepare periodic 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. A configurable workflow engine avoids building each service 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 for government systems apply from day one.
  • Protect citizen data. Apply role-based access, audit trails and encryption. Collect only the documents each service actually 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.

Our broader e-governance services cover related areas such as workflow automation and departmental portals, and the same principles of clear ownership and phased rollout apply here.

Common mistakes to avoid

  • Counting the deadline from the wrong date, for example from scrutiny instead of receipt of a complete application
  • Letting offline counter applications sit outside the system, where no one tracks their timelines
  • Hard-coding time limits in the software, so every notification change needs a developer
  • Building reports only for the head office, leaving field officers without a daily view of their own pending cases

Frequently Asked Questions

Which law gives citizens the right to timely services in Maharashtra?

The Maharashtra Right to Public Services Act, 2015. It requires notified services to be delivered within stipulated time limits and provides for appeals.

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 State Commission for Right to Services.

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 service centres.

Can a department build its own RTS tracking system?

Yes, for its 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 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 Services system, contact us to discuss your requirements.