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.
- Insurance Agent Portal
- Features
- Review and Evidence
Review and Evidence
Preserve the reason, source version and file behind a commission decision.
OverviewReview Decisions×
Insurance Agent Portal · Review and Evidence
New
Review Decisions
Review decisions
| Name | Decision | Decided at | Reason | Source revision | Reviewer | |
|---|---|---|---|---|---|---|
| Decision 652 | Approve | 18 Oct | Approve rd-376 | 730 | ||
| Decision 382 | Return | 15 Oct | Reject rd-659 | 950 | ||
| Decision 555 | Approve | 13 Oct | Return rd-696 | 370 | ||
| Decision 715 | Return | 21 Oct | Approve rd-219 | 230 | ||
| Decision 754 | Approve | 08 Oct | Reject rd-472 | 730 |
6 of 6 records
Decision 652Review decisions · RD-49367
ApproveDecided at18 Oct
ReasonApprove rd-376
Source revision730
ParentOPP-43907
What you can do
Decision trail
Review decisions link to an opportunity and record an approval, rejection or return, the deciding team member, reason, decision date, operation key and source revision. Record attachments keep a title, file, evidence type, visibility and uploader against the same opportunity. Operation receipts carry the action, expected revision, result state and any failure reason.
How the work is organized
- Record owner. Commission Reviewer owns the decision. Producer and Commission Specialist attach relevant files. Agency Manager and Admin inspect exceptions.
- Related work. Decision, file and receipt records each link to an opportunity. Compare the submitted statement on that opportunity before making a decision.
- Visible outcome. Keep the decision reason or receipt failure reason with the relevant opportunity.
What to agree during setup
Agree which files may be Shared, who can see Internal material and how a reviewer verifies that the source revision still matches. The team should test this rule with a realistic client case and decide how corrections are recorded. Check that the people who prepare work can see what they need, while the person responsible for the decision has the correct access.
Check the handoff on an actual case
A reviewer receives a submitted commission statement and opens the related opportunity evidence. The reviewer checks the carrier document, then records a decision and reason. If an operation fails, the agency manager checks Failed Operations and its failure reason before retrying any action. The receipt and decision stay linked to the opportunity so the team can explain the result later.
For a disputed commission amount, open the file as the reviewer and compare it with the submitted statement before deciding. Record the reason in terms the specialist can act on. If the decision is Return, the specialist needs the same parent opportunity and source context to make the correction. Review Internal and Shared visibility with ordinary user accounts. When an operation has needs review, inspect its expected revision before attempting a correction so the team can avoid repeating an effect.
A decision records a reason and source revision on the opportunity; it does not by itself identify a specific statement. For a disputed amount, the reviewer compares the submitted statement and carrier file before recording which revision was examined. A later correction should lead to another review, with the earlier decision left available for the manager.
What your team sees
- Review Decisions — Read decision, reviewer, reason and source revision together.
- Failed Operations — Find actions needing attention with their failure reason.
Follow the work through
Read the related process and implementation before rehearsing this handoff.
What it keeps track of
Data model- Review decisions
- Captures whether a submitted change was approved or rejected and why, for accountability.
- Record attachments
- Stores files and evidence linked to a record so the team has proof on hand when reviewing it.
- Operation receipts
- Logs each system action taken and whether it succeeded, so the team can trace what happened and why.
- Opportunities
- Tracks a potential deal in progress, so the team can follow it from first contact to close.
- Team members
- Represents a person on the team, used to assign work and track who does what.
Who uses it
Permissions- Commission Reviewer
- Owns the decision.
- Producer
- And Commission Specialist attach relevant files.
- Agency Manager
- And Admin inspect exceptions.
Set up Insurance Agent Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.