Designing a simpler,
more accessible
MahaRERA portal

🏛️ About MahaRERA

The Maharashtra Real Estate Regulatory Authority (MahaRERA) is the statutory state body that regulates the real estate sector in Maharashtra under the RERA Act, 2016. It maintains the official public record of every registered housing project in the state, tracks promoter (builder) compliance, and gives citizens an independent way to verify a project before they commit their life savings to it. No promoter can legally advertise, market, or sell a housing unit in Maharashtra without first registering the project with MahaRERA.

👥 Who uses it, and why

• Citizens & Homebuyers — use MahaRERA to verify a project's registration status, promoter credibility, and construction timeline before booking a flat. For most first-time buyers, it is the only independent, government-backed check available to them.
• Promoters & Builders — register new projects, file mandatory quarterly progress updates, upload legal and financial disclosures, and respond to homebuyer complaints through the platform.
• Real Estate Agents — register as authorised agents, look up project credentials before recommending a property, and renew their own agent certification each year.

🧩 Two Major Problems

MahaRERA is really two separate digital products serving two very different audiences — a public-facing Website for verification and trust, and an internal-facing Application Portal for compliance and filing. Both had accumulated years of usability debt.

🎯 Problem Statement

"Homebuyers in Maharashtra cannot quickly and confidently verify whether a real estate project is legitimate and on schedule, because the website presents registration data in a technical, disconnected format that assumes users already know what they're looking for."

😤 User Frustrations

🔬 Research Approach

A mixed-methods approach was chosen so that quantitative data could reveal the scale of each problem, while qualitative data explained the "why" behind it.

• Quantitative: Analysed 90 days of website analytics — search abandonment, page drop-off, session duration. Chosen because it surfaced the scale of each problem across all 6M+ users without needing to interview each one individually.
• Qualitative: Ran 18 moderated interviews and 6 contextual inquiries with homebuyers, promoters, and agents across urban and rural Maharashtra. Chosen because analytics could show where users dropped off, but not why — especially for lower digital-literacy users.
• Competitive / heuristic audit: Benchmarked against two other state RERA portals and a private real-estate marketplace to see what strong project search and trust-signalling looked like outside typical government UX.

📊 Competitor Analysis

Illustrative benchmark data compiled for internal reference — not official published figures.

📈 What the Data Revealed

Representative figures synthesised from analytics review + interview sessions for this case study.

🧑‍🤝‍🧑 User Personas

🔑 Key Findings

• Search is the single biggest point of failure across all three personas — each expects to search differently (by name, locality, or registration number) but the old site supported only one.
• Trust is established visually before it's established textually — users scanned for badges, certificates, and status colour before reading any copy.
• The bureaucratic tone read as "hiding something" — plain language and clear status indicators measurably increased perceived legitimacy in sessions.
• Promoters and agents need a different information density than citizens entirely — one dashboard could not serve all three well.

🎯 Strategy

Redesign the MahaRERA website around three role-based journeys — Citizen, Promoter, Agent — replacing a single one-size-fits-all interface with role-aware information density, plain-language content, and visible trust signals, while remaining fully compliant with government accessibility and security mandates.

📐 Scope of Work

• In scope: Public website redesign — project search, search results, project detail pages, QR verification, homebuyer guidance, and the three role-based corners.
• Out of scope (this phase): The Application Portal's internal filing forms (Part 2), payment gateway redesign, and the mobile native app.

✅ Success Criteria

• Reduce average project-search task time from 6m 40s to under 2 minutes.
• Meet WCAG 2.1 AA and GIGW accessibility compliance at launch.
• Cut "site feels untrustworthy" survey responses from 81% to under 25%.
• Zero data loss on government security and penetration audit.

🗺️ Planning — Project Phases

• 1. Research — discovery interviews, analytics review, competitor audit.
• 2. User Stories — role-based stories written and prioritised with stakeholders.
• 3. Design — full design system + ~25-page screen layout across all three corners.
• 4. Development — front-end build in parallel with backend API work.
• 5. Review — stakeholder, technical, feasibility, and accessibility review rounds.
• 6. Iteration — refine flows and content based on review feedback.
• 7. Integration — connect to live backend data from the Application Portal via API.
• 8. Testing — usability testing, QA, and security audit.
• 9. Deploy — domain approval from Government IT cell, hosting on the government server (NIC), publish.

⏱️ Estimated Timeline

🧭 Determine Flow

Every user flow was mapped back to the three personas before any screen was drawn — search flow, verification flow, and role-corner navigation.

📋 Feature Prioritisation — MoSCoW

🎨 Design System & Branding

• Colour & Typography: Government-appropriate but modern palette; high-contrast type scale meeting WCAG AA at every size.
• Atomic components: Buttons, status badges, cards, and tables built once as reusable tokens across all 25 page layouts for consistency and dev handoff speed.
• Branding: Retained the official MahaRERA identity while modernising iconography and removing dense bureaucratic visual noise.

🗺️ Journey Mapping

🧩 Prototyping Process

• Low-fi: Paper sketches of every core screen — fast, disposable, easy to argue with in a room full of stakeholders.
• Review & Iteration: Sketches reviewed with the research team and revised where flows didn't match persona goals.
• Mid-fi: Grayscale block prototypes to lock information architecture and layout before any visual design was applied.
• Hi-fi: Fully styled, interactive prototypes matching the new design system, built for stakeholder walkthroughs and usability testing.

Low-fi sketches Add photos of the paper sketch sessions.

Mid-fi wireframes Block-level layout prototypes.

Hi-fi prototype Add final styled interactive prototype screens.

🔎 Search Project

Inspired by professional, corporate real-estate search experiences rather than typical government form patterns. Search now supports name, locality, promoter, and registration-number filters at once. Problem solved: a first-time buyer no longer needs to know a registration number to find their project.

📄 Search Result Page

Every result surfaces the information a buyer actually decides on, at a glance:

• Project name & promoter name
• Location
• Registration certificates
• Last updated date & expected completion date
• View application details / view documents

📱 QR Code Verification

Every registered project now gets a scannable QR code for use on physical advertisements and hoardings — a buyer scans it on-site to instantly confirm the project's registration authenticity, without typing anything.

🏗️ Building Data Visualisation

Illustrative data — approved floors vs. sold, unsold, and mortgaged flat counts.

🚪 Role-Based Corners

Content and navigation split into three dedicated "corners" so each audience sees only what's relevant to them: Citizen Corner (search, verify, guidance), Promoter Corner (filings, project status, compliance), Agent Corner (verification lookups, registration renewal).

📘 Guidelines for Homebuyers

A step-by-step guidance module walks first-time buyers through what to check before booking — registration validity, promoter history, and how to read a certificate — in plain language, not legal text.

🧪 Review Rounds

No major structural changes came out of this round — the core information architecture held up. What did change was the user flow being refined, missing information being added back into result pages, and content clarity being tightened throughout.

⏱️ Usability Test Outcomes

Moderated sessions, n=14 participants across the three personas. Times are illustrative, representative of observed trends.

🔁 Iterations

• Refined the search filter order based on how testers actually searched, not how the data was structured internally.
• Improved the document-preview experience so users didn't need to download a PDF to check a certificate.
• Final hi-fi prototype locked and handed off to development with all four review rounds closed out.

🛠️ Design + Code Collaboration

• Design ↔ code pairing: Sat alongside the development team through the build so component behaviour matched the design system exactly, not just the static screens.
• Data integration: Connected the website's search and result pages to live data from the MahaRERA Application Portal database — the same records promoters file quarterly updates against.
• Search filters: Implemented the multi-criteria filter logic (name, locality, promoter, registration number) defined in Chapter 3.

🔌 API Development & Testing

• APIs were developed per feature, on demand — search, verification, certificate lookup, and building-data endpoints were each scoped and built as design work confirmed the exact data needed.
• Every endpoint was tested in Postman before frontend integration, covering expected responses, empty states, and error states.
• A curated API layer was introduced so the public website only ever receives sanitised, citizen-safe fields from the Application Portal's full internal dataset.

✅ QA, Content & Launch Prep

• QA: Cross-browser and cross-device regression testing against every user flow validated in Chapter 5.
• Content alignment: Final copy pass to keep tone consistent with the plain-language principle from Chapter 1.
• SEO & production content: Metadata, page titles, and structured tags added so project pages are correctly indexable and discoverable.
• Launch management: Coordinated go-live checklist across design, engineering, and the MahaRERA IT cell.

Publishing a government platform is rarely a single "deploy" step. Some features performed exactly as designed the moment they went live; others surfaced real-world edge cases that no prototype session had caught, and needed further work post-launch.

📊 Post-Launch Usability Data

🅰️🅱️ A/B Testing Against Success Measures

4-week split test against the defined success criteria from Chapter 2.

🎯 Hypothesis for Optimisation

"If document previews are surfaced directly on the result card instead of behind an extra click, in-session verification confidence and document engagement will increase further." — queued as the next optimisation test.

📝 Content Audit & Settlement Analysis

• Content audit: Every legal/regulatory string was cross-checked against the Application Portal's source data to ensure the simplified website copy never diverged from the legal record.
• Data & settlement analysis: Reviewed how registration and completion-status data settles between systems over time, to catch any lag between a promoter's filing and what the public website displays.

📈 Outcomes

The redesigned MahaRERA website significantly improved the state's digital public infrastructure — bridging the gap between citizens and critical regulatory data, and giving promoters and agents a system that finally reflected how they actually work.

🚀 Future Work

The redesigned website was built to be a starting point for a more connected regulatory ecosystem, not a finished endpoint. Planned next-phase integrations with other government departments directly or indirectly linked to real estate:

• Planning approval integration: Pull live planning & building-permission approval status directly from municipal planning departments.
• Sold register directory integration: Cross-reference the official sold-flat register to strengthen the building data visualisation with government-verified sale records.
• Financial transaction data integration: Connect escrow/RERA account transaction data to monitor real project progress against declared timelines, not just self-reported status.