Monitoring quality

The Monitor tab is where you watch data arrive and act on its quality. Joripo checks every submission the moment it lands; what the checks find appears here as quality flags.

Submissions

Form submissions and dataset data lists your forms with their deployed version and number of complete submissions. Each form has a strip of actions:

* Monitor form data asks which submissions to include (all, a random subset, or the last few days) and opens the form's Data Explorer: a summary of every question that fits its kind (counts and percentages of each choice, mean, median and a histogram for numbers, a time line for dates, the most frequent typed answers), how many answered and how many did not, a cross-tab of two questions, a search and filters. Every count opens the submissions behind it, one at a time, as questions and answers. Save keeps your view of the form for next time, Reset forgets it, Download gives the summaries, the selected submissions (with the export permission) or the view itself. * External viewers opens the workspace's sharing with people outside your organisation. * Review workflow opens the form's review queue (approve, reject, correct). * Purge form data deletes submissions from the server after a backup and a typed confirmation. * Look up by key opens one submission by its KEY. * Advanced mode is the spreadsheet of every submission, newest first, 50 to a page, with the form's questions as columns and the technical ones on request. * Translations & Transcriptions opens the form's labels in its other languages; automatic transcription of audio and translation of answers are not available on this server.

Column headings are the question labels, in any of the form's languages (Labels in), with the variable name underneath. Choice labels shows what a choice says instead of its code.
A file answer (photo, audio, signature) is a small link that opens the file.
System and device fields, calculated fields, repeat counts and each choice's 1/0 column are behind Technical columns. A wide form shows 30 columns at a time; Jump to goes straight to a section.
Filter by enumerator, quality (flagged or clean), the days received (in the workspace's time zone) or a search over the answers, the enumerator and the KEY. Export current data downloads exactly the submissions the filters select, every page of them.

Click a submission's date to see every answer, its attachments and its flags, and step to the older or newer one. Look up by key opens one directly, and Submission statistics shows submissions over time.

Quality findings

Each finding names the check that raised it, its severity and the enumerator, and says in plain words which question, what was entered and what was expected. Technical details under it (for owners, managers and reviewers) has the variable names, the number behind the finding and the rule that raised it. A finding about another interview (a duplicate, a copied answer) links to that interview too.

Show Open, Resolved, Dismissed or All findings, 50 to a page. Write a note if you like, then Resolve (the problem is dealt with) or Dismiss (it is not a problem); Re-open puts one back. Who did what, when and with what note is shown under the finding, every change is kept in its History, and the change is recorded in the audit trail. The list refreshes on its own every 15 seconds, but not while you are writing a note.

When the checks run again:

a dismissed finding stays dismissed unless it gets materially worse: its measure (how far past the limit, how unusual) is at least 50% worse than when it was dismissed, or the answer now crosses a hard limit;
a resolved finding about an enumerator or the whole form re-opens if the problem comes back in interviews that arrived after it was resolved (for a daily cap, only when that same day gets more interviews). A resolved finding about one interview re-opens only if it gets materially worse, since the interview's answers do not change.

A finding that is still open is brought up to date each time the checks run, so you always decide on its current numbers. A re-opened finding says "Re-opened by the checks" and why. Times are shown in the workspace's time zone. An empty list says why it is empty: no interviews yet, checks not set up or not run yet, or checks switched on but skipped because the questions they read are not mapped. Only when the checks ran and found nothing does it say there is nothing to review.

The Quality report (Excel; on each form's card in Monitor and under Export) has every finding of the form with its status, who reviewed it, when, the note and the technical details, then the form's field-work indicators:

Indicators: completed surveys, the average per active collection day (days with at least one interview) and per calendar day (first to last collection day), the average per enumerator (enumerators with at least one interview; interviews with no enumerator are counted on their own), the median and mean interview duration, and how many durations were left out (a start or end time missing, an end before the start, more than 24 hours). Every average shows its numerator and denominator.
Enumerator by day: each enumerator's completed surveys on each interview date, with totals.
Sections: each top-level group and repeat of the deployed form, how many questions it asks (questions that collect data, notes, calculations and metadata counted apart) and, when the form has a text audit, the median and mean time spent in it. Without a text audit there is no time per section — Joripo does not estimate it — and the sheet says to add a text audit field.
Text audit summary: how many interviews have a text audit, and the median and mean seconds on each question.

Completed means every submission the server has received: a phone sends a form only once it is finalized, so drafts are never counted. An interview's date is the day it started, in the workspace's time zone (its end, when it has no start; the day the server received it, when it has neither — the report says how many). The card in Monitor shows the form's pace in short: interviews a day over its active days, and per enumerator. Text audits, processed (one readable workbook) and Text audits, raw (the files as the phones sent them) are offered beside the report for a form with a text audit field. The workspace's Quality flags, every form report has the findings only. Export's Joripo, with quality-flag columns layout carries each submission's number of flags (n_flags), so you can drop flagged rows in your analysis.

Automated quality checks

The High Frequency Checks look for problems while fieldwork is still running: interviews that are too fast or too slow, GPS points that are missing, inaccurate or implausibly far apart, travel speeds no one could manage, straightlining, high refusal or "don't know" rates, skip patterns not followed, answers that contradict each other (dates and times included), numbers outside the range you expect or that is possible at all, rosters filled in too few or too many times, numeric outliers, numbers heaped on round values, duplicate IDs and near-duplicate submissions, digit patterns that fail Benford's law, and back-checks: a separate back-check form's answers compared with the original interviews, matched on a household or respondent ID, per question, enumerator and back-checker. Days are counted by when each interview happened, in the workspace's time zone. Each enumerator is compared with the rest of the team, not with a team average that includes them.

Enumerator scorecards summarise each enumerator's flags and output.
Quota and stratum tracking shows progress against your targets. An owner or manager sets the targets right there, a stratum and its target per row (the strata already seen in submissions are offered), and removes one with Remove.
Quality checks in force lists, form by form, which checks run and their thresholds — each form's own settings, or the workspace's when it has none.
Run HFC checks runs the checks you choose over all of a form's data at once and reports what they found.

The checks need to know which questions hold the enumerator, start and end times, GPS and stratum. If a check never fires, look at Which question holds what at the top of the form's quality-check settings (HFC checks), where the checks' thresholds are set too.

Purging data

An owner or manager can Purge some or all of a form's submissions, by date or by key. You review exactly what will be deleted and confirm by typing the number of submissions that will go; a backup is always made first, and other forms are never touched. Collect has the same Purge data on each form.

Field monitoring

Field monitoring (in a workspace's navigation, for reviewers and up) turns a form's data into the numbers a field team is run by. A monitoring project reads one source: a Joripo form of the workspace (read as submissions arrive), a SurveyCTO form (pulled on a schedule or with Sync), or a CSV, Excel or Stata file you import. Owners and managers set it up, in this order:

Variables: what each field is for (labels, roles, which one identifies a household or a respondent, which are hidden or not exported). Derived variables compute new values with XLSForm expressions (${age} >= 18 and selected(${services}, 'anc')).
Indicators: a count, a percentage, a sum, a mean and so on, each with who is counted (the denominator), what qualifies (the numerator) and what happens when an answer is missing — a missing answer is never counted as zero. Build the conditions with the visual builder or write them; the preview shows the value on the data now and where every record went.
Rules: what to look at — a duplicate household ID, an interview too short, an answer outside its range, an unusual value, poor GPS, an enumerator whose rate is out of range. A rule is tested on the data before it can be switched on. What it finds goes to Review, where a reviewer confirms a finding as a real problem, marks it not a problem or corrected, with a note; every decision is kept. A finding is something to check, not a verdict on anyone.
Productivity: enumerators down, days across, the interviews each did each day as the project counts them (every submission, completed interviews, or unique households), with totals, days off and leave never counted as zeros, and the records behind any cell.
Targets, Dashboards (KPI cards, charts, tables, the matrix, findings, built by dragging and resizing, with filters and a table view of every chart), and Sheets (tables written to a Google spreadsheet; Joripo only ever writes the tabs it made).

A dashboard is seen by the workspace's team once it is published, and by someone the workspace was shared with only when it is also shared with external clients and their access includes Quality. Published dashboards are listed at the top of Monitor.

Downloading a chart

Every chart, map and matrix on Monitor has a Download control: Submissions, last 30 days (Monitor, Activity and a workspace's Overview), Daily submissions by form (a workspace's Quality page and the Legacy Monitor tab), each chart, map, target progress line and productivity matrix on a field-monitoring dashboard, and the Productivity matrix.

Picture (PNG) is drawn in your browser from the chart on the page, at twice its size so it stays sharp on a slide or in print. Under it is what it shows: its title, the workspace, form or dashboard, the period and filters chosen, and "Generated" with the date and time. Picture (SVG) is the same as a drawing that stays sharp at any size. Nothing is sent anywhere to make them.
Numbers (CSV) are the chart's numbers from the server, counted for you exactly as the chart is: the same workspaces, the same filters, the same masking of names and codes. A chart of counts downloads counts, never the submissions behind them. A CSV opens in Excel, and no cell is ever read as a formula.
On a dashboard, Download all makes one .zip with every item's numbers (CSV) and every chart's, map's and matrix's picture (PNG), of every tab, numbered in the dashboard's order, with a note of the filters it was made under. PDF / Print prints the dashboard as you see it.

A file is named by the chart's title and the day (Field-overview-By-district-2026-10-24.png), never by a filter's value or anything a respondent typed. A shared dashboard link offers the same downloads, each computed as the link shows the dashboard. Someone a workspace was shared with downloads only what their access shows them: the daily chart's numbers need Quality.