Prepare comparable policy facts before a renewal review
For Insurance account managers preparing renewal reviews
Extract a consistent set of declaration-page fields from the expiring policy and the proposed renewal. Use separate results to prepare the account manager’s comparison worksheet.
25 free credits/month · No card needed
See the workflow and review checks{
"named_insured": "Example Retail LLC — synthetic",
"carrier_name": "Example Carrier",
"policy_number": "DEMO-POL-204",
"effective_date": "2026-10-01",
"expiration_date": "2027-10-01",
"total_premium": 6400,
"coverage_schedule": [
{
"coverage_label": "Example business personal property",
"limit": 250000,
"deductible": 2500
}
]
}Synthetic data, not a live extraction. Real responses also include confidence, validation, and result status.
When this work lands on your desk
Renewal documents arrive from a carrier, and an account manager needs to compare the stated terms with the current policy before discussing the renewal.
Carrier layouts change, coverage schedules move between pages and a familiar total premium can conceal changes in deductibles or listed locations. A shared schema makes selected printed facts easier to compare. It does not interpret policy wording, identify every exclusion change or determine whether the renewed coverage is suitable.
Start with the documents you already collect
- Current policy declaration pages
- Renewal declaration pages
- Coverage schedules prepared as appropriate supported files
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
Your application links the current and renewal records and calculates any numerical differences. The account manager verifies source documents, reviews endorsements and explains material changes through the agency’s normal review process.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaStarter fields are optional until you choose which are required. Nested line items need a defined structure if you want validation of their individual values.
| Field | Type | What to capture |
|---|---|---|
named_insured | string | Insured entity named in the declarations. |
carrier_name | string | Insurer shown on this policy record. |
policy_number | string | Printed policy identifier, preserving suffixes. |
effective_date | date | Beginning of the stated policy period. |
expiration_date | date | End of the stated policy period. |
total_premium | currency | Printed premium; keep taxes and fees distinct if your schema requires them. |
coverage_schedule | array | Printed coverage label, limit and deductible for the selected schedule. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- Renewal quote confused with an issued policy
- Premium includes a different mix of taxes or fees
- Coverage labels differ despite similar amounts
- Changes appear in endorsements outside the declarations
Prove the fit on a representative batch.
Choose matched current and renewal documents from several carriers. Check extracted values and then review whether your comparison worksheet preserves coverage labels and policy period context.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Use paid capacity for recurring renewal preparation. Add validated schemas for other policy lines and supporting schedules as the team extends its review process.
For a tailored implementation
Discuss custom volume and schema setup for agencies handling numerous policy lines, carrier formats or account teams.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about policy renewal comparison preparation
Does Dokyumi generate a complete coverage comparison?
No. It extracts your requested fields. Your comparison logic and qualified reviewers determine what changed and inspect the complete policy documents.
Can both policies be compared in one API call?
Process each supported file with the selected schema, then join the two results in your application for comparison and review.
Will it find exclusions missing from declarations?
Do not assume declaration-page extraction covers exclusions or endorsements. Define separate document review requirements for those materials.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.