> For the complete documentation index, see [llms.txt](https://docs.openstamanager.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openstamanager.com/2.8.3/guide/esempi/contratti-a-ore.md).

# Contratti a ore

Come gestire i contratti a ore con OpenSTAManager

Per gestire il **Consuntivo** di un contratto a ore è necessario [creare un Contratto](https://github.com/devcode-it/openstamanager-docs/blob/master/esempi/broken-reference/README.md), e successivamente creare delle **Attività** collegate.

Per poter far ciò, il **Contratto** interessato deve essere impostato in uno stato pianificabile (di default: In lavorazione, Fatturato, Pagato e Parzialmente fatturato).

![](https://content.gitbook.com/content/2PiRYHiPQyyI5VSQPG8a/blobs/lK9TZ8EQsFNESyAycbnO/immagine.png)

Lo stato dei contratti è verificabile in Strumenti/Tabelle/Stati dei contratti.

![](https://content.gitbook.com/content/2PiRYHiPQyyI5VSQPG8a/blobs/vpLNfUTrUjbjG5sM89K9/immagine.png)

![](https://content.gitbook.com/content/2PiRYHiPQyyI5VSQPG8a/blobs/2cLNk1UdEgFopF5cJaIy/immagine.png)

Si potrà ora [creare un'**Attività**](/2.8.3/openstamanager/modules/attivita/creazione.md) a cui collegare il **Contratto** appena creato. Le ore di lavoro inserite verranno scalate dal **Budget ore** del contratto.

![](https://content.gitbook.com/content/2PiRYHiPQyyI5VSQPG8a/blobs/TNnxluNrcZjrILFtkDfO/immagine.png)

Per verificarne il **Consuntivo,** si dovrà ora aprire il contratto da Vendite/Contratti e selezionare il Plugin **Consuntivo**.

![](https://content.gitbook.com/content/2PiRYHiPQyyI5VSQPG8a/blobs/uzMzjWliCATfN67XMIrz/immagine.png)

Da questa schermata è ora possibile verificare la lista delle **Attività** associate a questo contratto, l'ammontare del **Budget ore** disponibile e le ore erogate/residue.


---

# 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.openstamanager.com/2.8.3/guide/esempi/contratti-a-ore.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.