> 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/outsmart-knowledge-base/outsmart-knowledge-base-pt/app-movel/ios-outsmart-app/visoes-gerais-dos-modulos/ordem-de-trabalho/horas.md).

# Horas

Registar tempo diretamente na ordem de trabalho na app iOS.

## Horas

Usar **Horas** para registar períodos de trabalho para o Trabalho.

O ecrã pode apresentar as entradas em grelha ou em lista.

### O que é possível fazer

* alternar entre vista de grelha e vista de lista
* criar entradas a partir de um temporizador
* adicionar Horas que ficam associadas à Ordem de trabalho

### Usar **Horas**

{% stepper %}
{% step %}

### Abrir **Horas**

Abrir a Ordem de trabalho.

Ir para **Horas**.
{% endstep %}

{% step %}

### Escolher o layout

Alternar entre grelha e lista, se necessário.

A app memoriza a última vista.
{% endstep %}

{% step %}

### Adicionar ou Parar tempo

Criar um período de trabalho manualmente ou a partir de um temporizador parado.
{% endstep %}

{% step %}

### Guardar a entrada

Guardar o resultado para que permaneça associado à Ordem de trabalho.
{% endstep %}
{% endstepper %}

### Ter em atenção

Alguns trabalhos requerem **Horas** antes de a Ordem de trabalho poder ser Concluído.


---

# 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/outsmart-knowledge-base/outsmart-knowledge-base-pt/app-movel/ios-outsmart-app/visoes-gerais-dos-modulos/ordem-de-trabalho/horas.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.