all workflows
Insurance document workflows for US MGAs
How policy data becomes filled PDFs, dynamic documents and packets assembled by your rules.
Explore all insurance document workflowsinsurance document automation for US MGAs, wholesale brokers and program administrators
Insurance documents should follow the policy data.
For US MGAs, wholesale brokers and program administrators, Mezdoc turns the data you already have into the forms, letters and packets your team sends.
Policy data becoming the documents in a packet
Mezdocdocument layerExisting PDFDynamic documentWorkflow rules
Quote letter
Binder
Certificate
AI endorsement
Three ways Mezdoc handles insurance documents.
Most packets use all three.
Existing PDF
Fill the binders, carrier forms and ACORD forms you already use.
How static PDF templates workDynamic document
Write quote letters and schedules that grow with the data.
How dynamic documents work
See how static PDFs, dynamic documents and workflows build one insurance packet
Keep your PAS, AMS or rater. Mezdoc handles the documents beside it.
Your system keeps the policy, the rating and the decisions. There is no prebuilt connector: your system, a person filling a form, or a short script sends the data.
Your system of record
PAS, AMS, rater or spreadsheet
- Policy and insured records
- Rating and premium
- Underwriting decisions
- Binding authority
Mezdoc
The document layer
- ACORD forms and carrier PDFs, filled
- Quote letters, binders and schedules
- The right forms for each risk, by your rules
- The finished packet, back to your system
Insurance document workflows, step by step.
Policy packets, ACORD 25 certificates and the quote-to-binder paperwork, each shown with the documents it produces.
policy issuance
Policy packets and the schedule of forms
Declarations, coverage forms, state notices and endorsements, each included by a rule your team configured, then merged into one policy packet.
Explore insurance policy packet automation for US MGAscertificates of insurance
Automate ACORD 25 certificate creation
Map the ACORD 25 your organization is licensed or authorized to use once. Each certificate of insurance then fills from the policy, insured and holder data you send.
Automate ACORD 25 insurance certificate creation from policy dataquote and bind
Quote letter, binder and schedule from approved quote data
Once a quote is approved in your PAS or rater, send the data once and get back the quote letter, the binder, the schedule and the forms your rules call for.
See the quote-to-binder document workflow
It already speaks your forms.
Upload the forms you send today. Mezdoc reads their fields and fills your original PDF, so form numbers and edition dates stay as they are.
ACORD forms you are licensed or authorized to use
- ACORD 25
- ACORD 125
- ACORD 126
- ACORD 130
- ACORD 140
Agency and MGA paperwork
- Quote letters
- Binders
- Endorsement requests
- Premium finance agreements
- Surplus lines notices
- Producer licensing packets
Across the policy term
- Declarations pages
- Change endorsements
- Cancellation notices
- Nonrenewal notices
- Reinstatement notices
When an edition changes, publish a new version. Links that follow the live version pick it up; a pinned link stays on the version it was made with, and every document already issued keeps rendering from the version that made it. Your team writes the rules that decide which forms go out; Mezdoc never decides what a risk needs.
Built for the question that comes months later.
Every submission records which template version produced it, when, and the signature details it captured, including the IP address and device for link and embed fills. A certificate issued in March renders the same in September, because the version it ran on is pinned.
Read the security pageA signature record
Drawn, typed or uploaded, with the signer's email when an email code is on, the IP address, device and time.
A SHA-256 of every PDF
Recompute it on the file you hold to show it has not changed since it was issued.
The version it ran on
Each document names its template version, and that version re-renders identically.
An append-only log
Workflow publishes, restores and link changes, with who made them and when, plus every run.
Three ways to send the data.
Mezdoc is not a policy admin or rating system. It takes the data those systems send and returns finished paperwork.
from your policy admin
An API call
POST the bound policy to a workflow and get the merged packet and each document back, with a signed webhook when the run finishes. A single certificate renders from one call, and an idempotency key means a retry never issues it twice.
from the insured
A link
Send the insured a link to the workflow. They answer once, sign where the documents ask, and the packet lands with you. Links can ask for an email code first, expire, and stop after a set number of uses.
inside your portal
An embedded form
Put a single form, such as a certificate request, inside your agent portal. It loads only on the sites you allow and shows the Mezdoc logo.
One call from your system.
The workflow returns the merged packet and each document. Add ?async=true for a 202 and a webhook instead.
POST /api/v1/workflows/renewal_packet/runs
curl -X POST "https://api.mezdoc.com/api/v1/workflows/renewal_packet/runs" \
-H "Authorization: Bearer $MEZDOC_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "data": { "insured_name": "Harbor Point LLC", "state": "TX", "additional_insured": true } }'Three insurance teams, one engine.
Agencies and brokers
- ACORD 25 certificates from one API call or one link.
- Renewal packets filled from one set of answers.
- The insured's name typed once, on every page.
MGAs and program administrators
- A rule on each document: the notice joins only where the state calls for it.
- Versioned templates, so an edit never changes a live packet until you publish.
- One link collects the answers and the signature for the whole packet.
Premium finance
- Finance agreements rendered in batches, safe to retry.
- A signed webhook when each document is ready.
- A SHA-256 of every PDF, recorded with the submission.
Questions from insurance teams.
- Do you support ACORD forms?
Yes, the ones your organization is licensed or authorized to use; Mezdoc does not supply ACORD forms. Upload ACORD 25, 125, 140 or any other edition and Mezdoc reads its form fields, or you place them. It fills your original PDF, so the form number and edition date stay exactly as they are.
- Does Mezdoc decide which forms a risk needs?
No. Your team writes the rules, and Mezdoc applies them the same way every time and records what went out. Coverage, eligibility and compliance decisions stay with you and your carriers.
- How do signatures work?
The insured signs in the form, drawn, typed or uploaded. Each submission or workflow run is completed and signed by one person. Mezdoc does not route documents to another signer, and has no signing order or countersignature. In a workflow, one signature field can fill signature lines on several documents. Each submission records the email when an email code is on, the IP address, device, time and a SHA-256 of the PDF.
- What happens when a form edition changes?
Upload the new edition and publish it as a new version. Links that follow the live version pick it up at once, a pinned link stays on its version, and documents already issued keep rendering from the version that made them.
- Can we keep our agency management or policy admin system?
Yes. It stays the system of record. It sends the data to Mezdoc over the API and gets the PDFs back, with a signed webhook when each run finishes. Mezdoc is the document layer, not a rating or policy system.
Bring the certificate everyone dreads.
We build the first template with you on a call. Free plan, no card, and you keep whatever we build.
Free plan, no card