> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/contract-management.md).

# Contract Management

Manage service agreements and generate recurring work orders automatically in OutSmart.

**Contract Management** adds the Contracts module to OutSmart.

Use it when you sell recurring maintenance agreements or corrective service agreements.

{% hint style="info" %}
Availability depends on your package, license, and permissions.
{% endhint %}

### What this Power-Up unlocks

* preventive contracts for recurring maintenance
* corrective contracts with optional SLA handling
* contract terms, renewals, schedules, and generated work orders

### Use the main Contracts docs for setup and daily use

Use the BackOffice Contracts section for the full workflow:

* [**Contracts**](/backoffice/backoffice/contracts.md)
* [**Create a contract**](/backoffice/backoffice/contracts/create-a-contract.md)
* [**Manage contracts**](/backoffice/backoffice/contracts/manage-contracts.md)

### Start here if you are evaluating the Power-Up

1. Check [**Introduction to Contract Management**](/marketplace-packages-and-power-ups/power-ups/contract-management/introduction-to-contract-management.md).
2. Confirm the feature fits your service model.
3. Continue in [**Contracts**](/backoffice/backoffice/contracts.md).

### Related topics

* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/contract-management.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.