Does Mezdoc calculate premium or rate the quote?

No. Your rater or PAS does the rating. Mezdoc receives the approved figures and puts them into the quote letter, the binder and the schedule. A workflow can add values together, such as premium plus fees, but it never rates a risk or decides the terms.

Can the binder be our existing PDF?

Yes. Upload the binder PDF you use today as a static template and place fields on it. If your binder is written rather than a fixed form, build it as a dynamic document instead. One workflow can mix both.

How are conditional attachments added to the binder packet?

Each attachment in the workflow carries an include rule your team writes, such as surplus_lines == true && state == "TX". When the rule is true for the approved quote, the attachment joins the packet; when it is false, it is skipped.

Can the insured sign what Mezdoc generates?

Through a hosted link, yes: the person who opens it completes the workflow's form and signs where the documents ask. Each submission or workflow run is completed and signed by one person. A packet generated from your quote data through the API comes back unsigned, because a link cannot be pre-filled from your system today.

What happens when our quote letter wording changes?

Edit the template and publish a new version, test it on staging, then publish the workflow again. Runs already made keep the versions they used, so an old quote letter renders exactly as it went out.

USA MGA Quote & Binder Document Workflow

What happens after the quote is approved.

Six scenes, one idea each. Nothing in your rating or underwriting changes.

Mezdocdocument layerExisting PDFDynamic documentWorkflow rules

Surplus lines in Texas?Add the Texas notice.
Additional insured?Add the endorsement.

Quote letter

Binder

Schedule

Surplus lines notice

AI endorsement

Packet ready, 5 documentsA signed webhook tells your system it is ready.

Scene 1
Your PAS or rater approves the quote.
Rating and the decision happen in your system, as they do today.
Scene 2
The approved data moves to Mezdoc.
Your system posts it to the API, or someone fills a hosted form.
Harbor Point LLC3 coveragesSurplus lines: yes
1. Template
2. Data arrives
3. Table grows
4. Paragraph added
5. Ready
Ready
Scene 3
A dynamic quote letter renders.
The coverage table grows with the quote, and a paragraph appears only when the data calls for it.
1. Your PDF
2. Fields mapped
3. Values filled
4. Ready
Ready
Scene 4
Your binder PDF fills.
The binder you use today, filled field by field from the same data.
- Surplus lines in Texas?Add the Texas notice.
- Additional insured?Add the endorsement.
Quote letter
Binder
Schedule
Surplus lines notice
AI endorsement
Scene 5
Configured forms join.
The notice and the endorsement your rules call for slide into the packet. Nothing else does.
Scene 6
The final packet is ready.
One merged PDF, separate files or both, back to your system.

Keep your rater or PAS. Use Mezdoc for the documents downstream.

Mezdoc handles document generation and workflow. It does not calculate premium, make underwriting decisions, or bind coverage.

Your PAS or rater

Stays your system of record

Rating
Premium
Underwriting decision
Binding authority

Mezdoc

The document layer beside it

Quote letter
Binder
Schedule
Conditional document packet

How approved quote data reaches Mezdoc.

Send Mezdoc structured quote or policy data through the API, a hosted form, or your existing application. There is no prebuilt connector to install.

from your PAS, rater or quoting app
Through the API
Your system posts the approved quote to the workflow when a quote is approved, and stores what comes back.
from an underwriter or broker
Through a form
Someone fills the workflow's hosted form in the browser. Useful before an integration exists.
from inside your own tools
From your existing application
Your internal quoting or underwriting app calls the same API when a quote is approved.

Conditional attachments, by the rules you write.

Put the quote letter, the binder, the schedule and every possible attachment in one workflow. Each attachment carries an include rule, so the binder packet holds only the attachments whose rules are true for this approved quote.

The same approach assembles the full policy packet after binding: explore insurance policy packet automation for US MGAs.

Sample include rules for binder packet attachments
Include rule	Attachment
`surplus_lines == true && state == "TX"`	Texas surplus lines notice
`state == "FL"`	Florida state notice
`additional_insured == true`	Additional insured endorsement
`premium_financed == true`	Premium finance agreement
`terrorism_coverage == false`	Terrorism coverage rejection form

Your team writes these rules. Mezdoc does not decide which attachments a risk legally requires.

Reusable quote and policy data.

A workflow has one set of fields, shared by every document. A document field fills from a shared field, a formula, or a fixed value.

Sample workflow fields for a quote to binder workflow, and the documents each one fills
Workflow field	Quote letter	Binder	Schedule
`insured_name`input	Fills the quote letter	Fills the binder	Fills the schedule
`effective_date`input	Fills the quote letter	Fills the binder	Not used in the schedule
`premium`input	Fills the quote letter	Fills the binder	Not used in the schedule
`total_due`computed: premium + policy_fee + surplus_lines_tax	Fills the quote letter	Fills the binder	Not used in the schedule
`coverages`input, a list	Fills the quote letter	Not used in the binder	Fills the schedule
`binder_number`input, from your system	Not used in the quote letter	Fills the binder	Not used in the schedule

A computed value is worked out once per run, before any document fills, so the quote letter and the binder show the same total. The same insured and policy data can fill the certificate later: see ACORD 25 certificate creation from the same policy data.

the API flow

From approval to packet, with nobody retyping the quote.

01The quote is approved in your PAS, rater or quoting app.
02Your system posts the approved data to the workflow, with ?async=true.
03Mezdoc answers 202 with a poll URL, applies the include rules and renders every included document.
04A signed workflow.run.completed webhook arrives. Your system downloads the merged PDF or each document with its API key.

How signed webhooks work

POST /api/v1/workflows/quote_to_bind/runs?async=true

curl -X POST "https://api.mezdoc.com/api/v1/workflows/quote_to_bind/runs?async=true" \
  -H "Authorization: Bearer $MEZDOC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "data": {
        "insured_name": "Harbor Point LLC",
        "state": "TX",
        "effective_date": "2026-06-01",
        "premium": 14200,
        "policy_fee": 250,
        "surplus_lines_tax": 695.80,
        "surplus_lines": true,
        "additional_insured": true,
        "premium_financed": false
      } }'

# 202 Accepted: run_id, status, poll_url
# later, to your endpoint:
workflow.run.completed

When the insured has to sign

Send the workflow as a hosted link. The person who opens it completes the form and signs where the documents ask, and the packet comes back with its certificate of completion. A link can ask for an email code first, expire, and stop after a set number of uses.

A packet built from your quote data through the API comes back unsigned: links cannot be pre-filled from your system today.

Document versioning

Change the quote letter wording or a binder edition, publish the new template version, test it on staging, then publish the workflow again. Each run records the versions it used, so an old binder renders exactly as it went out.

Mezdoc handles the documents. Rating, underwriting and binding stay with you.

Mezdoc does

Writes the quote letter from the approved terms you send
Fills your binder PDF and renders the schedule
Adds the attachments your include rules call for
Returns one packet, or each document, to your system

Mezdoc does not

Rate the risk or calculate premium
Make underwriting decisions or referrals
Bind coverage; your team and your authority do that
Decide which attachments a risk legally requires
Replace your PAS, AMS or rater

Good to know before you build

One signer per submission or run: 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.
Links are filled by whoever opens them: A link cannot be pre-filled from your system, and links are created in the dashboard, not through the API.
No prebuilt PAS or rater connector: Your PAS, rater or quoting app calls the REST API. There is nothing to install.
Your wording, your rules: Mezdoc ships no clause library and no rule library for quotes and binders. Your team writes both.

Questions about the quote and binder workflow.

Does Mezdoc calculate premium or rate the quote?: No. Your rater or PAS does the rating. Mezdoc receives the approved figures and puts them into the quote letter, the binder and the schedule. A workflow can add values together, such as premium plus fees, but it never rates a risk or decides the terms.
Can the binder be our existing PDF?: Yes. Upload the binder PDF you use today as a static template and place fields on it. If your binder is written rather than a fixed form, build it as a dynamic document instead. One workflow can mix both.
How are conditional attachments added to the binder packet?: Each attachment in the workflow carries an include rule your team writes, such as surplus_lines == true && state == "TX". When the rule is true for the approved quote, the attachment joins the packet; when it is false, it is skipped.
Can the insured sign what Mezdoc generates?: Through a hosted link, yes: the person who opens it completes the workflow's form and signs where the documents ask. Each submission or workflow run is completed and signed by one person. A packet generated from your quote data through the API comes back unsigned, because a link cannot be pre-filled from your system today.
What happens when our quote letter wording changes?: Edit the template and publish a new version, test it on staging, then publish the workflow again. Runs already made keep the versions they used, so an old quote letter renders exactly as it went out.

All insurance document workflows for US MGAs

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 MGAs
certificates 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 data

Build your first quote-to-binder workflow.

Start with the quote letter and the binder you send today. Add the attachments that depend on the risk, then run it from your system or a link.

Build the workflow Book a setup call

Free plan, no card

Turn approved quote data into the documents that come next.

An approved quote becoming the binder packet

What happens after the quote is approved.

Your PAS or rater approves the quote.

The approved data moves to Mezdoc.

A dynamic quote letter renders.

Your binder PDF fills.

Configured forms join.

The final packet is ready.