> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/sprintgestao/initial-settings/proposals-and-invoices-initial-settings-guide/proposal-and-invoice-contracts.md).
# Proposal and Invoice - Contracts
The **Contracts** SprintHub contracts work as **templates** that you edit once and reuse in your proposals/closings. Below is the step-by-step guide based on the screens you sent.\
\
The SprintHub contract editor is HTML-based. This means that, in addition to the basic visual tools, you have complete freedom to configure the document exactly as you want.
***
### Where to find it
**Settings → Contracts**
In the list you see **First name**, **Alias**, **creation/update dates**, search, button **+ New Contract** and **Change logs**.
***
### Create a contract
1. Click on **+ New Contract**.
2. Fill in:
* **Contract Name** *(required)* — title that appears in the list.
* **Alias** *(required)* — short identifier, without spaces (e.g.: `closing`).
* **Internal Description** — notes only for your team.
* **External Description** — supporting text visible to the client (optional).
In the block **Editor**, write the contract content and click **Register** to save.
***
### Content editor
* **Quick formatting:** bold, italic, underline, strikethrough, links, code.
* **Ready-made blocks:** Paragraph, **Heading 1–6**, **Bulleted list**, **Numbered list**, **Divider** (menu to the left of “Paragraph”).
* **Integrated AI (brain icon):** select a passage and use AI to **review, summarize, or rewrite** text inside the editor.
* **“Result” tab:** see how the contract will be formatted before saving.
> Tip: use **headings** for sections (1. Subject, 2. Price, 3. Deadlines…) and **lists** for clauses. It stays clean and easy to read
### Base template to paste into the editor
```
# SERVICE AGREEMENT
1) Parties
Client: [company name], [CNPJ/CPF], [address].
Provider: [company name], [CNPJ], [address].
2) Subject
Provision of services for [describe scope] according to proposal no. [no.] dated [date].
3) Term
Starts on [dd/mm/yyyy] and ends on [dd/mm/yyyy], and may be renewed by agreement between the parties.
4) Price and Payment Terms
Amount: R$ [amount] ([frequency, if any]).
Method/Plan: [upfront / 30-60 / recurring], due on [day].
5) Obligations
Provider: [specific items].
Client: [specific items].
6) Confidentiality and LGPD
The parties will keep exchanged information confidential and will handle personal data in accordance with the LGPD.
7) Termination
For breach or with [x] days' prior notice. Proportional amounts will be due until the termination date.
8) Jurisdiction
The court of the District of [city/state] is hereby elected.
```
Done! That way you create, standardize, and keep your **contracts** organized in SprintHub — ready to be used in proposals and in closing with the client.
---
# 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://docs.sprinthub.com/en/topics/general/sprintgestao/initial-settings/proposals-and-invoices-initial-settings-guide/proposal-and-invoice-contracts.md?ask=&goal=
```
`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.
