Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Industry Playbooks 6 min read

NGO programme data management: a buying guide

How to buy programme data management for an NGO: requirements, provider categories, a scorecard, pricing questions, pilot design and exit terms.

E
EncryptTechBD · 0 comments
Mechanic working in an automotive workshop
Photo: AJ Yorio / StockSnap

An NGO buying programme data software is rarely buying a blank database. It is buying a way to reconcile field reality, donor reporting and participant protection. The field team needs a form that works offline. The programme manager needs a result by district. The donor needs a report in a defined format. The data protection lead needs to know why each record exists and who can see it.

This buying guide is for a Bangladeshi NGO, foundation or implementing partner that has outgrown spreadsheets and wants a system it can defend. It does not repeat the common failure modes. It sets out the requirements, the provider options, a scorecard, the pricing questions and the pilot that proves the system before a full rollout.

Requirements before software

  • Programme structure. Projects, components, locations, cohorts and reporting periods, with a clear rule for when a participant belongs to more than one.
  • Participant identity. A way to avoid duplicate beneficiaries without collecting more personal data than necessary.
  • Indicators and results. Definitions, disaggregation, targets, data sources and the calculation method for each indicator.
  • Field collection. Offline forms, low-bandwidth sync, device sharing, validation at the point of entry and a path for paper fallback.
  • Consent and purpose. Recorded consent, purpose limitation, withdrawal handling and rules for photos, case stories and referrals.
  • Case or service records. If the programme provides services, the system must track interactions, referrals and outcomes without turning sensitive notes into open data.
  • Donor reporting. Outputs mapped to each donor's format, with a reproducible path from raw record to reported number.
  • Access and audit. Role-based access, field-level restrictions, an audit trail and a process for staff exits.
  • Language and usability. Bangla interfaces where field staff need them, plus clear labels and minimal free-text fields.

Provider categories

  • Generic CRM configured for programmes. Flexible and widely supported, but participant and case management may need extensive customisation.
  • Purpose-built monitoring and evaluation platform. Strong on indicators, forms and donor reporting; may be weaker on case management and local support.
  • Custom application. Best fit for unusual programme models or strict data residency, but requires long-term ownership.
  • Local systems integrator. Useful for training, offline field work and ongoing support; check the underlying product and exit terms.
  • Spreadsheet and mobile forms. A reasonable starting point for one programme, but weak on access control and duplicate prevention at scale.
  • Shared consortium platform. Common in donor-funded consortia; efficient for joint reporting but needs clear rules on who owns and can see shared data.

A scorecard

CriterionWhat good looks likeWeight
Offline field useForms work on shared devices, sync without duplicates and recover from interruptions.High
Indicator modelDefinitions, disaggregation and calculation logic are visible and versioned.High
Participant protectionConsent, purpose, field-level access and retention can be enforced, not just described.High
Donor reportingA report can be reproduced from source records without a parallel spreadsheet.High
Local supportTraining and support in Bangla, with a realistic response time for field issues.Medium
IntegrationExports and APIs for finance, referrals and any existing case system.Medium
Total cost of ownershipImplementation, training, devices, connectivity and annual support are all visible.High

Score from one to five against evidence, not promises. Ask for a demonstration using a programme that resembles yours, including a field device with no connection.

Pricing questions

  • Is pricing per user, per participant, per project, per form or per report?
  • What happens when a donor funds a new programme mid-year?
  • Are implementation, data migration and training separate from the licence?
  • Does the price include offline sync, SMS, device management and support in Bangla?
  • How are donor-specific report templates priced?
  • What is the annual support commitment, and what is charged as a change request?
  • If the grant ends, can the data be exported and the account closed without losing records?

Compare total cost across the grant cycle, not only the first-year licence. Devices, connectivity, training refreshers and staff time for data cleaning are part of the programme budget.

Pilot design

Run the pilot in one programme, one district and one reporting cycle. Include at least one field team that works offline and one donor report that must be produced from the system.

  1. Week 1: agree the indicator set and the participant identity rule; prepare the data migration sample.
  2. Weeks 2–4: configure forms and access, train field staff and run a paper-to-system comparison.
  3. Weeks 5–8: collect live data, test duplicate handling and produce the donor report.
  4. Week 9: review data quality, staff time, support tickets and protection controls; decide to proceed, change or stop.

Acceptance criteria should include the percentage of forms synced without manual correction, the time to produce the donor report, the number of duplicate participants and the number of access exceptions. These are measurable and they matter after the pilot, not only during it.

Data ownership and exit

  • Who owns participant data, and who is the controller or processor?
  • Can all records be exported in a usable format, including attachments and audit history?
  • What happens to data at contract end, and how is deletion evidenced?
  • Where is data stored, and are subprocessors disclosed?
  • What support is provided during a transition to another system?

Common procurement traps

  • Buying forms before indicators. A good form that produces no reportable result is a data collection cost with no decision value.
  • Piloting with a friendly team. Test in the district with the weakest connectivity, not the one closest to the head office.
  • Ignoring the grant cycle. A multi-year licence that outlasts a one-year grant creates a cost without a budget line.
  • Treating training as a one-off. Field staff turn over; budget refreshers in every grant.

Our Custom Software & Integrations division builds programme data systems with offline collection, consent records and donor reporting. The pricing page explains how discovery, build and support are scoped. For the operational problems this system must solve, read NGO programme data management: problems and fixes.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes