> 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/backoffice/backoffice/contracts/link-contracts-to-projects.md).

# Link contracts to projects

Connect contracts to project context when agreement work belongs inside a wider project flow.

You can link a contract to a project when recurring work belongs to a broader project setup.

This helps keep the contract work aligned with project reporting and context.

### When to link a project

Link a project when the contract is part of a larger customer rollout, installation, or service program.

This keeps the generated work connected to the right project record.

{% stepper %}
{% step %}

### Open the contract

Create a new contract or open an existing one.
{% endstep %}

{% step %}

### Fill in the main contract details

Complete the agreement and work order setup.
{% endstep %}

{% step %}

### Select the project

Choose the project that should be linked to the contract.
{% endstep %}

{% step %}

### Save the contract

Click **Save**.

Future generated work orders keep the project context.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Do I need a project for every contract?</summary>

No.

Only use a project when the contract work belongs in a project flow.

</details>

<details>

<summary>Why link a contract to a project?</summary>

It keeps related work grouped in the correct project context.

</details>

<details>

<summary>Can I still use contracts without the Projects module?</summary>

Yes.

Projects are optional in the contract flow.

</details>

### Related topics

* [**Create a contract**](/backoffice/backoffice/contracts/create-a-contract.md)
* [**Projects**](/backoffice/backoffice/projects.md)
* [**Contracts**](/backoffice/backoffice/contracts.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 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://knowledge.out-smart.com/backoffice/backoffice/contracts/link-contracts-to-projects.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.