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.
- Hospitality CRM
- Features
- Review and evidence
Review and evidence
Keep review decisions, attachments and guarded action receipts tied to the opportunity revision.
OverviewReview decision history×
Hospitality CRM · Review and evidence
New
Review decision history
Review decisions
| Parent | Source revision | Decision | Decided at | Reason | Reviewer | |
|---|---|---|---|---|---|---|
| OPP-41725 | 880 | Approve | 10 Oct | Approve rd-129 | ||
| OPP-41068 | 200 | Return | 14 Oct | Reject rd-400 | ||
| OPP-20933 | 580 | Approve | 04 Oct | Return rd-126 | ||
| OPP-36442 | 620 | Return | 08 Oct | Approve rd-548 | ||
| OPP-88997 | 50 | Approve | 07 Oct | Reject rd-956 |
6 of 6 records
Approve rd-129Review decisions · RD-42220
ApproveParentOPP-41725
Source revision880
Decided at10 Oct
What you can do
Show what was decided
A review decision records the source revision, decision, date, reason, operation key and reviewer for an opportunity. A supporting attachment has a title, file, evidence type, visibility and uploader. An operation receipt records the action, expected revision, result state and any external or local effect references. These records let a Sales Manager explain why a proposal or outcome advanced. For an inquiry, the decision is recorded under its parent opportunity; the operation key and inquiry revision must identify the request being reviewed.
The critical question is whether the reviewer assessed the same revision that the owner now wants to act on. An approval on an earlier version cannot safely carry forward after the owner changes the case. The stable operation key also lets a repeated action return its earlier result instead of quietly doing the work twice.
How the work is organized
- Decision. The Sales Manager records approve, reject or return with a reason against the exact source revision.
- Evidence. The Relationship Owner attaches the supporting file with its visibility and evidence type.
- Receipt. Each guarded action records its key, expected revision and outcome for later reconciliation.
What to agree during setup
Decide which evidence types the team will use for qualification, proposal and customer acceptance. Agree when a file may be shared and who can see internal evidence. The Sales Manager should set a clear reason for a rejection or return so the owner knows which part of the case must change.
Also agree who investigates a receipt left pending or marked for review. A receipt is a record of an attempted operation; its result state should be read with the linked opportunity and effects before anyone treats it as a completed business outcome.
Check the handoff on an actual case
Take an opportunity whose buyer has asked for a revised group stay. The Relationship Owner attaches the revised request and submits it. The Sales Manager records a return with a reason. The owner corrects the inquiry, submits the next revision, and the manager approves that one. Inspect both decisions so the earlier return remains in history.
Now repeat the same guarded action with the same operation key. The second attempt should resolve to the recorded result, not create duplicate effects. Change the expected revision and check that the action is refused or marked for investigation. Finally, have an Auditor follow the authorized attachment, decision and receipt from the parent opportunity without changing the record.
What your team sees
- Review decision history — Decisions by date, source revision, reviewer and reason.
- Receipts needing review — Guarded actions whose recorded effects require investigation.
- Pending operations — Actions awaiting evidence of their declared effect.
Follow the work through
What it keeps track of
Data model- Review decisions
- Independent review decisions (approve, reject, return) recorded against an opportunity revision.
- Record attachments
- Evidence files attached to an opportunity with visibility and evidence type.
- Operation receipts
- Idempotent operation receipts recording the outcome of each guarded action with its stable operation key.
- Opportunities
- Hospitality sales opportunities with lifecycle stage, expected value, expected close date and revision guard.
- Team members
- Internal hospitality sales and review team members with their organization membership and role.
- Group stay inquiries
- Domain extension records requesting group-stay availability for a selected opportunity parent.
Who uses it
Permissions- Relationship Owner
- Supplies evidence.
- Sales Manager
- Decides and reconciles.
- Auditor
- Reads the authorized trail.
- App Administrator
- Maintains organization membership that underlies access.
Set up Hospitality CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.