> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useunderflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Servicing

> Keep renewals, midterm changes, documents, claims, and money on the bound policy.

A bound policy remains part of its original submission. Endorsements, cancellations, reinstatements, certificates, and claims add to that record. A renewal opens a new submission linked to the expiring policy and carries its application forward.

> **[Renewals and nonrenewal](https://docs.useunderflow.com/policy-servicing/renewals.md)**
>
> Work the renewal file opened from an expiring policy or issue a nonrenewal notice.

> **[Endorsements](https://docs.useunderflow.com/policy-servicing/endorsements.md)**
>
> Change coverage midterm and account for the premium difference.

> **[Cancellations and reinstatement](https://docs.useunderflow.com/policy-servicing/cancellations.md)**
>
> Calculate return premium, give notice, rescind, or restore coverage.

> **[Certificates and claims](https://docs.useunderflow.com/policy-servicing/certificates-and-claims.md)**
>
> Issue ACORD 25 certificates, record claims, and produce loss runs.

## Documents

Policy documents are stored by purpose, not only by filename: binder, declarations, endorsement, notice, certificate, and carrier paper. Most generated policy documents remain linked to the policy event that produced them. A generated loss-run PDF is stored with insured metadata but is not currently linked into the file's document register.

## Correspondence

Service requests stay on the file's existing thread when possible. Aurora can draft and send the response under the email autonomy policy. Taking over the file stops Aurora's file turns until a member hands it back; mail and servicing records continue to be stored.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.