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.
- Regulatory Change Management
- Features
- Review and Evidence
Review and Evidence
Keep revision decisions, uploaded evidence and operation receipts in view.
OverviewOperation Exceptions×
Regulatory Change Management · Review and Evidence
New
Operation Exceptions
Operation receipts 2
| Operation key | Action | Expected revision | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| OK-784 | ACT-656 | 380 | Failed | 19 Oct | Cut to length | |
| OK-386 | ACT-617 | 50 | Needs review | 12 Oct | Weld frame | |
| OK-519 | ACT-467 | 960 | Failed | 04 Oct | Drill and tap | |
| OK-520 | ACT-933 | 450 | Needs review | 10 Oct | Deburr | |
| OK-266 | ACT-561 | 110 | Failed | 06 Oct | Assemble |
6 of 6 records
OK-784Operation receipts 2 · OR-19425
FailedActionACT-656
Expected revision380
Occurred at19 Oct
Failure reasonCut to length
What you can do
Make the decision inspectable
A reviewer decision records the assessment, source revision, reviewer, decision, date and reason. That combination matters when a Control Owner changes a rule implementation after an earlier review. The Independent Assurance Reviewer can decide to approve, reject or return a revision. The recorded reason gives the next owner a precise starting point. A decision belongs to the revision reviewed, not merely to the current display of the assessment.
An operation receipt records the action, expected revision, result state, occurrence time and references to effects. When an operation receipt is recorded, failed and review-needed results remain available for reconciliation. Operations Overview brings failed operation state and review workload to authorized users, giving the team a place to notice unresolved results before it treats a plan as complete.
How the work is organized
- Decision. Record the reviewer, revision, outcome and reason against the assessment.
- Attachment. Store evidence with title, type, upload date, visibility and uploader.
- Receipt. Use a recorded result state and failure reason to investigate an operation.
What to agree during setup
Define when an assessment or rule change is ready for independent review. Choose a consistent way to name evidence files and evidence types, and decide which attachments should be internal or shared. Agree who reconciles a failed operation receipt and what counts as a resolved discrepancy. A reviewer should be able to understand a decision from the source revision and recorded reason without calling the original owner.
For a submitted implementation plan, the reviewer opens the assessment and follows its tests, findings and attachments. The reviewer decides with a reason tied to the examined revision. Record that outcome against the assessment, then confirm the related rule change carries the corresponding status. If an operation receipt is present and shows failure, investigate the result before reporting the action as finished.
Check the handoff on an actual case
Select a submitted rule change with a linked assessment. Confirm the reviewer can identify the revision being considered and the evidence attachments relevant to it. Check the recorded approval, rejection or return decision and its reason with a second reviewer. If an operation receipt exists, inspect its expected revision and result state. Follow a review-needed result through its failure reason and effect references.
Have an Auditor read the same case from the recorded evidence. The Auditor should see who uploaded an attachment, when the decision was made and why, and the result of any recorded operation. This rehearsal tests both the clarity of the record and the team’s access choices for shared and internal evidence.
What your team sees
- Operation Exceptions — Find failed or review-needed operations with their reasons.
- Assessments for Review — Work through assessment revisions awaiting examination.
- Rule Review Queue — Open submitted rule changes and their linked evidence.
Follow the work through
See review a rule change and remediation.
What it keeps track of
Data model- Review decisions 2
- Independent reviewer decisions recorded per source revision
- Operation receipts 2
- Durable operation receipts for guarded workflow commands
- Record attachments 2
- Uploaded evidence files linked to an assessment
- Assessments 2
- Impact and control assessment periods per organization and owner
- Rule changes 2
- Incoming regulatory rule changes and implementation plans
- Team members 2
- Named staff with operational roles and organization membership
Who uses it
Permissions- Independent Assurance Reviewer
- Examines revisions and reconciles evidence.
- Control Owner
- Prepares the material under review.
- Auditor
- Reads authorized records.
- App Administrator
- Maintains membership.
Set up Regulatory Change Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.