What documents are in a homeowners insurance policy packet?

A bound homeowners policy is a packet, not a single PDF: a declarations page, a base policy form (for example an HO-3), the attached endorsements (water back-up HO 04 95, ordinance or law HO 04 77, scheduled property HO 04 61, and others), any state-mandated notices, and, when flood is bound, the NFIP or private flood forms. Which documents are included depends on the coverage, the property, and the state.

How do conditional document inclusions work?

Each document carries an include or exclude rule written in one condition language. Examples: include the California wildfire and FAIR Plan notice when the state is CA and the property is in a very high fire-hazard zone; include the NFIP flood form when the flood zone is A or V; attach water back-up HO 04 95 only when the insured selected it; add the mortgagee notice only when a mortgagee is present. Workflow-level fields are entered once and map into every document in the packet.

Can I keep my core system and use Mezdoc only for documents?

Yes. Mezdoc is the document generation and assembly layer, with signature fields built in, not a policy admin or rating system. Your core system stays the system of record and POSTs the policy data to a Mezdoc workflow; Mezdoc returns the assembled packet. There is no re-platforming.

How is this different from hand-coded Liquid or Velocity templates?

Hand-coded templates live in code, so only engineers can change a sentence, every edit waits on a deploy, and versioning rides the platform pipeline. Mezdoc gives your ops and compliance teams a visual editor, per-template versions with staging and production pinning, free test renders, and the same condition language across fillable PDFs, smart documents and workflows.

Do you support flood (NFIP) documents?

Yes. The NFIP Homeowner Flood Form, Dwelling Form, and General Property Form, the flood declarations page, and private flood carrier forms can all be templated and assembled by rule, including ICC and zone-driven conditions.

homeowners and flood

The right notices for that address. Nothing else.

A declaration packet is dozens of forms, endorsements and state notices, each included or left out by a condition. Change a fact below and watch the packet rebuild. Nothing was edited, nothing was deployed.

Start free Book a setup call

try a scenario

policy facts

Risk state

Flood zone

Coverage A (dwelling)

Roof age

what your code sends

{
  "state": "CA",
  "flood_zone": "A",
  "coverage_a": 750000,
  "roof_age": "15yr+",
  "water_backup": true,
  "scheduled_items": false,
  "mortgagee": true
}

assembled packet

8of 12 included

Declarations page

always

Homeowners policy formHO-3

always

Water back-up & sump overflowHO 04 95

water_backup is on

Ordinance or law, increasedHO 04 77

coverage_a >= 750,000

Scheduled personal propertyHO 04 61

scheduled_items is on

Skipped

Roof payment schedule (ACV)RPS

roof_age >= 15 years

Wildfire + FAIR Plan noticeCA

state == "CA"

Hurricane / named-storm deductibleFL/TX

state in FL, TX

Skipped

Sinkhole coverage disclosureFL

state == "FL"

Skipped

NFIP flood policy formNFIP

flood_zone in A, V

Coastal / V-zone endorsementV

flood_zone == "V"

Skipped

Mortgagee notice

mortgagee is present

One field set in, the right packet out. No template edits, no deploy.

Sample rules, run in your browser. The API takes the same fields and returns the assembled PDFs.

Today, changing one sentence means a deploy.

Compliance wants one line on the California wildfire notice reworded before renewals go out. The notice lives in a Liquid template in a repo, so the fix needs an engineer, a pull request and a deploy window.

Multiply that by every state, every carrier form and every declaration, endorsement and cancellation you send.

policy-docs / declaration.template.liquid

<h1>Declarations</h1>
<p>Insured: {{ data.policy.holder.name }}</p>
{% if data.policy.characteristics[0].cov_a > 0 %}
  <p>Coverage A: {{ data.policy.characteristics[0].cov_a
     | currency }}</p>
{% endif %}
{% if data.policy.state == "CA"
   and data.policy.fire_zone == "very_high" %}
  {% include "ca_wildfire_fair_plan_notice" %}
{% endif %}
{% for e in data.policy.endorsements %}
  {% include e.template_id %}
{% endfor %}

engineer onlyno version pinevery edit is a deploydeploy queued, 9m 41s

No UI, engineers only: Documents are HTML and Liquid in a repo. Compliance cannot fix a notice or swap a logo; they file a ticket and wait for an engineer.
Versioning is brittle: Changes ride the platform deploy pipeline. There is no clean per-document history, no staging-versus-production pin, and rollback is a redeploy. Someone edits a template and production breaks.
Every edit is a deploy: Changing one sentence means a code change, a config redeploy, and a slow render feedback loop. A wording fix that should take a minute takes a release.
Logic is duplicated: The same condition (if state is CA, if flood zone is A or V) gets rewritten across many templates. Drift is inevitable and hard to audit.
Costly for what it is: You pay premium platform pricing for a document engine that still needs your engineers for every change. The value does not match the bill.
Hard to test: Validating a change means rendering against sample data through a slow loop, with no instant preview of how the final packet looks.

Every document, and the rule that includes it.

You bring the form content. Mezdoc handles the fields, the conditions and the assembly. The table is an illustrative configuration: it shows how a homeowners program could set up its document rules. Carrier, state and program requirements vary. Your team decides which forms and notices apply, and Mezdoc applies the rules you configure.

Homeowners and flood documents, their form numbers and include rules
Document	Form	Included when
core
Declarations page		`always`
Homeowners policy form	HO-3	`always`
Personal property replacement cost	HO 04 90	`if replacement cost`
endorsements
Water back-up & sump overflow	HO 04 95 / 06 95	`if water_backup selected`
Ordinance or law, increased	HO 04 77	`if coverage_a >= 750,000`
Scheduled personal property	HO 04 61	`if scheduled_items`
Premises alarm credit	HO 04 16	`if alarm_system`
Roof payment schedule (ACV)	RPS	`if roof_age >= 15`
Named-storm / wind-hail deductible		`if peril == named_storm`
state notices
Wildfire + FAIR Plan notice	CA	`if state == "CA"`
Hurricane / named-storm notice	FL / TX	`if state in FL, TX`
Sinkhole acceptance / rejection	FL	`if state == "FL"`
Fraud + replacement-cost disclosures		`by state`
flood
NFIP Homeowner / Dwelling / General Property form	NFIP	`if flood_zone in A, V`
Flood declarations page		`if flood bound`
Increased Cost of Compliance	ICC	`if substantial loss`
Coastal / V-zone endorsement		`if flood_zone == "V"`
lifecycle & parties
Notice of cancellation		`if transaction == cancellation`
Notice of nonrenewal		`if transaction == nonrenewal`
Reinstatement notice		`if reinstated`
Change endorsement + revised dec		`if transaction == endorsement`
Mortgagee / lienholder copy		`if mortgagee present`

One engine for the whole policy term.

The same fields and the same condition language cover every document set across the life of the policy.

01
Declaration
New business and renewal. Assemble the dec page, base form, selected endorsements, state notices, and flood forms by condition.
Declarations, HO-3, HO 04 95, HO 04 77, CA wildfire notice, NFIP form, mortgagee copy
02
Endorsement
Mid-term change. Issue the change endorsement and a revised declarations page, with the 30-day explanation when an endorsement reduces coverage.
Change endorsement, revised declarations, coverage-change explanation, mortgagee notice
03
Cancellation and nonrenewal
Notice days and wording vary by state and reason. Generate the notice your rules select, plus reinstatement and lienholder copies.
Notice of cancellation, notice of nonrenewal, reinstatement notice, mortgagee or lienholder copy

Keep your core system. Swap the document layer.

Your policy admin or rating system stays the system of record. It sends the policy data to a Mezdoc workflow and gets back the assembled packet.

Mezdoc is the document layer, not a policy admin or rating engine.
You bring your carrier forms and notice wording; Mezdoc fills and assembles them.
Send the homeowner a link and one signature fills every signature line in the packet.

POST /api/v1/workflows/homeowners_declaration/runs

curl -X POST "https://api.mezdoc.com/api/v1/workflows/homeowners_declaration/runs" \
  -H "Authorization: Bearer $MEZDOC_API_KEY" \
  -d '{ "data": { "state": "FL", "flood_zone": "V", "coverage_a": 750000, "mortgagee": true } }'

Questions from homeowners and flood teams.

What documents are in a homeowners insurance policy packet?: A bound homeowners policy is a packet, not a single PDF: a declarations page, a base policy form (for example an HO-3), the attached endorsements (water back-up HO 04 95, ordinance or law HO 04 77, scheduled property HO 04 61, and others), any state-mandated notices, and, when flood is bound, the NFIP or private flood forms. Which documents are included depends on the coverage, the property, and the state.
How do conditional document inclusions work?: Each document carries an include or exclude rule written in one condition language. Examples: include the California wildfire and FAIR Plan notice when the state is CA and the property is in a very high fire-hazard zone; include the NFIP flood form when the flood zone is A or V; attach water back-up HO 04 95 only when the insured selected it; add the mortgagee notice only when a mortgagee is present. Workflow-level fields are entered once and map into every document in the packet.
Can I keep my core system and use Mezdoc only for documents?: Yes. Mezdoc is the document generation and assembly layer, with signature fields built in, not a policy admin or rating system. Your core system stays the system of record and POSTs the policy data to a Mezdoc workflow; Mezdoc returns the assembled packet. There is no re-platforming.
How is this different from hand-coded Liquid or Velocity templates?: Hand-coded templates live in code, so only engineers can change a sentence, every edit waits on a deploy, and versioning rides the platform pipeline. Mezdoc gives your ops and compliance teams a visual editor, per-template versions with staging and production pinning, free test renders, and the same condition language across fillable PDFs, smart documents and workflows.
Do you support flood (NFIP) documents?: Yes. The NFIP Homeowner Flood Form, Dwelling Form, and General Property Form, the flood declarations page, and private flood carrier forms can all be templated and assembled by rule, including ICC and zone-driven conditions.

Turn your declaration packet into a workflow.

Show us the forms and the conditions you handle today. We map them to a workflow with you and render a first packet in your shape.

Start free Book a setup call

Free plan, no card

The right notices for that address. Nothing else.

Today, changing one sentence means a deploy.

Every document, and the rule that includes it.

One engine for the whole policy term.

Declaration

Endorsement

Cancellation and nonrenewal

Keep your core system. Swap the document layer.

Questions from homeowners and flood teams.

Turn your declaration packet into a workflow.