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.
- Change Request Management
- Process
- Evidence and exception handling
Evidence and exception handling
Evidence files explain a change and its delivery. Operation receipts give the team a place to record attempted actions and their outcomes. Neither a file nor a receipt takes the place of the review decision.
Step by step
-
Add evidence Business Analyst
Business Analyst or Delivery Contributor attaches a file to the package with a title, evidence type and visibility.
- Keep files with the change
- Updates Record attachments, Work packages
-
Check the handoff Project Manager
Project Manager confirms the file is attached to the correct package and useful for the current revision.
- Confirm title, type and visibility
- Updates Record attachments
-
Review the material Independent Reviewer
Independent Reviewer reads the evidence with the assessment and package before recording a decision.
- Support a reasoned choice
- Updates Review decisions, Record attachments
-
Inspect an exception Admin
Admin or Delivery Lead opens a Failed or needs review operation receipt and reads the action, expected revision and failure reason.
- Find failed action and revision
- Updates Operation receipts
-
Resolve the attempt Delivery Lead
The owner corrects the underlying record or request, keeping the earlier receipt visible. A new decision is recorded separately if the scope changes.
- Correct work while preserving history
- Updates Operation receipts, Work packages
Who does what
Roles and permissions- Business Analyst
- And Delivery Contributor supply files, Independent Reviewer examines them, and Admin with Delivery Lead investigates receipts.
Set up Change Request Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.