Skip to content
Novus Examples
docx37.1 KB

Pine Property Services: Insurance renewal application (DOCX)

Insurance renewal application (DOCX) for Pine Property Services. A renewal application for the 2027 policy year. It asks for the same limits the expiring policy carries and declares the same loss history the insurer own loss run holds: 3 claims and 20,650.00 USD incurred. The declaration says the two must agree, so the pair is a ready-made consistency test. The PDF twin in the same directory carries the identical text.

Rendered preview of Pine Property Services: Insurance renewal application (DOCX)

Rendered preview of the docx file (37.1 KB). Download above for the original.

Specifications

Document Set
insurance
Industry
trades-property
Source Kit
trades-property
Entity
Pine Property Services
Synthetic
true
As Of
2026-09-08
Application Id
APP-2027-0001
Locations
6
Vehicles
4
Declared Claims
3
Declared Incurred
20650.00
Renderer
python-docx
Paragraphs
11

Testing contract

Expected to pass
Scenario
Compare the loss history table with loss-run-report.csv row by row.
Expected result
All 3 claims appear with the same loss dates, perils and incurred amounts, and both documents total 20650.00 USD incurred.

What is a .docx file?

DOCX is the default Microsoft Word format, an Office Open XML document packaged as a ZIP archive of XML parts, media, and relationships. It stores structured text, styles, tables, images, and metadata. It is the dominant format for editable word-processing documents.

How to use this file

Use an example DOCX to test Office Open XML parsing, text and style extraction, ZIP-package handling, and converters that render or transform Word documents.

How to use this file for testing

“Pine Property Services: Insurance renewal application (DOCX)” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: DOCX · 37,961 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

from docx import Document  # pip install python-docx

doc = Document("insurance-application.docx")
for p in doc.paragraphs[:10]:
    print(p.text)

Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.