1. Crop Insurance Platform
  2. Process
  3. Review and operation exceptions
Process · Review and operation exceptions

Review and operation exceptions

A policy attachment identifies the evidence type and uploader, and its visibility guides sharing. review decisions preserve the reviewer, source revision, operation key and reason. The reviewer may Approve, Reject or Return. That decision is a human gate for the policy team. Operation receipts then show whether a workflow action completed, failed or needs review. Operations Overview surfaces failed provider operations beside claim and assessment pressure.

Step by step

  1. Collect evidence Policy Owner

    Policy Owner keeps the file, visibility and uploader under the policy.

    • Policy Owner keeps the file, visibility and uploader under the policy.
    • Updates Record attachments, Policies
  2. Review revision Independent Reviewer

    Independent Reviewer records decision, source revision and reason.

    • Independent Reviewer records decision, source revision and reason.
    • Updates Review decisions, Policies
    ApprovalA person approves before the work moves on.
  3. Check operation Payment Operator

    Payment Operator reads result, expected revision and failure reason.

    • Payment Operator reads result, expected revision and failure reason.
    • Updates Operation receipts, Policies
  4. Return for correction Policy Owner

    Policy Owner updates returned work for a new review.

    • Policy Owner updates returned work for a new review.
    • Updates Review decisions, Policies
Policy Owner
, Independent Reviewer, Payment Operator.
Each person follows the record within their organization and keeps the next actor clear.
A decision remains tied to the person who made it and to the source evidence available at the time.

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