Understand review history
Use review history to answer two questions: what did the reviewer decide, and what did the application report afterward? Read those events separately. One does not prove the other.
In Inbox → Assigned reviews, choose View review history on a completed queue to inspect its records. Each record identifies a policy escalation review or session investigation. A completed queue record does not prove that the linked human review request is complete.
Choose Open session review to check the final decision owner, evidence, and application status. Closed automatically means no person recorded a queue decision. Its saved reason explains why it closed.
Read the events that happened
The timeline shows only recorded activity. Depending on the request, you may see these events:
- Review requested or Review routed: a person needs to respond.
- Reviewer assigned: a reviewer now owns the request.
- Response recorded or More information requested: the reviewer has responded, or the request needs more information.
- Decision ready to send or Decision sent to application: the response is on its way to, or has been sent to, the application.
- Application received decision: the application saved the response and is handling the next step.
- Application resumed, Application ended the action, Application remains paused, Application replaced the action, or Application could not continue: the application reported the result.
Only the reported result can confirm that the application resumed, ended, stayed paused, replaced the request, or could not finish. A recorded response or sent decision does not prove that the application acted on it.
Ask for more information
When you ask the application a question, the review stays open on the same page. VeriProof sends the question to the application and checks for its reply while you keep the review open. When the application provides updated information, the current request and its earlier questions appear together.
Your question is sent to the application. A private review note is not.
VeriProof does not create another Inbox item or email for each delivery step. A single reminder may update the existing review item near its deadline. If responsibility moves to another reviewer, the old item closes and the new reviewer receives the request.
Check the request within the session
One session can have more than one request in progress. Open the request that needs attention and read its events, rather than treating one completed request as the outcome for the whole session. A mixed session has requests at different points in the flow.
Interpret missing events
The timeline shows recorded events, not assumed stages. A missing event does not establish that a step completed or failed. For example, a saved response without an application result means VeriProof has not received that result. Check application processing before concluding that work resumed.
When no activity is available yet, the timeline says so. It does not fill the space with stages that do not apply to that request.
Do not change a review record to make the timeline look complete. Resolve the application processing or reporting failure, then let the resulting activity appear in the timeline.
What each role can see
| Role | What the history helps them do |
|---|---|
| Administrator | Check assignment, delivery, and recovery status. |
| Developer | Trace the checkpoint, callback, receipt, and application result. |
| Governance Engineer | Review policy, evidence, and investigation context. |
| Compliance Officer | Review the decision, its basis, and the audit record. |
| Business Owner | See a material business outcome without technical detail. |
| Auditor | Inspect the read-only decision and activity record. |
If your role has no review responsibility, the portal does not show an empty Human Review panel or an unrelated review metric.
For administrators and developers
The collapsed technical section contains the delivery, receipt, and correlation records needed to investigate a failed delivery to the application. Administrators can use the scoped recovery controls when they have the required access. Developers can use the same records to trace application processing and report the final result. These details are not part of the reviewer or business-owner view.
For a stopped delivery, see Operate application callbacks. For application restart and checkpoint recovery, see Recover a long-paused continuation.