01 · What breaks
Design for the failure modes, not only the happy path.
Women's groups handle money, local politics and sometimes violence at home. A system designed only for reporting upwards can expose members, misread what agency looks like and leave the group dependent on staff to see its own books.
Publicly exposing membership or finance
Savings balances, loan defaults and membership lists shown on a shared dashboard or in a WhatsApp group can bring pressure from family, moneylenders or local power holders. Give each group its own figures, show only aggregates beyond it, and restrict member-level finance to the group's bookkeeper and the assigned staff member.
Treating attendance as empowerment
A member who attends every meeting may still have no say over her own money. Attendance is an output. Pair it with decision records (who proposed, who was chosen, what was agreed) and a short periodic check on control over income and movement, read together with the facilitator's notes.
Household-level outcomes attributed to one service
When household income rises, the cause may be a loan, a husband's new job, a government scheme or a good monsoon. Record other support the household receives and report the collective's contribution as one factor among several. A claim that a single training produced the change rarely survives scrutiny.
Technology controlled only by external staff
If only the nonprofit's staff can open the books, the group cannot check its own balance, and the system leaves when the project does. Train bookkeepers and leaders on the group view, share a monthly statement in the local language, and plan the handover from the first month.
02 · Minimum viable model
Track the member and the collective as linked journeys.
Collectives need both levels at once. Group records hold meetings, books and federation links; member records hold savings, roles and the services each woman receives. The six records below keep the people flow and the money flow connected, so every loan can be traced to a decision and a member.
| Panchasutra norm | What the record stores | What the system can flag |
|---|---|---|
| Regular meetings | Meeting date, attendance, decisions | Groups with no meeting in the agreed interval |
| Regular savings | Savings per member per meeting | Members whose savings have stopped |
| Regular inter-loaning | Loans approved in a meeting, with purpose and amount | Groups holding idle savings with no internal lending |
| Timely repayment | Instalments due and paid | Overdue instalments, shown by group rather than by name on shared views |
| Up-to-date books of accounts | Bookkeeper, last update, reconciliation date | Books not reconciled with cash in hand and bank balance |
DAY-NRLM organises rural poor women into Self-Help Groups and their federations, Village Organisations and Cluster Level Federations, and describes good SHGs through the five Panchasutra norms above. LokOS is its web and mobile platform for digital bookkeeping of SHG and federation members, savings, loans and repayments. If your groups already keep books there, avoid building a second ledger. Hold the evidence LokOS is not designed for, and link the two by group code.
03 · Implementation sequence
Move through reviewable gates.
Begin with how the groups actually run, and fit the system to that rather than the reverse. Most collectives meet where the signal is patchy, so plan for offline field data collection from the first sprint.
Define the group's operating model
Write down how groups run today: meeting frequency, who keeps the books, savings and loan rules, federation tiers and which government platform they already report to. Programme leads and a few group leaders sign it off. The system then encodes these rules instead of inventing new ones.
Establish member and group identity
Give each group and member a stable ID, and keep memberships as dated links so a woman who moves to another group keeps her history. Check duplicates on her name, a family member's name and the village. Use the word the groups use for themselves on every screen.
Record decisions not only attendance
Add a short decisions section to every meeting form: loans approved, issues raised, actions agreed and who will follow up. Two or three structured fields and an optional voice note are enough. Over months this shows whether the group makes its own choices or waits for staff.
Connect financial and support workflows
Link loans to the meeting that approved them and the repayments that follow, and link referrals for schemes, legal aid or health to the member who needs them. Reconcile group books with cash and bank balances monthly, and raise differences with the bookkeeper first, not the whole group.
Review inclusion and leadership patterns
Each quarter, look at who holds roles and who speaks in decisions. Are the same women leading every group? Are poorer or younger members silent? The pattern prompts a facilitator conversation and perhaps a rotation rule the group chooses. The software shows the pattern; the group decides what to do about it.
Measure agency with context
Use a small set of agency questions asked the same way each time, such as who decides how her income is spent or whether she can visit the bank alone. A trained facilitator asks them privately and adds notes. The MEL lead reviews results with those notes before any figure leaves the programme.
04 · Evidence
Measure whether the work became clearer.
Group health and member agency need different evidence. These measures combine what the system holds with facilitator judgement, and each should be read group by group before it is rolled up. Our gender equity playbook covers the wider programme model.
05 · Responsible automation
Let systems prepare. Keep consequence with people.
Systems can support
- Group and member registers with dated roles
- Meeting, savings and loan ledgers
- Monthly book reconciliation checks
- Views of role-holding and participation patterns
People should decide
- Handling conflict or disclosure
- Interpreting agency and safety
- Loan or benefit decisions
- Changing group leadership
06 · Common questions
Practical questions teams ask.
Questions from teams supporting self-help groups and women's federations.
What should an SHG or women's collective management system track?
At group level: meetings, attendance, savings, internal loans, repayments, books, leaders and federation links. At member level: her savings and loans, roles held, services and referrals received and a small set of agency measures. The two levels must be linked, so a transaction is entered once and group books always match member balances.
How do you measure women's agency, not just participation?
Combine records of decisions with a few questions asked privately and consistently over time, such as who decides how her income is spent, whether she can travel to the bank alone and whether she has spoken at a panchayat meeting. Read the answers with facilitator notes, because a single figure without context can mislead in either direction.
Should SHG members be able to see their own records?
Yes. Members should see their own savings and loan balances, and each group should see its own books and meeting record. That is how members catch mistakes and how groups keep running after a project ends. Restrict who can see other members' finances, and never publish named balances in shared channels.
Can we run our own system alongside LokOS?
Usually, as long as you decide what each one holds. LokOS covers SHG and federation bookkeeping for DAY-NRLM. Your own system can carry decision records, agency measures and referrals, matched to LokOS by a shared group code. The test is simple: no bookkeeper should have to record the same savings or loan entry twice.
How should the system handle a member who discloses violence at home?
Not through a routine form. A disclosure goes to a trained staff member through a restricted record that only they and their supervisor can open, with a safe contact time and method noted. Group records show nothing about it. Any response, including a referral, is decided with the member and follows the organisation's safeguarding policy.