These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Audit Management
- Features
- Evidence and operations
Evidence and operations
Keep attachments, reviewer decisions and action results available for follow-up.
OverviewOperation Exceptions×
Audit Management · Evidence and operations
New
Operation Exceptions
Operation receipts
| Receipt number | Operation type | Operation key | Occurred at | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| OR-63426 | Assessment Approval | OK-395 | 22 Oct | Failed | Cut to length | |
| OR-22823 | Corrective Action Release | OK-442 | 27 Oct | Needs review | Weld frame | |
| OR-97453 | Risk Posting | OK-653 | 15 Oct | Pending | Drill and tap | |
| OR-12174 | Assessment Close | OK-979 | 05 Oct | Failed | Deburr | |
| OR-62202 | Engagement Issue | OK-411 | 03 Oct | Needs review | Assemble |
6 of 6 records
OK-395Operation receipts · OR-63426
Assessment ApprovalOccurred at22 Oct
Result stateFailed
Failure reasonCut to length
What you can do
Give reviewers a path back to the evidence
An audit conversation often resumes after the people involved have moved to another engagement. Evidence attachments help the team recover the context by recording a title, document link, evidence type and uploader. The parent record identifiers explain which working record the attachment supports. Choose a title that tells the reviewer what they will find before opening the document.
Review decisions and operation receipts answer different questions during follow-up. A decision records a person’s judgment and reason. A receipt records an operation type, stable operation key and result state. When an action needs investigation, the Audit Manager inspects those records with the finding, engagement or response involved. Operations Overview brings the authorized workload and outstanding exception queue into the same operating conversation.
How the work is organized
- Evidence reference. The Auditor or Control Owner records the document link and its parent record. Evidence types distinguish material such as a control policy, test workpaper or approval email.
- Review judgment. The Audit Manager or Independent Assurance Reviewer records Approve, Reject or Return with the subject and reason. The reviewer reference identifies the person responsible for that decision.
- Operation outcome. Receipts retain Completed, Failed, Needs review or Pending results. The operation key and failure reason help the team investigate a particular attempt without guessing from a screen message.
What to agree during setup
Agree where evidence files live and how participants receive access. A document URL should resolve for the authorized reviewer during the audit cycle. Decide how titles and parent references will be checked when evidence is imported. Review an attachment against its parent before relying on it in an approval discussion.
Agree which person investigates each operation type and when to escalate a Pending or Needs review result. Define what must be checked before repeating an action after an uncertain result. Include the current business record, the existing operation key and any failure reason in that investigation. If an external connection contributes evidence, retain its reference and agree who checks delivery and access failures.
Check the handoff on an actual case
Attach a test workpaper to a supplier access finding. The Auditor records the title and document URL and checks the parent identifiers. Ask the Audit Manager to open the attachment using the access that person will have during normal work. If access fails, resolve the repository permission before proceeding with the evidence review.
Next, inspect a finding approval with its review decision and operation receipt. The decision should explain the judgment; the receipt should let the team identify the action and its result. Rehearse an uncertain outcome by inspecting a Failed or Needs review receipt and tracing it back to the working record. The investigator should explain the next safe action before anyone repeats the command.
What your team sees
- Operation Exceptions — Inspect Failed, Needs review and Pending operation results.
- My Review Decisions — Revisit the decisions associated with the signed-in reviewer’s member record.
- My Evidence — Find evidence associated with the signed-in uploader’s member record.
Follow the work through
Rehearse evidence and exception review and agree the systems to connect.
What it keeps track of
Data model- Record attachments
- Evidence attachments linked to a parent record, with uploader and visibility.
- Review decisions
- Independent review decisions recorded against a source revision.
- Operation receipts
- Persisted operation receipts with a stable operation key and result state.
- Team members
- Team members and their audit role scope within an organization.
- Findings
- Audit findings raised from failed or inconclusive control testing.
- Audit engagements
- Audit engagements supporting an evidence-based audit conclusion.
- Corrective actions
- Corrective actions assigned to a finding, with owner, due date and completion evidence.
Who uses it
PermissionsSet up Audit Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.