1. Crop Insurance Platform
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Keep policy review decisions and supporting files with their source. Independent Reviewer records the decision, reason and source revision under the policy. Policy Owner keeps supporting attachments with the same policy, including who uploaded each file and whether it is shared.

OverviewPolicy review decisions
Crop Insurance Platform · Review and evidence

Policy review decisions

Review decisions

New
ParentReviewerSource revisionDecisionDecided atReason
PLC-33413830Approve10 OctApprove rd-300
PLC-26589210Return26 OctReject rd-701
PLC-68531840Approve27 OctReturn rd-425
PLC-78631450Return07 OctApprove rd-870
PLC-96095770Approve18 OctReject rd-332
6 of 6 records
Approve rd-300Review decisions · RD-53672
Approve
ParentPLC-33413
Source revision830
Decided at10 Oct
Example screen with sample data

What you can do

Review and evidence in practice

A review decision links a reviewer and policy with a source revision, decision, decision date, reason and operation key. The policy owner can read the exact decision that applied to a revision. A record attachment holds title, file, upload date, visibility, evidence type and uploader under its parent policy. Internal and Shared visibility values help the team discuss who should see a file.

The independent reviewer chooses Approve, Reject or Return and records a reason. A returned policy goes back to the policy owner for correction. The decision record is separate from the policy status, so the team should inspect both before issue. An attachment should remain tied to the same policy as the review rather than being reused by name on another policy.

How the work is organized

  • Keep the revision. Match each decision to the policy revision the reviewer saw.
  • Preserve evidence. Keep the attachment and uploader under the same policy.
  • Handle returns. Send corrected coverage back for a fresh decision.

What to agree during setup

Agree who can record review decisions and how the team prevents self-review. Decide what evidence the reviewer must see before selecting Approve, Reject or Return. Set the meaning of Internal and Shared attachment visibility for each operating role. Rehearse a returned revision, then compare the new decision with the earlier one before issuance.

Check the handoff on an actual case

Take a policy under review with a changed coverage line. Upload the relevant evidence under the policy and have the reviewer record the source revision and reason. If the reviewer returns it, revise the policy and ask for a new decision against the updated revision. When it is approved, issue the policy and inspect its operation receipt. Keep the earlier decision available to explain what changed.

The Policy Owner should find the latest decision and its reason beside the policy. Independent Reviewer should be able to locate the attachment and the revision reviewed. If the policy changed after a decision, the team requests a new review rather than treating the earlier approval as current.

What your team sees

  • Policy review decisions — Read decisions with reviewer, source revision and reason.
  • Policies awaiting review — Find policies awaiting review and open their supporting files.

Follow the work through

Follow the related operating process and use the record definitions when checking a field or relationship.

What it keeps track of

Data model
Review decisions
Review Decisions records; retain actual linked evidence and role scope.
Record attachments
Record Attachments records; retain actual linked evidence and role scope.
Policies
Policies records; retain actual linked evidence and role scope.
Policy coverages
Policy Coverages records; retain actual linked evidence and role scope.
Team members
Team Members records; retain actual linked evidence and role scope.

Who uses it

Permissions
Independent Reviewer
Records the decision.
Policy Owner
Supplies evidence and corrections.
Admin
Manages access.

Set up Crop Insurance Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started