What Joripo is · Joripo documentation

Joripo is a platform for collecting survey data and keeping it trustworthy while fieldwork is still running. You design a questionnaire as an XLSForm workbook, field teams fill it in on Android phones or in a web browser, and every submission is stored on your Joripo server and checked the moment it arrives: interviews that were too fast, GPS points that make no sense, an enumerator whose answers never vary. Supervisors see what the checks found on the same day, review and correct the data, and export it ready for Stata, SPSS, R or Excel.

The parts of Joripo

Part	Who uses it	What it does
The web console	Owners, managers, reviewers	Design and test forms, manage phones and people, watch submissions and quality findings, review and correct, export. It runs in any modern browser.
Joripo Collect	Data collectors	The Android app for fieldwork: works offline, keeps drafts, sends finalized forms when there is a connection. It runs the same form engine as the console's tester and web forms.
ODK Collect	Data collectors	Joripo speaks the standard OpenRosa protocol, so ODK Collect works against it unmodified, with a device key or (where the owner allows it) an email and password.
Web forms	Respondents, data collectors	Any deployed form can be filled in a browser from a link, signed in or (if you allow it) anonymously.
Joripo Desktop	Owners, managers, reviewers	A Windows app that keeps a copy of a workspace's data on your computer and makes the same export files without a connection.

How the data moves

A phone, a web form or the tester sends a submission to your Joripo server.
The server writes it to its file store first. The files are the record: the database is an index over them, and it can be rebuilt from the files if it is ever lost.
The submission is indexed, and the quality checks that look at one interview run on it straight away. Checks that compare interviews or enumerators run when you ask for them, over a whole form.
Findings appear in the console under Monitor, with the interview they are about.
When you export, you get the data as it stands after review and correction.

If you already use XLSForm

A team that already writes XLSForms can bring them: Joripo reads SurveyCTO-compatible and ODK workbooks with their functions, server datasets and pulldata(), has review and correction, and exports the WIDE CSV in the SurveyCTO-compatible layout with its Stata import do-file, so existing analysis pipelines keep working. Such a workbook usually deploys on Joripo as it is; Compatibility with SurveyCTO and ODK lists the exceptions.

What Joripo adds is the quality layer: twenty-eight High Frequency Checks that run as data arrives, enumerator scorecards, quotas, back-check comparison and a quality verdict carried into the export (n_flags).

The workflow in four steps

Design: upload your workbook (or build the form in the browser), attach media and preload files, test it, deploy it. See Designing forms.
Collect: sign phones in to Joripo Collect, give ODK Collect a device key, or share web-form links. See Collecting data.
Monitor: watch submissions arrive and work through what the checks found. See Monitoring and quality checks.
Export: download the data as CSV, Excel, Stata or SPSS, or keep a copy on your computer with Joripo Desktop. See Exporting data.

What Joripo does not do

So that nothing here is a surprise later, these are not built: telephone interviewing (CATI), sampling, workflow automation, connectors that publish data to cloud warehouses, an offline console, a supervisor mode on the phone, SurveyCTO-style form encryption with a public key (a form that asks for it is refused rather than stored in the clear), training modules, automated billing, and moving cases from one phone to another. Where a feature exists but is incomplete, its page says so under the title.