# First Notice of Loss ("FNOL")



Overview [#overview]

The First Notice of Loss ("FNOL") process is intended to capture relevant data about a potential loss before the formal claims process starts. It accommodates information that is relatively unstructured, incomplete, potentially inaccurate, and subject to revision.

In Socotra, an FNOL is distinct from a claim, but can be associated with or used as the basis for a claim.

Configuration [#configuration]

FNOL and losses are configured at the top configuration level:

```javascript
{
    fnol: map<string, FnolRef>,
    losses: map<string, LossRef>,
    lossCategories: string[]
}
```

See the [Deployments API](/api/configuration-and-development/deployments) for details on `FnolRef` and `LossRef`.

When you define an FNOL, you specify the loss types appropriate for that FNOL. In turn, a loss type is defined as belonging to some category specified in `lossCategories`. Beyond that, as with other primary platform entities, you may define an inheritance hierarchy, associate data extensions, specify contact associations, fine-tune the search behavior, and assign a numbering plan.

State Flow and Validation [#state-flow-and-validation]

FNOLs can have the following states:

* `draft`
* `validated`
* `onClaim`
* `completed`
* `rejected`
* `discarded`

An FNOL starts in the `draft` state, where it remains until validated, either manually or by setting the `autoValidate` flag to `true` in the `FnolCreateRequest`.

An FNOL will proceed to `onClaim` state when at least one claim has been created with it. From there, it may proceed to `completed`, `rejected`, or `discarded`.

An FNOL in the `onClaim` state will revert to the `validated` state if any of its data is modified.

Losses [#losses]

You may <ApiLink name="addLosses">add</ApiLink> and <ApiLink name="deleteLosses">remove</ApiLink> *Losses* from the FNOL, and optionally tie each loss to a specific policy element for associating coverage and exposure information. The system can automatically check whether coverage is valid using [Coverage Checks](/features/claims/coverage-checks).

Versioning [#versioning]

FNOL versioning mirrors the same behavior as contacts. Versioning history is not kept for `draft` records.

Promotion [#promotion]

An FNOL can be promoted to a claim via the <ApiLink name="createClaim" /> endpoint.

See Also [#see-also]

* [FNOL API Guide](/api/claims)
* [Coverage Checks](/features/claims/coverage-checks)