- Home
- Documentation
- Review and correct
- Statuses and the review workflow
Review and correct
Statuses and the review workflow
Partly builtApproved, rejected and awaiting review; turning a form's review workflow on; and deciding on many submissions at once.
Joripo documentation · https://joripo.com/docs/review-and-correct/review-workflow
Statuses
Every submission is approved, rejected or awaiting review. A submission nobody has reviewed counts as approved. Open a submission and use Review at the top of its page to approve it, reject it or set it back to awaiting review, with a comment if you like. Approving a never-reviewed submission explicitly is recorded as a decision of its own.
The review workflow
Each form has a review workflow setting, on its review page (Data, then Review on the form's row):
- off (the default): new submissions arrive approved;
- on: every new submission arrives awaiting review, so nothing reaches a default export until someone approves it.
Turning it on or off never changes a submission already received. A submission that arrives while the workflow is on is recorded as awaiting review before anything else happens to it; if its indexing fails, the server records it as awaiting review when it catches up, so a submission never becomes approved because something broke.
The review page
The review page lists a form's submissions by status (Awaiting review, Approved, Rejected or All), newest first, with how many corrections and open quality findings each has. Tick some (or the box at the top for the whole page) and Apply to the ticked submissions to approve, reject or set them awaiting review in one go, up to 500 at once, with one comment kept on each.
Who can do what
- Reviewers, managers and owners of a workspace approve, reject and correct its submissions. With restricted workspaces on, it is the person's role in that workspace that counts.
- Owners and managers turn a form's review workflow on or off.
- Someone the workspace is shared with sees each submission's status and the corrected answers, never the controls, the original answers, the comments or the history.
- Data collectors never open the console.
Not built yet
All or nothing per form. With the workflow on, every new submission awaits review. Sending only some submissions for review, chosen by a quality check's result or as a random share, is not built yet.
Rejected and awaiting-review submissions still count in the quality checks, the Data Explorer and the lists: the checks are about fieldwork, which happened.