SAYNIS FieldOps
Offline-capable field data collection with programme reporting for NGOs working in low-connectivity areas.
Field data tools generally assume connectivity returns within hours. In much of the Horn it may be days, on a shared device, in a language the form was not written in.
FieldOps is being built for that case first: long offline periods, syncing that does not overwrite anyone's work, checks at the point of collection, and export in the formats donors actually require.
It is not a general survey tool. It is built for programme teams reporting against indicators on a funding cycle.
What SAYNIS FieldOps is being built to do.
Offline collection
Designed for low-end Android handsets, including shared devices.
Long sync windows
Multi-day offline periods with conflict resolution on return.
Validation at entry
Errors caught in the field, where they can still be fixed.
Beneficiary records
Access scoped to what each role genuinely needs to see.
Indicator tracking
Programme indicators recorded against your logframe.
Donor export
Reports generated in each funder's required format.
Supervisor review
A queue for checking submissions before they are final.
Four steps, end to end.
- W1Assign
Assign forms
Supervisors push the right forms to the right field staff.
- W2Collect
Collect offline
Data is captured and validated with no connection at all.
- W3Sync
Sync and resolve
Records reconcile safely when a connection returns.
- W4Report
Report
Indicators export in the formats each donor requires.
- Android, including shared and low-specification handsets.
- Multi-day offline operation as the normal case.
- Multilingual forms for the languages field staff work in.
- Programme teams reporting to more than one donor.
- Android application built for small install size.
- Conflict-aware synchronisation over unreliable networks.
- Node.js and PostgreSQL with a documented API.
- Field testing on real hardware, not emulators.
What people ask about SAYNIS FieldOps.
The design target is days, not hours — a full field rotation without a connection, then a safe sync when one returns.
Low-end Android handsets, including shared devices. Requiring staff to have a modern phone would defeat the purpose.
Access is scoped by role, sensitive fields are restricted, and a device holds only what its user needs. Retention and access rules are agreed with you in writing.
Yes. Indicators are stored once and mapped to each donor's export, so a second funder does not mean collecting the data twice.
It is in development. We are taking a small number of design partners, and we will tell you quickly whether we can take yours on.
Request a preview
Design partners get early access and direct influence over what we build. We can only take a few at a time, so we will tell you quickly either way.