> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/commercial-lending/getting-started/concepts/covenants-and-ticklers.md).
# Covenants and ticklers
Learn what a covenant is, how ticklers schedule its compliance checks, and where violations show.
A **covenant** is an obligation in the loan agreement that the borrower must meet during the loan term. Covenants are:
* Affirmative - do something
* Negative - don't do something
* Financial - maintain a metric.
The covenant-extraction agent identifies covenants from the loan agreement. The ones selected for tracking are monitored after closing, and violations show as **Non-Compliant** on the [Covenant dashboard](broken://pages/ExVPio48FQTH6aqK84f0).
A **tickler** is a scheduled compliance check: one instance of a covenant requirement due on a specific date. Ticklers are generated from the covenant rules on a loan's product category, using the *Generate Ticklers* action in [Covenant consolidation](broken://pages/TkTZ1HJULgyMOS9qRL9c).
Each tickler has a due date and a status, such as Upcoming, Compliant or Overdue.
## Related
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# 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.uptiq.ai/commercial-lending/getting-started/concepts/covenants-and-ticklers.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.
