> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/user-guide/commitment-inventory.md).

# Commitment Inventory

Commitment Inventory allows you to manage existing commitments and plan for renewal. This tool provides visibility into your current cloud commitments and helps you make informed decisions about future renewals.

## Viewing Expiring Contracts

The interface displays a graph of expiring contracts over time. You can click on "Expiring Contracts" in the graph, and the related commitment entries will be selected and highlighted in the table below.

## Creating Renewal Plans

When you identify commitments that are approaching expiration:

1. Click on the commitment in the graph or table
2. Click "Create Renewal Plan"
3. Archera's system will provide you with three default renewal plans
4. You can also create custom renewal plans tailored to your specific needs

The renewal planning feature helps ensure you maintain optimal commitment coverage and maximize savings opportunities without gaps in your coverage.

## Related Resources

* [Commitment Planner - Overview](/help-center/user-guide/commitment-planner.md)
* [How to Create a Custom Purchase or Renewal Plan](/help-center/user-guide/how-to-create-custom-plan.md)
* [Billing and GRIs](/help-center/billing/billing-and-gris.md)


---

# 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.archera.ai/help-center/user-guide/commitment-inventory.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.