Use audit logs and chain of custody
Trace hashes, events, source snapshots and evidence movements across the module.
Before you start
Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.
Follow these steps
- Go to the chain-of-custody workspace.
- Search by entity type, ID or reference.
- Check event order and previous-hash linkage.
- Go to the source record or artifact.
- Investigate any missing or inconsistent event before relying on the pack.
Fields, rules and limits
- The chain records event ordering and hash linkage within the application. It is not externally anchored or immutable against an administrator who can rewrite both records and hashes. Investigate gaps against original evidence and operational records.
Check it worked
The linked entity, saved state, dates and evidence match the intended task.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
Does a parsed document count as approved?
No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.
Is the generated PDF the original certificate?
No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.