Sign in Sign up

Your data

Collection is the easy half

Nobody pays for data collection. They pay for what comes out at the end. Exports are built as a first-class part of the system, not bolted on once the app works.

From rows to columns

Because fields are rows in the database, an export has to be pivoted back into the shape an analyst expects. Writing that once, properly, is the difference between a product and a demo.

record_values — one row per value recordfieldvalue 1041referenceWP-233 1041operationaltrue 1041flow_lmin18.4 1042referenceWP-234 1042operationalfalse 1042flow_lmin0.0 pivot export — one column per field recordreference operationalflow 1041WP-233 true18.4 1042WP-234 false0.0 Two records. Six stored rows on the left, two analysable rows on the right.
Diagram: values stored one per row are pivoted into a table with one column per field.

One column per field

Spreadsheet exports arrive shaped the way an analyst expects, not as rows of field-name-and-value pairs.

Coordinates you can map

Decimal degrees to six places, with the recorded accuracy kept alongside, so a bad fix is visible rather than silent.

Per-device access

Access is granted per device, not per shared password. A phone that goes missing is revoked on its own without disturbing anyone else.

Photos stay attached

Every image keeps its link to the record and the field it was taken for, so an export is never a folder of anonymous files.

Set up your first form today

If you run field teams and the offline problem sounds familiar, create an account and build your first form in minutes.