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

# Overview

> What the AI Insurance app is, and the insurance lifecycle it manages — from submission to quote to policy to claims and billing.

AI Insurance is a platform for running an insurance program end to end. The web
app is where your team does the day-to-day work: intake submissions, work up and
send quotes, bind policies, service them over their life (endorse, renew,
cancel, reinstate), handle claims, and manage the money — invoices, payments,
and reserves.

<Frame caption="The app: sidebar navigation on the left, breadcrumbs across the top, and the working area — here, the Policies list.">
  <img src="https://mintcdn.com/ai-insurance-fmv1/XH5fzBvkqbS_uBK9/assets/app/getting-started/app-overview.png?fit=max&auto=format&n=XH5fzBvkqbS_uBK9&q=85&s=a4fda621ea37fe398bd5dfdcb0bd7088" alt="The AI Insurance app with the left sidebar showing Dashboard, Events, Exposures, Policies, Quotes, Submissions, Directory, and Financials, breadcrumbs across the top, and the Policies list page filling the main area." width="2914" height="1132" data-path="assets/app/getting-started/app-overview.png" />
</Frame>

Everything in the app is a **record** — a submission, a quote, a policy, a
claim, an exposure, a person, an organization. Each record type has its own
list page, its own detail workspace, and its own set of fields. The
[Entities documentation](/entities/overview) describes the record types and how
they connect; this section covers using the app itself.

<Note>
  AI Insurance is **configured per company**: the fields on your records, the
  pages that display them, the dropdown choices, and the rules that drive them
  are all set up for your specific program. Your app may show different fields
  and tabs than the screenshots in these docs. See
  [How your app is configured](/app/getting-started/configuration).
</Note>

## The lifecycle at a glance

The heart of the app is the path a risk takes from first contact to an
in-force, serviced policy:

```
Submission → Quote → Bind → Policy → Endorse / Renew / Cancel / Reinstate
                                 ↘ Events (claims)
                                 ↘ Billing & payments
```

<Steps>
  <Step title="Submission">
    A request to be quoted arrives — entered by hand, imported from files, or
    created from an email. The submission is where you record the applicant and
    check for clearance issues before doing any work. See
    [Creating submissions](/app/workflows/creating-submissions).
  </Step>

  <Step title="Quote">
    From a submission you work up one or more quotes in the **quote wizard** —
    a step-by-step flow through quote details, exposures, rating information,
    coverages, billing, and forms, ending with review and send. See
    [Quoting new business](/app/workflows/quoting).
  </Step>

  <Step title="Bind">
    When the insured accepts, you bind the quote. Binding runs a short flow of
    its own — policy details, policy forms, review and bind — and produces a
    **policy**: the bound, in-force contract. See
    [Binding a quote](/app/workflows/binding).
  </Step>

  <Step title="Service the policy">
    Over the policy's life you endorse it (change it mid-term), renew it into a
    new term, cancel it, or reinstate a cancelled policy. Each of these runs as
    its own guided flow, and the policy keeps a full history you can browse.
    See [Servicing a policy](/app/workflows/servicing-policies).
  </Step>

  <Step title="Claims">
    When something happens, you record an **event** — a claim or an incident —
    against the policy, manage it in the claim workspace (files, notes,
    contacts, legal, financials), and set reserves and record losses. See
    [Handling claims](/app/workflows/claims).
  </Step>

  <Step title="Billing">
    Premium flows into invoices, and invoices get paid — including by the
    insured directly through a shareable payment link. See
    [Billing & getting paid](/app/workflows/billing) and the
    [Financials section](/financials/overview).
  </Step>
</Steps>

Alongside the lifecycle, **exposures** — the things being insured (businesses,
buildings, vehicles, people) — sit at the center of the data model: submissions,
quotes, policies, and events all reference them. The **directory** holds the
people and organizations (brokers, attorneys, contacts) you link to records
along the way.

## Where things live

The sidebar mirrors the lifecycle. Each area has a feature-reference page with
the full detail:

<Columns cols={2}>
  <Card title="Dashboard & tasks" href="/app/features/dashboard-tasks">
    Your task calendar and list — follow-ups, reminders, and assignments.
  </Card>

  <Card title="Submissions" href="/app/features/submissions">
    Incoming requests to be quoted, and file/email imports.
  </Card>

  <Card title="Quotes" href="/app/features/quotes">
    Priced offers, their statuses, and quote actions.
  </Card>

  <Card title="Policies" href="/app/features/policies">
    Bound contracts, activity history, renewal chains, and exports.
  </Card>

  <Card title="Events" href="/app/features/events">
    Claims and incidents, and the claim workspace.
  </Card>

  <Card title="Exposures" href="/app/features/exposures">
    The insured things, cross-referenced from everywhere.
  </Card>

  <Card title="Directory & contacts" href="/app/features/directory">
    People and organizations, linked to records as contacts.
  </Card>

  <Card title="Financials" href="/financials/overview">
    Invoices, payments, reserves, and financial reports.
  </Card>
</Columns>

Recurring tools that work the same on every record type get their own pages:
[files & notes](/app/features/files-notes),
[generating forms](/app/features/forms), and
[exports & saved views](/app/features/exports-saved-views).

## Next steps

* [Signing in & your account](/app/getting-started/signing-in) — get into the
  app and manage your sign-in methods.
* [Navigating the app](/app/getting-started/navigating) — the sidebar, the
  record workspace pattern, and how list pages work.
* [How your app is configured](/app/getting-started/configuration) — why your
  screens may differ from these docs.
* [Entities overview](/entities/overview) — the data model behind it all.
