> For the complete documentation index, see [llms.txt](https://docs.onre.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onre.finance/for-insurers/underwriting.md).

# Underwriting

We underwrite regulated insurance programs written by licensed primary insurers. Our goal is to support programs that have predictable loss behavior, strong operational discipline, and clear data visibility.

### How We Select Risk

Before we accept reinsurance exposure, we evaluate:

* The insurer’s underwriting guidelines and pricing logic
* Historical loss experience and expected loss behavior
* How exposure is capped and structured
* The quality and reliability of policy and claims data
* The regulatory environment the insurer operates in

We only write risk that fits within established insurance frameworks and can be monitored throughout the policy period. We do not underwrite unlicensed programs, exposures that cannot be modeled, or risk structures that lack transparent data or regulatory oversight.

### Diversification and Exposure Limits

Each program is structured with defined limits so we know the maximum exposure at any time.\
Across the broader portfolio, we diversify by line of business, geography, and loss pattern to avoid concentrated risk.

### Premium and Reserve Management

Premiums are paid upfront and placed in the program’s segregated account.\
We divide the premium into:

* The amount earned over the life of the policy
* The portion that must remain reserved for future coverage
* Capital set aside for claims
* Collateral that can be invested in low-volatility assets

This protects policyholders, supports claims, and establishes the return profile for ONyc.

### Claims Expectations and Capital Modeling

We model expected losses for each program based on past performance and the structure of the underlying risk. This helps determine how much capital must be retained and how much can safely generate collateral yield.

### Weekly Underwriting Commentary

Weekly perspectives from OnRe's Chief Underwriting Officer on reinsurance market developments, emerging risks, and underwriting considerations.

{% content-ref url="/pages/g0Cn2AsD7D5CzNhMv4Xc" %}
[Underwriting Commentary](https://docs.onre.finance/for-insurers/underwriting-commentary.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onre.finance/for-insurers/underwriting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
