About
Built by Vibha to see what works
ImpactLens is Vibha’s own internal platform for collecting, monitoring and reviewing program data, built and used by our teams.
Why Vibha built its own data platform
Vibha’s teams collect field data — enrolments, baselines, assessments, surveys — but until now there was no common platform to collect it. Teams relied on Google Forms or KoboToolbox, and when those fell short, a new one-off application was built from scratch.
Each of those efforts repeated the same work, and the data stayed in the personal drives of whoever collected it — out of sight of leadership. ImpactLens is the answer: one configurable platform where any team builds its own forms without developers, and all data lands in one governed, role-based repository.
On top of that data sit dashboards and AI-enabled insights. The form creator reviews insights first and, once satisfied, publishes them for leadership.
The organisation behind it
Vibha at a glance
Our purpose
Give Vibha’s teams one dependable place to collect, monitor and review program data.
Educate. Empower. Enable.
Built around Vibha’s programs
Forms, rules and data apps shaped by how monitoring, assessments and follow-ups really run.
Access by role
Each person sees only what their role needs, with an audit log of who changed what.
Made for government programs
Dashboards and exports that program teams can share with state and district partners.
Many programs, one platform
Teams across states work in one system, each seeing only what its role allows.
What we commit to
Four things we hold ourselves to
Stated as commitments rather than values, because a commitment can be checked.
We describe what exists
Every capability on this site is built and documented. We do not list a feature as shipped because it is on a roadmap, and we do not claim a certification we do not hold — see security and compliance for exactly where we stand.
Data stays with the program
Export it to CSV whenever you want and delete it whenever you want, in whole or one response at a time. We do not sell it, mine it, or train anything on it.
Answers stay readable
A published version is frozen and every response records the version it belongs to, so editing a form next year cannot quietly change what last year’s data appears to say.
The interface is not the security
Permissions are enforced by the API on every request. Hiding a button is a courtesy to the user, never a control — and the two are never confused here.
Getting in touch
Questions, or something not working?
The documentation covers most of it. For anything else there is a person at the other end.