> For the complete documentation index, see [llms.txt](https://docs.ensuro.co/ensuro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ensuro.co/ensuro-docs/risk-partners/onboarding-process.md).

# Onboarding process

Risk models are vetted by Ensuro’s Quant team. The Quant team estimates the pricing parameters and the program’s portfolio structure with the Risk Partner before the roll-out of the program. The Quant team works to optimize the outcome for all stakeholders by considering the safety of the investment, the returns for the liquidity providers, and the costs for the end customers. The onboarding consists of four steps:

1\) In the initial phase, Ensuro's Risk team diligently gathers essential documentation pertaining to both the existing product structure and the envisioned future target portfolio. This documentation encompasses crucial aspects such as:

* Product description,
* Portfolio structure, risk limits, and risk drivers,
* Pricing model documentation. Including historical performance and available datasets,
* Target portfolio.

2\) Subsequently, the Risk team at Ensuro undertakes a meticulous validation process of the partner's model. This validation encompasses an in-depth analysis of: &#x20;

* Model performance analysis,
* Data quality checks,
* Estimation of known-unknowns and need for mitigating actions.

3\) Building upon the outcomes of the preceding stages, Ensuro's Risk team collaborates closely with the Risk Partner to establish:

* Mutually agreed risk limits and target portfolio parameters&#x20;
* The pricing structure for the product is determined during this phase, taking into account the insights gained from the validation process.
* Solvency capital requirements.

\
4\) Once the product is launched, Ensuro's robust real-time monitoring system diligently tracks the actual performance of the product. This monitoring capability enables prompt recalibration of pricing strategies and, if necessary, updates to the risk limits. By actively monitoring the product's performance, Ensuro ensures that any required adjustments can be swiftly implemented to maintain optimal risk management and pricing efficacy.

\
Real-time monitoring
--------------------

Once the program is live, the Quant team tracks its dynamics in real-time and performs sensitive interventions to adjust the pricing if the performance is not in line with expectations. The real-time visibility of the program allows Ensuro to carry out surgical and preventive actions rather than wholesale, a-posteriori resolutions.  Ensuro has built a dashboard to allow every stakeholder to monitor the protocol’s performance in real-time, in the same manner as the Quant team.

\ <br>

<figure><img src="https://lh6.googleusercontent.com/bJqU67PL5K1rfyvpA8tU81i0E-BKyOhbKGV3Ij3dKiCsiYZj_QLKk3Z4zrzdxGqV-XkiJmatV6l8_qQhqujHhDxQrXDobZ0ROk97SC2y2pCAB0uDLwJxirp_83n7OJNcFMdlROZ0pdXlG4MQhr3ZL0fwIw=s2048" alt=""><figcaption></figcaption></figure>

## <br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ensuro.co/ensuro-docs/risk-partners/onboarding-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
