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.
- Crop Insurance Platform
- Features
- Policy portfolio
Policy portfolio
Keep the policyholder, organization and policy owner together before issuance. Policy Owner links each crop policy to a policyholder, organization and team owner. The independent reviewer records a decision against the policy revision. When the owner issues the policy, the workflow stamps the issue time and records the operation.
OverviewMy policy portfolio×
Crop Insurance Platform · Policy portfolio
New
My policy portfolio
Policies
| Record number | Subject | Status | Effective date | Expiry date | Counterparty | |
|---|---|---|---|---|---|---|
| PLC-88359 | Draft plc-781 | Draft | 25 Oct | 28 Oct | PLC-1027 | |
| PLC-60908 | Under review plc-521 | Under review | 21 Oct | 26 Oct | PLC-5638 | |
| PLC-86518 | Issued plc-664 | Issued | 12 Oct | 17 Oct | PLC-2007 | |
| PLC-66219 | Active plc-794 | Active | 04 Oct | 09 Oct | PLC-4039 | |
| PLC-76413 | Expired plc-720 | Expired | 10 Oct | 14 Oct | PLC-8972 |
6 of 6 records
Draft plc-781Policies · PLC-88359
DraftEffective date25 Oct
Expiry date28 Oct
CounterpartyPLC-1027
What you can do
Policy portfolio in practice
A policyholder has a name, code, contact, address and eligibility note within an organization. The policy links that policyholder to its owner, subject, record number, premium and effective date. This gives the policy team a specific record to review when a grower reports a loss. Active flags on the policyholder and organization help the owner check identity before creating further work.
A policy moves from Draft through under review to Issued. The owner checks the effective date, proposed premium and policyholder while the independent reviewer records a decision against the policy revision. Issuance stamps the issue time if it is empty and writes an operation receipt. That receipt gives the operations team a place to check the outcome of the issuance action.
How the work is organized
- Establish identity. Check the policyholder and organization before writing coverage.
- Review the revision. Compare the reviewer decision with the current policy revision.
- Confirm issuance. Read the issue time and operation receipt after the status changes.
What to agree during setup
Agree who creates policyholders, who may prepare policies and who makes the independent review decision. Decide how the team handles a returned decision after coverage changes. Check the policyholder and organization links before issuance. Rehearse a policy that is revised after review so the owner can identify a stale decision before moving it to Issued.
Check the handoff on an actual case
Take a policy for a named farm with a crop subject and an effective date. Confirm the policyholder and organization, assign an active owner, and compare the current revision with the reviewer decision. Issue the policy, then find its issue time and operation receipt under the same policy. When a claim arrives later, follow its policy link back to this record instead of matching a similar name by hand.
The Policy Owner should see assigned policies and their current status, then open the review decision for the relevant revision. Independent Reviewer should see the supporting coverage and attachment. After issuance, both should find the stamped time and operation receipt under the policy.
What your team sees
- My policy portfolio — See policies assigned to the signed-in team member and open the next one.
- Policies awaiting review — Find policies awaiting the independent review decision.
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- Policies
- Policies records; retain actual linked evidence and role scope.
- Policyholders
- Policyholders records; retain actual linked evidence and role scope.
- Organizations
- Organizations records; retain actual linked evidence and role scope.
- Team members
- Team Members records; retain actual linked evidence and role scope.
- Review decisions
- Review Decisions records; retain actual linked evidence and role scope.
- Operation receipts
- Operation Receipts records; retain actual linked evidence and role scope.
Who uses it
Permissions- Policy Owner
- Prepares and issues the policy.
- Independent Reviewer
- Records the review decision.
- Admin
- Maintains access.
Set up Crop Insurance Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.