KEEP THE DECISION. KNOW WHEN TO REVISIT IT.
One source changed.
What needs another review?
Keep the earlier review. Update the source you are allowed to use. See which tests and decisions need a person to look again.
Runs in this browser. Nothing is submitted. Save your packet before closing.
START WITH A SUPPLIED PACKET
Choose an example or start your own.
Loading the fictional packet…
YOUR CURRENT REVIEW
Checking the supplied records…
WHO NEEDS TO DO WHAT?
The retest queue
KEEP THE UNCERTAINTY VISIBLE
What remains open
Only relationships someone has supplied can be followed. Missing or excluded records stay visible.
01 / UPDATE A CURRENT SOURCE
What changed?
Choose a source and enter its current version and text. Use only sources you are allowed to supply. Permission and status are declarations, not verified rights.
Read the retained source
02 / RECORD THE RETEST
What did a person observe?
Run the test using your approved process. Record the expected behavior, the observed result, and the outcome you are declaring. This tool does not run the test or judge whether the answer is correct.
Read the retained test and review
Saving a test leaves its earlier fingerprint in place. It does not create a new review.
03 / RECORD A HUMAN REVIEW, SEPARATELY
A person owns this declaration.
For the selected test, record the review that actually happened. Save the declaration first. Bind it only after explicitly confirming that a person reviewed this current test and its supplied sources.
A fingerprint records the supplied context and declaration. It is not a signature, verified identity, authority, or proof that the review occurred.
Requires a declared passed test, accepted review, named reviewer and reference, valid dates, and complete current sources with permission declared. Other tests and scope issues can still need review.
Workflow date, owners, decision, and declared links
Changing the workflow date can expire a declaration. These are supplied names and conclusions, not verified identities or a recommendation to proceed. The guided editor keeps existing IDs and links fixed.
Apply or discard edits first. A check can report unresolved work; it does not approve the institution's decision.
Inspect, import, or change the complete JSON packet
Complete import replaces both supplied snapshots after validation. Keep an exported copy of the earlier packet. Guided edits never replace the retained baseline. A JSON draft clears the result immediately; an invalid draft stays visible and blocks guided actions until you fix or explicitly discard it.
Maximum 1 MiB. No automatic PDF extraction, semantic answer assessment, directory scan, or core import. If you use the package through an assistant, its provider may process conversation and tool data under that account's terms.
A CHECK OF THE FILE. A DECISION FOR THE INSTITUTION.
A retained match
is a declaration check.
A matching review means the supplied test, sources, reviewer declaration, and dates match their retained context. A changed or expired record returns to a human reviewer. Undeclared dependencies cannot be discovered.
Fingerprints identify supplied text. They do not verify a person, prove authority, or establish that a review happened. Permission declarations are not verification of source rights.
No core connection, compilation, execution, financial action, certification, legal opinion, achieved savings claim, live monitoring, reminders, cloud history, or model activation.