> 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/mobile-app/ios-outsmart-app/module-overviews/work-order/hours.md).

# Hours

## Hours

Use **Hours** to register work periods for the job.

The screen can show entries in a grid or list layout.

### What you can do

* switch between grid and list view
* create entries from a timer
* add hours that stay linked to the work order

### Use **Hours**

{% stepper %}
{% step %}

### Open **Hours**

Open the work order.

Go to **Hours**.
{% endstep %}

{% step %}

### Choose the layout

Switch between grid and list if needed.

The app remembers your last view.
{% endstep %}

{% step %}

### Add or stop time

Create a work period manually or from a stopped timer.
{% endstep %}

{% step %}

### Save the entry

Save the result so it stays attached to the work order.
{% endstep %}
{% endstepper %}

### Keep in mind

Some jobs require **Hours** before the work order can be completed.


---

# 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/mobile-app/ios-outsmart-app/module-overviews/work-order/hours.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.