JoripoAbout Joripo
Built by people who cleaned survey data the hard way.
Joripo comes out of years of running high frequency checks after the fact, in Stata and R, on data that had already gone stale. We wanted a platform that collects the data and checks it in the same place, as it arrives, so we built one.
Why Joripo exists
The checks were right. They were just too late.
On most surveys, quality checks happen somewhere else. Interviews come in from the field, someone downloads them, runs a do-file or an R script, and sends a list of problems back to the supervisors. By the time the list arrives, days have passed, the enumerator is working in another district, and the respondent cannot be asked again.
Joripo puts those checks where the data arrives. Twelve of its 28 built-in checks run on each interview the moment it reaches the server, and the rest compare across the whole dataset whenever an owner or manager runs them. Every finding says in plain words what was entered, what was expected and which enumerator was involved, so a supervisor can act on it the same day.
Around the checks sits the rest of what a survey needs: XLSForm design and testing, offline collection on Android, case lists for repeat visits, and exports your analysts can open straight away.
Joripo's console, showing a demo workspace with synthetic data.
Our purpose
The survey platform for a more informed tomorrow.
Decisions about health services, farm support, schooling and social protection are made on survey data. When an interview is rushed, a module skipped or a household counted twice, the error does not stay in the dataset. It travels into the report, and from there into the decision.
A more informed tomorrow starts with today's interviews. We build Joripo so that they are:
- checked while the field team can still go back,
- protected for the people who answered them,
- and handed to analysts in files they can trust.
What we believe
Six principles behind every decision in Joripo.
They decide what we build first, what we leave out, and how we describe the product to you.
Quality is a field decision
The best time to catch a bad interview is while the team is still in the area. Checks that run days later can only tell you what was already lost.
Ship what works, say what does not
A screen that looks finished but does nothing helps no one. If something is not built yet, we say so plainly, on this site and in the product.
Data belongs to whoever collects it
Each organisation's data is walled off from every other. The organisation decides who sees identifying answers and which partner reaches which workspace, and its data leaves in the formats analysts already use.
Familiar to XLSForm users
Teams should not have to relearn their tools. Joripo reads the XLSForms teams already have, writes the WIDE CSV in the SurveyCTO-compatible layout, and accepts ODK Collect over OpenRosa.
Built on open foundations
Forms run on ODK's open-source XForms engine, extended by Joripo, so a form behaves the same in the browser tester, in web forms and in Joripo Collect.
Free to start, fair to grow
Every organisation can collect 5,000 submissions a month for free. Paid plans have every feature on every submission and unlimited team members. See Pricing.
Get in touch
Talk to us about your programme.
We read every message. Tell us what you are planning and we will answer plainly, including when Joripo is not the right fit.
- Request a demoA walkthrough with a form like yours, not a generic tour.
- Pricing for your programmeTell us your forms, interviews and months of fieldwork.
- Moving from another toolBring the XLSForms you use today and we will look at them with you.
- Self-hosting and larger deploymentsRunning Joripo on infrastructure you control is arranged case by case.
See what Joripo would do for your next survey.
Send us your questionnaire or describe your study. We will walk you through Joripo with a form like yours: design, field collection, quality checks and export.
Already using Joripo? Log in to your server.