From submission to signed-off cover
Referrals route to the right approver by rule, surveys are tracked against the risk, and every endorsement becomes its own version with its premium impact attached.
One policy, every version
Surveys, referrals and endorsements all attach to the policy, so the full history of the risk sits on one record.
Survey
Scheduling · Processing · Completed
Referral
Pending · Approved · Rejected
Policy
New Business · Active · Renewing
Endorsement
Draft · Applied · Cancelled
Every change becomes a version
Mid-term changes are captured as endorsements against the policy, listing exactly what was added, modified and removed with the premium impact of each. Apply the endorsement when it is ready, undo it if you need to, and the policy keeps a link to the version before and after it.
- Added, modified and removed items with before-and-after values
- Premium impact and pro-rata premium on every endorsement
- Apply or undo an endorsement from the record
- Each policy links to the version before and after it
Referrals routed by rule
Set the mandate once. Each submission is matched against the approval processes you configure and routed to the right approvers in series or in parallel, with every response kept alongside its comment and date.
- Steps that run one after another or all at once
- Approvers delegate, submitters recall
- Responses and comments kept on the Approvals tab
- Processes are versioned, so referrals in flight never shift
Surveys tracked against the risk
Survey requirements sit on the policy, opportunity or insurer they belong to. Scheduling, processing and completion each have their own steps, and extensions are approved and dated instead of quietly moving the deadline.
- Statuses and sub-statuses from scheduling to sign-off
- Initial and extended due dates kept side by side
- Request an extension straight from the survey
- Scheduled reminders as due dates approach
Calculations and rules the business owns
Premium splits, commission percentages and net figures are defined once as formula fields on the record, reaching across related records and stored in real columns. Automations run on any object, updating records and sending emails when the data changes.
- Formula fields configured by administrators, not developers
- Results stored in real columns for lists, reports and exports
- Automations triggered by record changes
- Every automation run recorded step by step
One policy, every team
Sales
Accepted quotes become policies with their cover already in place.
Explore sales ➝
Claims
Cover is snapshotted on the day of a loss, so claims are assessed against what was insured then.
Explore claims ➝
Case management
Service requests and complaints link to the policy they concern.
Explore case management ➝
Ready to see what
Meta can do?
FAQ
Yes. Each endorsement is its own record listing what was added, modified and removed, with the premium impact of every change. Policies link to the version before and after them, so the whole chain stays one click apart.
Your approval processes decide. Each submission is matched against the processes you configure and routed to the right approvers in series or in parallel, and every response is kept with its comment and date.
Request an extension on the survey. The original due date stays put, the extended date is recorded once approved, and a scheduled job reminds the team as due dates approach.
Yes. Formula fields are configured by administrators against the record they belong to, can reach across related records, and store their results in real columns for lists, reports and exports.