Vibha's data and monitoring platform · vibha.org
ImpactLens
Get Started

Built by Vibha, for the field

Better data for every program

One configurable platform where any Vibha team builds its own forms, collects program data in one governed place, and turns it into insight for leadership.

Sign inWhy we built it
Participants in a Vibha program

The challenge

Program data is scattered. Leadership can’t see it.

Teams collect enrolments, baselines, assessments and surveys in whatever tool works for them. The data ends up in personal drives, out of sight of the people who need to act on it.

Fragmented tools

Some teams use Google Forms, others KoboToolbox, each with its own layout and spelling.

One-off applications

When a tool falls short, a new custom application is built — repeating the same effort for the same need.

Data in personal drives

Collected data sits with the individual who gathered it, harder to secure and easy to lose when roles change.

No leadership visibility

Leadership cannot easily see what data exists, where it lives, or what it says across states.

Slower decisions

Without a consolidated view, it is hard to compare programs, spot trends and act on them early.

Why we built it

From scattered tools to one shared platform

Vibha’s teams have collected data in whatever tool was to hand. ImpactLens replaces that patchwork with one configurable platform any team can use.

01

Google Forms

Teams start with simple forms, each kept in its own drive.

02

Third-party tools

When form logic needs more, teams move to tools such as KoboToolbox.

03

One-off applications

When neither is enough, a custom application is built from scratch — again and again.

04

One shared platform

Any team builds its own forms, and all data lands in one governed, role-based repository.

A summary of how data collection has worked across Vibha’s teams, and what ImpactLens changes.

What we built

Tools for the whole loop: collect, check, follow up, understand

Each answers a problem above. Pick a tab to see how.

Catch mistakes while the field worker is still on site.

Questions check each other as they are filled in, and dropdowns draw on lists managed once for every form.

  • Rules that calculate values and require answers only when they apply
  • District → block → site lists that cascade and auto-fill
  • Versioned publishing, so old answers keep their original wording
Read the docs →
Participants present41
Participants enrolled38

check present ≤ enrolled — flagged before the form is submitted

Built for programs like these

The work a form has to carry

Kinds of work this tool is designed around. Each starts from a template you can adapt.

Enrolment and baseline

Program teams build their own forms, with location lists that cascade district → block → site.

Assessments

Scored questions and cross-field checks, with an immutable form version behind every result.

Leadership dashboards

Program and organisation-level views of what is happening, where, and what needs attention.

Surveys and follow-up

Follow the same site or participant across later steps, with every response filed in one record.

One governed repository

All program data in one place, filtered by role and program, instead of personal drives.

Reviewed insights

AI-enabled insights reach the form creator first, and are published to leadership once validated.

Browse form templates →

How a program gets started

From a first conversation to the first form

01

Confirm requirements

Tell us the program, who fills the forms, and what decisions the data should support.

02

Build your forms

Configure the fields, lists and rules for your program — no developer needed.

03

Pilot with your team

Run a pilot, with hands-on training for the people who fill in and review the forms.

04

Roll out

Publish, review insights, and share dashboards with leadership as the program runs.

Who uses it

Everyone in the chain gets what they need

Program team members

Fill in clear, guided forms — on a phone, with answers checked as they go.

Program admins

Manage their program’s users, forms, data and reporting.

Platform team

Own the system, its roles and its governance across the organisation.

Leadership

See organisation-wide dashboards and published insights built on traceable records.

Safe by design

Care with the data of the people we serve

Collect only what a program needs. No identifying or sensitive data goes in without approved governance. Each person gets the least access their role requires, and a record is kept of who did what.

Security and compliance →

  • Permissions enforced by the server

    Roles are checked on every request — hiding a button is never the control.

  • Audit log and two-factor sign-in

    See who changed what, and protect accounts with a second factor.

  • Teams and sharing

    Share a form or app with a specific team, not with everyone.

Questions, answered

Frequently asked questions

The short answers. The documentation has the detail.

What is ImpactLens?
ImpactLens is Vibha’s internal data collection platform: a configurable form builder with a rules engine, shared dropdown lists, versioned publishing, dashboards and data apps that follow one subject across many updates. All data lands in one governed, role-based repository.
Why did Vibha build ImpactLens?
Vibha’s teams were collecting field data in different tools, such as Google Forms and KoboToolbox, and building one-off applications when those fell short. The data sat in personal drives, out of leadership’s view. ImpactLens replaces that with one reusable platform any team can configure without developers.
Who is ImpactLens for?
It is Vibha’s own platform, used by program teams to collect data, program admins to manage their program’s users, forms and reporting, a platform team that owns the system, and leadership who need organisation-wide visibility.
Who sees AI-enabled insights?
The form creator sees insights first, to check them against what they know. Once they are satisfied, they publish the validated insights and dashboards for leadership.
How does ImpactLens keep collected data accurate?
Rules check answers as they are entered — calculating values, requiring questions only when they apply, and validating across fields — and are verified again on the server when a response is submitted. Dropdowns draw on lists managed in one place, so a spelling is fixed everywhere at once.
What happens to old responses when a form is edited?
Nothing. Publishing freezes a form as an immutable version, and each response records the version it was filled on, so earlier answers always read against the wording the respondent saw.
Can I connect ImpactLens to Power BI or Looker Studio?
Yes. Power BI Desktop can read a form’s responses through a built-in OData feed or a Power Query script, and Looker Studio can show shareable charts of safe summary numbers. Signed webhooks can also send each submission to your own systems.
How is access to data controlled?
Access follows least privilege. Roles from Super Admin to program team member are enforced by the server on every request, forms and apps can be shared with a specific team or person, and an audit log records who changed what. Accounts can be protected with two-factor sign-in.
Can I collect personal details of participants?
Not without explicit, approved governance controls. Vibha’s data protection guidance applies: collect only what a program needs, and keep identifying or sensitive data out unless it has been approved.
How do I get started?
Create a workspace and follow the quickstart to build and publish a first form in about ten minutes, or write to impactlens.vibha@gmail.com to talk through your program first.

Start with your first form

Create a workspace and build a form, or write to the Vibha team to talk through your program first.

Sign inTalk to the team