
🤝 Non-profit & NGO · Data Flow
How field data from an NGO's programmes flows from mobile surveys to dashboards and donor reports.
Drawing diagram…
NGO programme monitoring data flow: field workers collect beneficiary and activity data offline in KoboToolbox/ODK. Submissions sync to a central server, go through validation and de-duplication, and are stored in a monitoring database. Indicators (reach, attendance, outcomes) are computed and shown on a programme dashboard and compiled into donor reports.
flowchart LR
subgraph EXT["External Entities"]
FW[Field Workers]
DON[Donors]
PM[Programme Managers]
end
subgraph PROC["Processes"]
P1[1. Collect survey data offline]
P2[2. Sync submissions]
P3[3. Validate and de-duplicate]
P4[4. Compute indicators]
P5[5. Build donor reports]
end
subgraph STORE["Data Stores"]
D1[("Raw submissions (ODK server)")]
D2[("Monitoring DB (PostgreSQL)")]
end
FW -->|"1. Forms"| P1 --> P2
P2 -->|"2. Raw data"| D1
D1 --> P3
P3 -->|"3. Clean records"| D2
D2 --> P4
P4 -->|"4. Dashboards"| PM
P4 --> P5
P5 -->|"5. Reports"| DONHow a donor gives online to an NGO: choosing a cause, paying by UPI or card, and getting a tax-exemption (80G) receipt automatically.
Where an NGO's money comes from and where it goes: donations, grants and CSR funds flowing into programmes, operations and fundraising.
An NGO's fundraising platform: donation pages, donor CRM, recurring giving, tax receipts and impact reporting to donors.
The states of a grant, seen from the NGO applying for it: from concept note to award, reporting and close-out.
How an NGO takes a volunteer from sign-up to first assignment: screening, background check for child-facing roles, training and matching.
A schema for tracking an NGO's beneficiaries and the services they receive across programmes, for impact reporting.