Doing reviews
Find what needs attention
Section titled “Find what needs attention”Two places tell you what is waiting:
- The dashboard shows a Needs review count: the number of records that are in review or flagged as suspect, within the regions you can see.
- On a survey type’s records table, filter chips narrow the list to a review state.
The filters are All, Draft, In review, Approved, Rejected, and Flagged. More appear when they apply: Off-station (when the survey records a location) and Data outliers (when it records numbers), covered in Data quality, and Duplicates (when a field is unique), covered in Reviewing duplicates.
Choose the columns
Section titled “Choose the columns”The table shows the first few fields as columns to start. Use Columns above the table to pick which fields appear. The choice is kept per survey type on your own device, so you can tailor the table to what you are working on without changing it for anyone else. The full record, with every field, is always there when you open it.
Review one record
Section titled “Review one record”The Review column shows each record’s state as a colored badge (with a flag marker if it is flagged). Open a record to review it. Its drawer shows:
- the current state,
- a note field (a note is required to reject),
- the action buttons you are allowed to use, and
- the full history of what happened to the record and who did it.
What you see depends on your role: members get Submit for review and Flag; admins also get Approve, Reject, and Reopen. Viewers see the history but no buttons.
Correcting a collected record
Section titled “Correcting a collected record”A record collected on a device can be corrected here. In the review drawer, Edit record opens the record’s fields, prefilled; save your changes and they are written back as a headquarters correction, kept in the record’s history. Only device-collected records can be edited this way: a published record cannot be edited (the public archive is permanent), and a record with an open sync conflict must be resolved first.
If a field worker also edited the same field on their device and has not synced yet, your correction and their edit meet as a sync conflict on their next sync, which you settle in Resolving conflicts.