Notes on insurance software

A policy history and a renewal answer have details that are easy to lose between screens. These two notes follow those details through the record. The examples are constructed; they describe software behavior rather than insurance decisions.

An endorsement history needs more than one date

An example of a policy screen that keeps document receipt dates separate from the effective date of an endorsement.

Read the chronology

Policy term begins

Effective date: January 1
Document received: January 1

The application holds the locations and documents associated with the start of this term.

Illustrative policy history. Example records, not customer data.

A location is added

The endorsement takes effect on April 1. Its document is received on April 5. Both dates remain in the history.

A corrected document arrives

The corrected document arrived on April 12. It replaces the earlier file for the endorsement effective April 1.

Units and reporting periods in renewal forms

A field worksheet for revenue, payroll, headcount and premises area in an insurance renewal form.

Read the submission worksheet

Requested figure

Revenue

UnitUSD

Period or context

Specified fiscal year or requested 12-month period

Illustrative renewal fields. Retain the requested measure, unit and period with the entered value.

Requested figure	Unit	Period or context
Revenue	USD	Specified fiscal year or requested 12-month period
Payroll	USD	Requested reporting period and definition
Employee headcount	People	Specified as-of date or requested average
Premises floor area	Square feet	Identified risk location