> 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/marketplace-packages-and-power-ups/power-ups/timesheets.md).

# Timesheets

Set up Timesheets, register hours in the app, and manage approval and reporting in the BackOffice.

**Timesheets** helps you register working hours, travel time, expenses, and mileage centrally.

Use this section to set up the Power-Up and manage the full process.

{% hint style="info" %}
Time Sheets is a **Power-Up**. Power-Ups are available from **Boost** onward. A trial lasts **14 days**.
{% endhint %}

### What you do with Timesheets

* register hours per employee
* link hours to work orders, projects, and customers
* record expenses and mileage
* approve, reject, and export hours
* gain insight into time spent and costs

### Start here

* [**What is Time Sheets?**](/marketplace-packages-and-power-ups/power-ups/timesheets/what-is-timesheets.md) — introduction and basics.
* [**Set up employees and working hours**](/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-employees-and-working-hours.md) — availability and default working hours.
* [**Set up hour types and rates**](/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-hour-types-and-rates.md) — work time, travel time, and exceptional hours.
* [**Register hours in the app**](/marketplace-packages-and-power-ups/power-ups/timesheets/register-hours-in-the-app.md) — register on work orders or through Timesheets.
* [**Review and export hours**](/marketplace-packages-and-power-ups/power-ups/timesheets/review-and-export-hours.md) — checks, statuses, and reports.

### Recommended order

1. Start with [**What is Time Sheets?**](/marketplace-packages-and-power-ups/power-ups/timesheets/what-is-timesheets.md).
2. Then [**set up employees and working hours**](/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-employees-and-working-hours.md).
3. Next create [**hour types and rates**](/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-hour-types-and-rates.md).
4. Then let employees [**register hours in the app**](/marketplace-packages-and-power-ups/power-ups/timesheets/register-hours-in-the-app.md).
5. Finish with [**reviewing and exporting**](/marketplace-packages-and-power-ups/power-ups/timesheets/review-and-export-hours.md).

### Important to know before you start

* Hours can be taken over automatically from work orders.
* **Timesheets** in the app requires the right employee settings.
* The selected status of hours affects checks and reporting.
* You export reports as Excel files.

### Webinar

Prefer to follow the process visually? Watch the webinar about Timesheets.

{% embed url="<https://www.youtube.com/watch?v=D8GonhoP2Vg&t=7s>" %}

### Related topics

* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.md)
* [**OutSmart Marketplace**](/marketplace-packages-and-power-ups/marketplace.md)
* [**Start a Power-Up trial**](/marketplace-packages-and-power-ups/marketplace/start-a-power-up-trial.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 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/marketplace-packages-and-power-ups/power-ups/timesheets.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.