The same person appears in several spreadsheets.
Teams cannot see a complete history of enrolment, services, assessments, referrals and outcomes.
Programme & evidence systems
Know who received what, what changed, and what needs attention.
We design programme MIS, case management, monitoring, evaluation and reporting systems around the journey your participants, partners and field teams actually take. One useful record from first contact to outcome, with evidence that can travel into decisions and reports.
What breaks today
The report is only as reliable as the journey underneath it.
Most reporting problems begin earlier: duplicate identities, unclear stages, offline delays, changing indicators or follow-ups that live outside the system.
Managers discover drop-offs after the programme ends.
Operational warning signs stay buried until a monthly or quarterly reporting cycle.
Every funder asks for a different version of the truth.
Programme and M&E teams rebuild numbers manually because indicators and source records are not connected.
See it working
Three screens your team would use every week.
A programme system earns its place when a field worker, a manager and an M&E lead each open it and see what they need to act on, not the same report.
SPSample participantEDU-02418 · consent active · cohort B
Enrolment verified, programme and location linkedComplete
Three sessions missed, reason not recordedFollow up
Coordinator assigns a home visitHuman decision
Baseline assessment, literacy level 2Recorded
One stable ID. Enrolment, services, cases and outcomes in one history instead of four spreadsheets.
4 follow-up visitsDue
2 referral check-insPlanned
6 forms waiting to syncQueued
1 record flagged by supervisorCheck
Work queues, not passive dashboards. Only the caseload assigned to them, on the device they carry.
78%attendance in cohort B this month
- Numerator
- Sessions attended
- Denominator
- Sessions scheduled
- Window
- 1–30 September
- Status
- Verified by MEL lead
Definitions beside every number. Funders get the same figure the programme team acts on.
Illustrative screens with sample data. Not a live partner record.
End-to-end workflow
From programme design to the next decision.
The system should support daily delivery and organisational learning. If it only produces a dashboard, the hard part is still happening elsewhere.
- Design, outcomes and targets
- Enrolment, consent and identity
- Services, attendance and cases
- Assessments, referrals and milestones
- Follow-up, outcomes and data quality
- Decisions, learning and reports
Programme MIS & case management
A working system for the frontline, not only a reporting database.
We start with the operating model, roles and decisions. The technology follows: often Zoho Creator or CRM, sometimes custom applications, and always the smallest stack that can be supported.
Participants, households and organisations
Stable identities, consent, relationships, programme eligibility, locations and history across multiple interventions.
Programmes, cohorts and services
Programme structure, partner delivery, batches, sessions, attendance, entitlements and field activities.
Case work and referrals
Needs, risk flags, action plans, notes, documents, referrals, follow-ups and role-based visibility.
Field and partner experience
Mobile-friendly forms, offline needs, partner portals, validations, task queues and supervisor review.
Monitoring, evaluation & reporting
Evidence should change a decision, not just fill a dashboard.
We connect indicators to source records, owners, review cadences and reporting obligations so teams can see both what happened and where they need to act.
Results framework
Translate Theory of Change, logframe and funder commitments into indicators the system can actually produce.
Data quality and accountability
Build validations, exception queues, review roles, audit history and definitions into the workflow.
Decision cadence
Design dashboards and reports around the weekly, monthly and quarterly conversations they must support.
Responsible assistance
Use AI for transcription, classification, summarisation or anomaly review only with traceable evidence and a named human decision-maker.
How a project runs
What you get at each stage.
Every programme system follows the same ImpactOS stages and sign-off points, so you always know what is being decided, by whom, and what you will have at the end of it.
- 01
Listen
We follow one participant through today’s process with the people who run it.
You getA journey map and a practitioner who has built this kind of system before - 02
Scope
Theory of Change, outcomes and indicators first, then the records and roles behind them.
You getA locked data model, an honest estimate and what we won’t do✓ Scope agreed - 03
Deliver
The smallest complete workflow first, tested with real roles, devices and connectivity.
You getA working first release, migrated data with a transformation log, and training in context✓ Design locked✓ Tested - 04
Close
We track completion, exceptions, duplicates and workarounds, not just logins.
You getHandover, documentation and 30 to 60 days of hypercare after go-live✓ In use - 05
Learn
A retrospective on what worked and what the next release should be.
You getA roadmap for connecting funding, people and finance in sequence
Programme systems are often the first release in a wider roadmap. See the five-stage transformation pathway →
Results
Programme systems already running in context.
The pattern transfers; the exact records, permissions and indicators change with the programme. Full case studies live on edzola.com.
Teacher development · Compass MIS20,000+teachers across four states
Teacher training, classroom observations and multilingual assessments. A new-state pilot logged 2 million interactions in its first week.
Read the case study ↗
Skilling & employability10,000+trainees a year
Regional teams, trainee journeys and automatic certificates in one system. Live in four months.
Read the case study ↗
Education access16,000+out-of-school children tracked
Identification, enrolment, attendance and retention, with separate access for field teams, partners and managers.
Read the case study ↗“Everyone was slightly blown away by what the portal can do and what potential it has. The team is highly collaborative and extremely responsive.”
Adding AI
When the record is solid, AI can take on the volume.
Our own products plug into a programme system once the journey and the evidence are clear. People keep every decision that affects someone’s rights, money or opportunity.
Zolabs · Listen
Voice follow-ups
AI-led phone interviews in participants’ own languages for outcome studies and feedback, each finding traced to what was said.
Explore Zolabs → DozAI · RunRepeat case work
Mission 01 verifies where graduates are working at 30, 90 and 180 days, and hands unclear cases to your team.
Explore DozAI → ZolaShield · ProtectConsent and DPDP
See where beneficiary data, especially children’s records, carries risk, with a 180-day plan to fix it.
Explore ZolaShield →Not sure where AI belongs in your programme yet?Start with AI for nonprofits →
Questions
What teams usually ask first.
If yours isn’t here, bring it to the first call. We’d rather answer it honestly than have it surface halfway through a build.
How long does a first release take?
It depends on the number of journeys, roles and integrations. We scope one complete journey first and give you an honest estimate when we agree scope. For reference, TRRAIN’s programme system was live in four months.
Can field teams work without connectivity?
Where the programme needs it, yes. We design offline-capable forms and test them with the devices and connectivity your field teams actually have, before anything goes live.
What will it cost to run, not just to build?
Cost follows records, roles, integrations, migration and support. We show expected running costs, including licences, up front. Eligible nonprofits can access subsidised delivery through the Built for Impact Programme.
We already have spreadsheets and an old system. Do we start over?
No. We profile what you have, agree a cut-off date and migrate only data that earns its place, keeping the source files and a transformation log so nothing is lost silently.
Who owns the data and the system?
You do, whichever platform we build on. Documentation and handover are part of the Close stage, so another team could maintain it.
Will AI make decisions about participants?
No. AI can transcribe, classify, summarise or flag anomalies, always with traceable evidence. A named person makes every decision that affects a participant.
Go deeper without duplicating
Guides for MIS, journeys and evidence.
Use these before or during discovery to align teams on what the system should do.
Complete guide
Nonprofit MIS software
Records, workflows, indicators, permissions and implementation decisions for a useful nonprofit MIS.
Read the guide →Solution libraryExplore programme-system solutions
Compare MIS, M&E, CRM, privacy, voice AI and workflow-automation approaches.
Explore solutions →Interactive field guideThe participant journey
Follow entry, services, milestones, drop-offs and outcomes across a programme.
Open chapter 3 →Interactive field guideData, M&E and workflows
Connect indicators, data quality and review cadences to the decisions they serve.
Open chapter 4 →Programme dataMake sense of programme data
Practical strategies for moving from scattered collection to useful information.
Read on edzola.com ↗M&E and reportingAlign M&E with reporting
Bridge the gap between measurement practice and useful impact reporting.
Read on edzola.com ↗Delivery principleProblem first, tool last
Why early prototypes and small tests beat tool-first implementation.
Read the essay →Sector context
The same journey, in different clothes.
Sector playbooks show how programme records and risk change across mission contexts.
Map the programme data chain.
Bring one programme workflow, reporting template or recurring data problem. We will trace where information begins, where it breaks and what the smallest useful system should change.