Sending the list to a reviewer, and bringing it back
Quick answer
Export the review list, let somebody who knows the documents fill in a column, and import their file — they never need a WordPress login.
The person who knows which handbook belongs to which page is usually not the person with admin access. This is the way round that without giving anybody an account.
Exporting
From Review & Resolve, export as CSV or XLSX. The file carries one row per staged file, with the filename, the proposed post, the confidence, the current status and a notes column.
A collapsible panel on the same screen documents the columns and the valid status values, and it is generated from the plugin's own status list rather than typed — so it cannot drift out of step with what the importer will accept. There is a copy-to-clipboard email draft beside it.
Every exported value is escaped against spreadsheet formula injection: anything beginning =, +, - or @ gets a leading tab. The file exists to be opened in Excel, and an untreated value would be evaluated rather than read.
What the reviewer does
They change the matched post, the status, or the notes. They do not need to understand WordPress — the columns are filenames and titles.
Importing
Upload their file on the same screen. Rows are matched by filename, which is why duplicate uploads are stored under their own unique names: two rows sharing a filename would send one reviewer's decision to the wrong row and silently drop the other.
Two things the importer will not do.
It will not touch a row that is already Combined, Replaced or Verified. A reviewer working from a file exported an hour ago should not be able to undo work that has happened since — and an earlier version of this plugin let exactly that happen, silently reverting a combined row to an active status.
It will not apply a status it does not recognise. Anything outside the documented vocabulary is reported rather than guessed at.
Undo
Every row an import changes is recorded before it is changed, tagged with that import's own identifier. The success notice carries an Undo this import link that restores every touched row to its pre-import state.
Single-level undo, not full history: it undoes that import, not the one before it. But it is enough to recover from a reviewer working off the wrong copy without hand-writing SQL, and the record is written and checked before the change it describes — so an import that cannot be undone is one that does not happen.
The Import history table on Review & Resolve lists every import with its file, its time and how many rows it touched.
File formats
.csv and .xlsx. XLSX is read without any library — the first sheet only, no merged cells, no formulas. Both are normalised to the same shape before anything is applied, so the rules above hold whichever you send.