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.
- Trade Compliance
- Features
- Review and evidence
Review and evidence
Keep independent decisions, attachments and operation receipts tied to the assessment.
OverviewReceipts needing review×
Trade Compliance · Review and evidence
New
Receipts needing review
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| ASS-44947 | OK-867 | ACT-902 | 550 | Needs review | Cut to length | |
| ASS-67199 | OK-619 | ACT-971 | 570 | Needs review | Weld frame | |
| ASS-92805 | OK-964 | ACT-291 | 190 | Needs review | Drill and tap | |
| ASS-94816 | OK-197 | ACT-925 | 340 | Needs review | Deburr | |
| ASS-17924 | OK-476 | ACT-383 | 300 | Needs review | Assemble |
6 of 6 records
OK-867Operation receipts · OR-29624
Needs reviewParentASS-44947
ActionACT-902
Expected revision550
Failure reasonCut to length
What you can do
Preserve the reason for a decision
A review decision records the assessment, source revision, reviewer, decision, date, reason and operation key. This lets the team explain why a specific revision was approved, rejected or returned. An attachment records title, type, upload time, uploader and visibility. The team can use those details to assemble the evidence packet for a reviewer without confusing internal material with material marked shared.
An operation receipt records an action, expected revision, result state, time and any failure reason. It gives reviewers a way to distinguish a completed operation from one that failed or needs review. The receipt does not replace the underlying decision or source evidence; it points the team toward the record and revision that require attention.
How the work is organized
- Record the decision. Keep the reviewer, source revision, decision date and reason on the assessment decision.
- Control visibility. Attach source material to the assessment and mark who may share it.
- Reconcile operations. Use the receipt’s expected revision and result state to investigate uncertain effects.
What to agree during setup
Agree what belongs in a shared attachment and what stays internal. Name the Independent Assurance Reviewer who can decide an assessment revision, and define how a changed revision returns to the Control Owner. Choose an operation key that the team can use to find its receipt. Assign someone to investigate receipts marked failed or needing review before the assessment is treated as settled.
Check the handoff on an actual case
Attach one internal item and one shared item to an assessment. Have the Independent Assurance Reviewer record a decision with a reason against the current assessment revision, then change that revision. Ask the Auditor to identify which version the decision covered. Create a receipt that needs review and have the reviewer compare its expected revision and failure reason with the assessment. Check access with a team member from another organization before opening either attachment.
What your team sees
- Receipts needing review — Inspect operations needing review against the expected revision.
- Shared assessment evidence — Find attachments available to the authorized reviewer.
During the pilot, include one attachment marked internal and one marked shared. Confirm who can open each file, then ask the auditor to follow the final decision to its source revision. Also rehearse a receipt that needs review, including its failure reason, so an uncertain operation does not look like a completed one.
Follow the work through
See the related process and the record model before agreeing the pilot.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions on submitted revisions
- Record attachments
- Evidence files attached to assessment records
- Operation receipts
- Durable receipts for guarded workflow operations
- Assessments
- Compliance assessments covering a defined period and scope
- Team members
- Compliance personnel and their platform identities
Who uses it
Permissions- Independent Assurance Reviewer
- , Control Owner, Auditor, App Administrator.
Set up Trade Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.