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.
- Risk Management
- Features
- Evidence and decisions
Evidence and decisions
Keep review decisions, files and operation outcomes traceable.
OverviewEscalations awaiting verification×
Risk Management · Evidence and decisions
New
Escalations awaiting verification
Escalations
| Issue key | Title | Severity | Project | Owner | Status | |
|---|---|---|---|---|---|---|
| IK-354 | Fixed esc-375 | Critical | PRJ-6877 | Fixed | ||
| IK-957 | Fixed esc-231 | High | PRJ-1180 | Fixed | ||
| IK-574 | Fixed esc-915 | Medium | PRJ-6822 | Fixed | ||
| IK-175 | Fixed esc-187 | Low | PRJ-2339 | Fixed | ||
| IK-735 | Fixed esc-435 | Critical | PRJ-6350 | Fixed |
6 of 6 records
IK-354Escalations · ESC-41158
CriticalTitleFixed esc-375
ProjectPRJ-6877
StatusFixed
What you can do
Preserve what the team decided
A project review often depends on more than the latest status. A Review Decision records the subject, decision, reviewer, date and notes. An Operation Receipt records what an action attempted and whether it succeeded or failed. Record Attachments hold file references associated with a delivery record. Together, these records help the Project Manager explain what happened without relying on a private chat or an overwritten status.
How the work is organized
- Decision. Use a reviewed subject and an Approved, Rejected or Returned result with a named reviewer.
- Receipt. Read the operation type, time, result and reference for an automated action.
- Attachment. Keep the file name, kind and parent record identifier with the record it supports.
The time approval workflow writes both a decision and a receipt on successful approval. The escalation triage workflow writes a receipt for the action it took. Failed guarded attempts also produce receipts. A decision, a receipt and a file have different meanings: the decision records an approval outcome, the receipt says whether an operation executed, and the attachment points to supporting material.
What to agree during setup
Decide how reviewers name subjects and where supporting files are stored. The attachment record has a file URL and parent record identifier; the team should make sure those references lead to the correct project record and that access to the file follows the intended permissions. Choose who can see review notes and who may add evidence after a decision.
Agree when a Returned decision requires another review. Keep the original decision understandable rather than rewriting it into Approved. For workflow receipts, the Evidence Reviewer should be able to distinguish Succeeded from Failed and Pending, then take the failed operation back to the person who can correct the underlying record.
Check the handoff on an actual case
A submitted time entry with positive hours is approved. The Evidence Reviewer checks the approved entry, its Review Decision and a succeeded Operation Receipt. The records should point to the same work, date and reviewer context. If the team member asks why the hours were accepted, the reviewer can reconstruct the decision from those records.
For a second case, a Delivery Lead tries to triage an issue with no severity. The guard blocks the change and records a failed receipt. The reviewer reads the issue’s current state and the receipt, then asks the lead to supply severity before retrying. The failed receipt remains evidence of the earlier attempt; it must not be treated as a successful triage.
What your team sees
- operation receipts — Inspect the result of a triage or time approval attempt.
- Time Entries Awaiting Approval — Inspect submitted entries and their operation results.
Follow the work through
Use evidence review, time decision and escalation handling.
What it keeps track of
Data model- Review decisions
- Recorded approval decisions on delivery subjects.
- Operation receipts
- Evidence that a delivery operation was executed.
- Record attachments
- Files attached to delivery records.
- Time entries
- Hours booked by a team member against a task and project.
- Escalations
- Defects and change items raised against project work.
- Projects
- Engagements delivered for an organization, with budget and schedule.
Who uses it
Permissions- Evidence Reviewer
- Examines the trail; Time Approver reviews the hours outcome; Delivery Lead owns issue triage; Project Manager settles the project context.
Set up Risk Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.