> For the complete documentation index, see [llms.txt](https://docs.tactyc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tactyc.io/portfolio-management/performance-cases/best-practices-on-performance-cases.md).
# Best Practices on Performance Cases
Performance cases offer flexibility in how you want to model an investment’s forecast. We recommend picking one of the following 3 approaches to manage performance cases for an investment.
## Approach 1: Single case with graduation rates
**Level of Effort: Low**
Build only one case and the performance risk is captured in the *graduation rates* of the forecasted rounds.
## Approach 2: Multiple cases with 100% graduation rates
**Level of Effort: Low**
Build multiple cases and the performance risk of the investment is captured in the *case probabilities* of each case.
## Approach 3: Multiple cases with custom graduation rates
**Level of Effort: High**
Build multiple performance cases and the performance risk is captured in *both the case* *probabilities and the graduation rates* within each case. This gives you the greatest control - for e.g., you may model an Upside case that has a higher likelihood of graduations than the Base case.
---
# 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.tactyc.io/portfolio-management/performance-cases/best-practices-on-performance-cases.md?ask=&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.
