In this lesson you
- Read one document's history, line by line
- Told Proof's own work apart from a person's
- Found one document's history by searching for it
Transcript
Who fixed what, and when
The remediation ledger. When someone asks what was done to a document, and who did it, you want an answer you can point to. That answer is the Remediation Ledger, here under Reports. It's the history of your library, document by document. Every step is written down in order, with who took it. Each document gets its own card, and the most recently active documents come first. Read a card from top to bottom, oldest step first. Each line has three parts. When it happened, who did it, and what happened. The Who column names a person, or it says Proof. Proof means the platform did that step on its own. Anything a person did carries their name. The top of each card says where the document stands today. On the right is its verdict. Compliant, Failed, or Certification pending, which means a person still has a check to make. A certified document also shows its certificate ID, just before the verdict.
One document's story
Let's read one card. Riverside Park Reopens arrived with seven failing checks. A failing check is a confirmed accessibility problem in the file. Then Proof's automatic pass ran. That's the line Baseline Auto-Remediation. It ran its fixers, the automatic repairs, in two rounds, and six checks were resolved. Then Jordan Lee applied fixes to the picture descriptions. That resolved the seventh check. Last, Jordan approved the document, and Proof issued its certificate. So seven problems came in, and all seven were cleared. Proof cleared six on its own, and a person cleared one. That's the split an auditor asks about, and the ledger shows it line by line. The next card shows that a clean start doesn't always mean nothing to do. Patient Rights and Responsibilities arrived with no failing checks. But reading order is something only a person can confirm. So Jordan confirmed it, and then approved the document. Then Proof issued its certificate. If you want to see the document behind a story, select its title. It opens that document in the Library.
Find one document
In a large library, you'll usually come here for one document. Maybe an auditor named it, or a colleague asked about it. Type part of its title, its file name, or its web address in the search box. To read a whole folder's history instead, choose a folder. Let's find the clinic hours notice. Now the page shows only that document. The line under the totals confirms it. One document matching Clinic Hours, of eight in this corpus. Clinic Hours and Walk-ins was added to the library with one failing check. Nothing has happened since, so it's still marked Failed. That tells you it's waiting for someone to fix it. Your search is part of the page's address. So you can copy the link, and send a colleague straight to this history. You can also arrive here from the Evidence Register. Each certificate there has a Ledger link that opens its document's history.
Take it with you
When you need the history outside Proof, for an audit file or a records request, choose Ledger CSV. While a search is on, the button reads Ledger CSV, this scope. The file then holds only what you're looking at. It's a spreadsheet with one row per step, giving its time, who acted, and what happened. For a printed copy of this page, choose Save as PDF. The ledger covers work on documents. For everything else people do in Proof, like invitations and settings, see the activity log, which has its own lesson. Now you can show what was done to any document, who did it, and what's still waiting.
Recap
That's the end of this lesson.
Maple Ridge Community Health, its documents and its people are fictional, made for these lessons.