Prepare certificate details when a vendor submits a renewal COI
For Vendor risk coordinators and insurance operations teams
Turn an incoming certificate of insurance into structured coverage rows and named parties. Give the reviewer a starting record for checking the renewal against your requirements and prior certificate.
25 free credits/month · No card needed
See the workflow and review checks{
"insured_name": "Example Contractor LLC — synthetic",
"producer_name": "Example Insurance Agency",
"certificate_holder": "Example Property Owner, 100 Example Way, Sample City, CA 00000",
"certificate_date": "2026-08-01",
"coverages": [
{
"coverage_type": "Commercial general liability",
"insurer": "Example Insurer",
"policy_number": "DEMO-GL-001",
"effective_date": "2026-09-01",
"expiration_date": "2027-09-01",
"printed_limits": "Each occurrence: USD 1,000,000"
}
],
"description_of_operations": "Example maintenance services at the demonstration property."
}Synthetic data, not a live extraction. Real responses also include confidence, validation, and result status.
When this work lands on your desk
A vendor submits a replacement certificate before an existing coverage period expires, and operations needs to determine which record to review next.
Certificates can list several policies with different dates, insurers and limits. A single expiration field loses that distinction, and a familiar vendor name does not establish that the requested holder or supporting endorsements are correct. Extract each coverage row without treating the certificate as proof that every contractual requirement is satisfied.
Start with the documents you already collect
- Certificate of insurance PDFs
- Scanned renewal certificates
- Supporting endorsements using separately evaluated schemas
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 tracking system associates the vendor and creates any renewal reminders. Your reviewer compares each coverage row with your requirements and checks the underlying policy or endorsements where needed.
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 |
|---|---|---|
insured_name | string | Named insured shown on the certificate. |
producer_name | string | Agency or producer as printed. |
certificate_holder | string | Holder name and address exactly as shown. |
certificate_date | date | Certificate issue date when printed. |
coverages | array | Coverage type, insurer, policy number, effective date, expiration date and printed limits. |
description_of_operations | string | Relevant description text without interpreting its legal effect. |
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
- Different expiration dates across coverage rows
- Named insured does not match the contracted entity
- Holder wording or location differs from the request
- Required endorsement evidence is absent from the submission
Prove the fit on a representative batch.
Evaluate certificates with several coverage rows, a replacement policy and a mismatched holder. Compare extracted dates and limits with a reviewer’s checked record.
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 ongoing vendor renewals. Add schemas or upload portals as different vendor programs need distinct intake fields and supporting documents.
For a tailored implementation
Discuss custom volume and schema setup for large vendor networks or many separately managed properties.
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 coi renewal intake
Does this determine insurance compliance?
No. It prepares certificate facts. Your qualified reviewer determines whether the actual coverage and supporting evidence satisfy your requirements.
Are expiry reminders included in extraction?
The extraction returns printed dates. Your application or tracking system schedules reminders and decides which date governs each renewal task.
Can a certificate establish additional insured coverage?
Do not infer coverage from extraction alone. Have the appropriate reviewer examine the policy and any required endorsements.
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.