Claims and policy review
Review the claim file and the policy behind it.
Read claim packets and compare policy versions, check the cited terms, and give the person who decides the evidence in one place.
Discuss your use caseRepair estimate from Brookside Restoration $8,640.00.
- Policy
- HO-4471902 p. 1
- Date of loss
- Sep 28, 2026 p. 1
- Cause
- Burst supply line p. 1
What it handles
The claim file, put together for you.
Claim packets are turned into a checked file and tested against the policy, so the person who decides starts with the evidence in front of them.
Forms, receipts and reports read into one claim record, each fact linked to its page and checked against the policy.
ClaimsCLM-61027 · Water damageReady to decideExtracted4 fields- Policy
- HO-4471902 p. 1
- Date of loss
- Sep 28, 2026 p. 1
- Cause
- Burst supply line p. 1
- Estimate
- $8,640.00 p. 2
Checks- Policy in force on the date of loss
- Cause covered under section I
- Within the adjuster's authorityLimit $10,000
Approve claimRequest inspectionOpen claims with their checks and amounts, the clean ones ready to approve and the rest flagged for a closer look.
Ask about any claim and get a summary of what happened, what is covered and what is missing, with each fact cited.
Compare premiums, limits and exclusions before the broker sends the recommendation.
How it fits
From first notice to a decision.
Strive reads each claim as it arrives, checks it against the policy and gives the adjuster a file ready to decide.
Comes in from
- Claims inboxNotices, forms and photos
- Uploaded evidenceReceipts, estimates and reports
- Policy dataPolicies, coverage and limits
- 01ReadForms, photos and receipts
- 02ExtractWho, what, when and how much, cited
- 03CheckCoverage, dates and duplicates
- 04ReviewAn adjuster decides
Goes out to
- A claims appEvery claim and its evidence
- Alerts in SlackClaims over authority, to a senior
- Into your claims systemDecisions returned over the API
What you can do.
Build the claim file
Forms, receipts and reports read into one record, each fact linked to its page.
Check coverage
Policy dates, covered causes and limits tested against the claim.
Flag what looks wrong
Duplicates and inconsistent dates or amounts flagged for a closer look.
Route by authority
Claims over an adjuster's limit go to a senior reviewer automatically.
Apps for this work
Security
Security your IT team will sign off on.
SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data never trains a model.
Security
SOC 2 Type II
Independently audited security controls, tested over time.
Europe
GDPR
Personal data handled under the EU's data protection rules.
California
CCPA
Personal data handled under California's privacy law.
Controls
Encryption
Encryption runs on every layer, built on Google Cloud's security controls. Data is encrypted at rest with keys held in Google Cloud KMS, and every connection is encrypted in transit, including traffic between our own services. The credentials your connections use are encrypted too, and never appear in an app.
- At rest
- AES-256, on Google Cloud.
- Keys
- Held and managed in Google Cloud KMS.
- In transit
- TLS on every connection into the platform.
- Inside the platform
- Traffic between our own services is encrypted too.
- Connection credentials
- Stored encrypted and entered through secure forms. Never shown in apps.
- Exported apps
- Credentials are left out.
No training on your data
Your data is never used to train AI models, and the AI services we use don’t train on it either: we use them on enterprise terms that exclude training. A data processing addendum makes our commitment contractual, and you decide how long your data is kept.
- AI model training
- Your data is never used to train AI models.
- AI services
- Used on enterprise terms, so they don’t train on your data either.
- In writing
- A data processing addendum makes it a contractual commitment.
- Retention
- You decide how long your data is kept.
Single sign-on
People sign in with the identity provider you already use: Google, Microsoft, Okta, or any provider that supports SAML or OpenID Connect. Their groups map to roles in Strive, so the right access follows them in. Systems connect with API keys.
- Providers
- Google, Microsoft, Okta, and any provider that supports SAML or OpenID Connect.
- Protocols
- SAML and OpenID Connect (OIDC).
- Roles
- Groups in your identity provider map to roles in Strive.
- Systems
- API keys.
- Rate limits
- Requests are limited for each organization.
Role-based access
Role-based access control: each person has a role, and the role decides which apps, data and actions they can use. The Assistant works with the same access as the person using it, so it can only see and do what they can.
- Roles
- Assigned to each person, or mapped from groups in your identity provider.
- Apps and data
- A role decides which apps, records and actions a person can use.
- The Assistant
- It has the same access as the person using it, no more.
- Changes it proposes
- They wait for someone with the right role to approve them.
- Actions that cost money
- They ask for confirmation first.
- Organizations
- Each organization's data is kept separate.
Questions
What people ask about claims processing.
Does it decide whether a claim gets paid?
No. An adjuster decides, from a claim file where every fact points to the page it came from, and can correct any value before the claim moves on.
Our adjusters aren't builders. Who sets this up?
We can. We build the claims workflow around how your team already works, and your adjusters just use the app. If someone on your team wants to change a rule or a field later, they can do it without waiting on us.
Can it read scanned receipts and handwritten claim forms?
Yes. Scans, photos and poor copies are read with OCR, and handwriting is read by a vision model. A packet that arrives as one PDF can be split into separate documents first.
Can it connect to our claims and policy systems?
Yes, if the system has a REST API, an MCP server or a PostgreSQL database Strive can connect to. Your claims system can also send claims in over the Strive API.
Is there an audit trail of each decision?
Yes. Each decision is tied to the version of the claim that was reviewed, so you can see who did what and when. Enterprise adds audit log export and custom retention.
Do you sign a BAA for health claims?
Yes, for health information.
Which document-heavy job would you hand over first?
Bring one process you want to improve and the information behind it. We build the first version with you in the session, so the first thing you see is your own work, running.
Contact SalesAn hour of your time and a process you know well. That's all it takes.