Paavai Foundation - NGO Management System

OVERVIEW

What it is
A role-based management platform for programs, beneficiaries, volunteers, documentation and reporting.

Problem to solve
NGO information such as programs, photos and reports is hard to track across many districts, so teams struggle to see what is happening on the ground.

My role
I owned the structure, flows, dashboard, data visualization, components and visual design.

Why it matters
Clear records help the NGO show its impact, report accurately and act faster.

CONTEXT AND CHALLENGE

Paavai works across several districts and program types. Every activity produces information: who attended, which area was covered, what photos were taken and what documents support it. That information has to reach coordinators, managers and the founder, each with different needs.

The design question: How do we bring all of this into one place so that each person sees what matters to them and can act quickly?

Key challenges

• Programs run in many districts at once.

• Beneficiaries fall into several categories and need tracking.

• Five roles need different levels of access.

• Field photos and files must stay linked to the right program.

• Quarterly and yearly reports must be accurate and exportable.

USERS AND ROLES

District Coordinator: Create projects, upload photos and files, view own district reports.
State Coordinator: See activity and beneficiary totals across districts.
Manager and Founder: Monitor organization activity and reports.
South Indian Manager (Super Admin): Manage users, programs, categories, and see yearly analytics.

INFORMATION ARCHITECTURE

I organized the navigation by task type so daily work stays separate from management and settings. Main menu covers Dashboard, Programs, Beneficiaries and Volunteers. Management covers Donations, Reports, District Centers and Calendar. Communication holds Messages and Notifications, and System holds Settings and Help. Each role sees only the sections it needs.

USER FLOW

I mapped the District Coordinator's path first since they use the system most. After logging in, they land on the dashboard, open an assigned program, then create or update a project. From there they add beneficiary details, upload photos and files, review the program impact, and generate the quarterly report, all without leaving the core modules.

DESIGN PROCESS AND DECISIONS

Dashboard first
Instead of asking people to open several sections to understand the state of the NGO, the dashboard shows programs, beneficiaries reached, active volunteers and funds collected right after login.

Quick actions on the dashboard
Create program, add beneficiary, schedule event, generate report, announce and assign volunteers sit next to the data. Users can go from checking numbers to acting on them in one click.

Two project modes
Awareness classes for women and regular events need different fields. Campaigning mode and Project mode keep each form short, and dates fill in automatically to cut entry errors.

Photos tied to programs

Every photo carries its program name, date, location and coordinator ID, so field documentation stays linked to the activity instead of becoming loose uploads.

Charts over tables

A program impact chart and a beneficiaries-by-category view let managers spot changes across months and groups without reading records one by one. Categories can grow over time.

Role-based views

Each role gets the information and actions for its job. This keeps screens simple and protects data.

How the design evolved

Addbeforeandafterscreens:earlywireframenexttofinaldashboard,withonelineonwhatchangedandwhyAdd before and after screens: early wireframe next to final dashboard, with one line on what changed and why

SOLUTION

Dashboard
Key metrics, impact chart, category breakdown, recent activity, upcoming programs.

Programs
Assigned programs, two entry modes, calendar view.

Documentation
Photos and files linked to programs, with metadata.

Reports
Quarterly for districts, yearly for admins, exportable as PDF.

Addscreens:programs,photoupload,reports,accountcreationAdd screens: programs, photo upload, reports, account creation

VISUAL DESIGN AND DESIGN SYSTEM

The look is clean and calm: white backgrounds, rounded cards, soft borders and a purple and magenta brand color, with green reserved for positive status. Compact cards keep dense data easy to scan.

A reusable system covers buttons, inputs, navigation items, metric cards, charts, tables, dropdowns, status indicators, notification cards, quick-action cards and modals.

It follows four principles:

• Consistency

• Hierarchy

• Scannability

• Feedback

EXPECTED IMPACT

Once live, the platform is designed to bring programs, beneficiaries, volunteers, field documentation, analytics and reports into one structure. Teams will be able to see organization activity at a glance, record field work consistently, and produce quarterly and yearly reports for official use. The structure can also grow to include new districts, programs and beneficiary categories.

WHAT I LEARNED

Good UX for an enterprise tool is about the whole system, not single screens. Four questions guided every choice: who is using this, what do they need to know, what decisions do they make, and what actions do they take. Answering them made me think like a product designer rather than a screen designer.