An overview with a clear task entry point.
The home screen brings progress, registered beneficiaries and quick actions together. Add Beneficiary starts a distinct task without hiding the wider daily context.
Gramtek / Digital SakhiSocial impact · UX/UI design
Designing for the last mile of care.
A public-distribution platform supporting women village agents as they deliver free sanitary pads to rural communities in India.
Contribution & scope
UX/UI design, marketing & content
9 chapters · Original project artefacts
01 / Service context
A recurring delivery is a connected service.
Gramtek brings essential hygiene products to women through local female agents. The design problem spans more than a doorstep handoff: agents need reliable records and clear tasks, support teams need to resolve exceptions, and programme clients need a useful view of coverage.
Field agent
Work through assigned residents, onboard people and confirm handoffs.
Support team
Keep records accurate, coordinate agents and resolve operational requests.
Programme client
Understand coverage and activity across regions and time.
02 / Project film
See the service in context.
The project film introduces the people and distribution model behind the interfaces. It places the digital journey within the real-world service it supports.
03 / Research synthesis
Trust, task clarity and continuity.
The research material frames Gramtek around three connected needs: an approachable field experience, dependable operational records and interpretable programme information. Its interview guide explores daily routines, comfort discussing menstrual health, OTP difficulties, data accuracy and reporting needs. These questions translate into concrete design priorities.
Trust before data entry
The agent is both an educator and a service contact. The flow needs to leave room for explaining the scheme and establishing confidence before collecting details.
A manageable sequence
Identity, personal details, documents and phone verification become separate stages. A visible progression makes a long task easier to follow.
A record that survives the handoff
The same beneficiary information must remain understandable to the agent, the team resolving changes and the client reviewing activity.
04 / People & priorities
Different work calls for different interfaces.
The research personas make the differences between roles tangible. They are design models used to frame needs and questions, rather than individual participant biographies.
Priya · The local change-maker
An agent balancing village visits, family responsibilities and conversations about menstrual health. Design response: clear daily actions, familiar language and a guided task sequence.
Preeti · The system navigator
A support person coordinating agents, resident records and requests. Design response: queues that expose the next action, consistent record states and an understandable path for edits or transfers.
Meera · The impact evaluator
A programme client interpreting activity and allocating resources. Design response: region/date filters, drill-downs and exportable reports with clear definitions.
05 / Agent journey
From a daily overview to a confirmed record.
The supplied screens make the Agent journey concrete. They show a task-focused home screen, a staged beneficiary flow and a completion state. Explore each stage below to see how the interface supports the work.
Make identity entry understandable.
The first stage moves from empty to partial to complete identity entry, with grouped digits and a consistent Search action.
Keep personal details and documents in sequence.
The next screens collect personal and village details, then prompt for document images. The progress indicator and bottom action retain a consistent structure.
Make the verification state explicit.
Phone validation precedes sending an OTP. The verification screens show entry and completion states; a receipt-style confirmation closes the illustrated journey.
Original Agent design mockups. Example names, values and counts are interface content. Swipe the screen sequence on a phone; select a screen to inspect it.
06 / Interaction decisions
Make the next action visible.
The design uses repeated patterns to carry the agent through the flow. Large bottom actions keep the primary step in a consistent location; progress markers explain where the agent is; and visual states distinguish incomplete inputs from information ready to continue.
Prevent uncertainty at entry
Grouped identity digits and input feedback clarify what the search requires. The interface progresses from empty to partial to complete entry.
Keep location information structured
Personal details and village hierarchy are grouped together. Support staff can later work with the same structured record.
Show why a task can continue
Document prompts distinguish front and back images. Number validation, OTP entry and a final confirmation make intermediate states explicit.
07 / Support journey
Keep exceptions from becoming dead ends.
The research maps a support workflow that starts with recent activity, moves into agent and resident records, then handles verification, edits and transfers. The PDS platform description adds coverage tracking, delivery progress, escalations and training materials as operational concerns.
Review
See recent activity and locate the agent, resident or request that needs attention.
Resolve
Verify a new record, process a correction or transfer, and maintain the relationship to the responsible agent.
Coordinate
Use coverage and reports to support field teams and follow up on unresolved issues.
08 / Client dashboard
From programme overview to a focused review.
The Client Dashboard connects six areas of programme oversight through a consistent navigation and visual system. These proposed views show how a client can start with the overview, inspect delivery records and feedback, and review the finance, stock and field activity that support the service.
Client Dashboard / Six proposed views
The supplied mockups use “Project Smile” as their interface label. They extend Gramtek’s client story from programme overview into finance, delivery evidence, feedback, stock and field activity.
These are design mockups. Names, figures, ratings, percentages, dates and system-status labels are illustrative interface content, not verified programme results. Select a view to expand it, then select its image for a closer look.
01Overview
Start with the programme picture.
The overview puts registrations, deliveries, funds and active Digital Sakhis in one scan. Geography, age groups and feedback then add context to the headline measures. A shared time-period control establishes the reporting window.
Design intent Use the summary to decide which part of the service needs closer attention.
02Billing
Make the approval journey visible.
The billing view combines documents, current-month totals, remaining funds and historic records. Its approval timeline exposes the handoffs between medical officers, taluka and district roles, and the Civil Surgeon stage, with Done, In Progress and Pending states.
Design intent Keep the current bill, its stage and its supporting history together so the next follow-up is easier to identify.
03Proof of deliveries
Connect programme totals with delivery records.
The ePOD view brings beneficiary identifiers, names, ages, delivery dates and batch numbers into a structured table. Taluka, village and delivery-month filters narrow the record set; Reset and Apply Filter distinguish changing the criteria from applying them.
Design intent Move from an aggregate delivery count to the records behind it while retaining geographic and monthly context.
04Beneficiary feedback
Read the pattern and the individual experience.
A satisfaction summary and category breakdown sit alongside written reviews. Rating and taluka controls help clients explore feedback by theme and location, while each review retains its village, rating and collection context.
Design intent Use the summary to locate a pattern, then read the feedback that gives it meaning.
05Stock & supply
See availability across the distribution network.
The inventory view separates main-warehouse stock from taluka-level capacity. Current quantities, utilisation bars, Healthy/Low Stock labels and links to warehouse detail make the supply picture scannable.
Design intent Expose stock conditions alongside delivery oversight so a shortfall can be investigated before it disrupts the next cycle.
06Sakhi efficiency
Compare targets with service activity.
The Digital Sakhi table places assigned village, target, served count and an efficiency indicator on the same row. Taluka filters, sortable headings and pagination support a narrower review of field activity.
Design intent Keep the underlying target and served values visible when reviewing a performance indicator, and investigate context before drawing conclusions.
09 / Reflection
Clarity across the whole service.
The Agent screens show how a complex field process can become a sequence of smaller decisions. The research expands that thinking to the teams supporting delivery and reviewing programme activity. Future evaluation should observe real task completion, OTP recovery and the handoff of incomplete or corrected records.
Field evaluation
Observe whether agents can explain their progress and recover from interruptions.
Operational evaluation
Follow an edit or transfer request from submission to resolution.
Reporting evaluation
Check whether clients can interpret a metric, apply a filter and explain what the result means.
Takeaway
A clear field task is only the beginning. The record, the support process and the programme view need to stay connected.
Explore the PDS product overview
Sources: supplied research document, Agent screens and six proposed Client Dashboard mockups; AEPL PDS product description. Personas and research plans inform the design narrative. Programme and health figures are not presented as independently measured UX outcomes. The Support journey will gain its dedicated screen walkthrough when those mockups are supplied.
Next story / Wingmate