Remediators · Lesson 6.1

How a review session works

The session screen every Review lane shares: keys, flags, Undo, AI pre-reads, and what an attestation records.

4:32Captions and transcriptRecorded October 2026For people fixing documents

Watch the lesson

In this lesson you

  • Worked through a session item by item, with the help, the rail and the keys
  • Flagged what fails, and attested what passes, in your name
  • Confirmed AI-cleared documents only after reading their reasons

Transcript

One question, many documents

How a review session works. When the same question waits on dozens of documents, how do you get through them without losing your place? You answer it once per document, one after another. That's a review session. Sessions start from the cards on the Review page. The cards that finish the most documents come first. The green chip, 3 to Compliant, counts the documents where this is the only open check. Greyed cards have nothing waiting today. Our example is Sensory characteristics. Judging it has its own lesson, so here we watch only the session.

Finding your way

Inside, the help opens first. It says what you're deciding, and lists the keys, which every lane shares. To bring it back later, press the question mark, or choose the i button. To see what's left, press Q. The queue rail lists every document in the session. To see a document in full, in a new tab, choose Open.

When something fails

The session opens on the documents most likely to fail. The AI flagged a likely issue here, so this one comes first. This document has other open checks, so its chip offers a review page by page, which is quicker when checks share pages. Not every item passes. Suppose this instruction does rely on its position alone. Choose Flag issue, or press X, and say why. The note is required, so whoever fixes the document knows what to change. A flag is saved in your name, and it fails the check. The document reads Failed until it's fixed. So Enter does nothing here. The square bracket keys skip to another document, and a skip records nothing. In the rail, the document moves to Flagged as failing. If you flagged it by mistake, choose Clear my flag. Only you can clear yours.

Before you judge

Before you judge, read the chips beside the document's name. Only check left means this check is all that stands between the document and Compliant. Confirm it, and the document is done. The AI chip says what Proof's AI thought, and how sure it was. Treat it as a hint, not an answer.

One item at a time

Now the judging itself. Your decision sits at the bottom right. The filled button, Not sensory-only, says this sentence passes. The outline button, Flag issue, says it fails. Enter presses the filled button, and the legend at the bottom shows its label. The arrow keys move between sentences. Plus, minus and zero zoom the page. On the last sentence, the button reads Not sensory-only, attest. Nothing is saved until this press. If you try to leave before it, with Escape or a bracket key, Proof asks first.

What an attestation is

That press is an attestation. It's a record, in your name, that you looked and the document meets this check. It's tied to this exact version of the file. Then Proof checks the document again, so its status catches up. A message says Sensory characteristics verified. For eight seconds you can take it back, with Undo or the U key. Undo removes only your own record, and returns the document to the queue. A teammate's record reads Attested by, with their name, and has no Undo.

Several at once

If you've already checked several documents, you can record them together. Tick them, and choose Attest 2 reviewed. The dialog records them in your name, but leaves out spot checks and flagged documents. We haven't read these two, so we'll cancel. Reading order has no checkboxes. Its review is the page walk.

When the AI found nothing

The next two show up most in the reading-order session, so we'll look at them there. Some documents give the AI nothing to find. Proof holds back one in ten of those as a spot check, for you to read in full. If you find something it missed, choose AI missed an issue. That's how Proof learns whether to trust its AI. The rest wait under AI-cleared, and nothing is recorded for them yet. Confirm all 2 AI-cleared lists them with the AI's reasons. Read them first, because confirming records each one in your name. All 2 are now attested. Now you can work through a session item by item, flag what fails, and record only what you've checked.

Recap

That's the end of this lesson.

Maple Ridge Community Health, its documents and its people are fictional, made for these lessons.

Try what you just watched.

Free, no account: a verified email, one document per email, up to 10 pages and 50 MB. Get the remediated file and its verification record, and see which checks still need a person.

Longer document? Request an assessment.