# Time tracking (Timesheet)

<p class="lead">Log the hours worked on each project and task and review the team's time by project and by person, without side spreadsheets.</p>

The **Timesheet** is where each person reports how much time they spent on each project. With hours logged, you know what each deliverable costs, who is overloaded, and which projects are taking more than planned. Use it daily on the project team and weekly in management.

[[roles: Company, Employee]]

!image[Timesheet screen with hours logged by person, project and task](/assets/img/erp/timesheet.webp)

## Before you start

- The projects and tasks must already exist. Create them in *Project > Projects*, as described in [Projects and tasks](#/project).
- The person logging hours must be a member of the project.
- The user's role must have permission for the Timesheet. Check it in [Roles and permissions](#/user-roles).

## Log hours worked

All time spent on a project becomes an entry, so the team's effort is visible.

**Menu path:** *Timesheet*

<ol class="steps">
<li>Open <strong>Timesheet</strong> in the side menu.</li>
<li>Click the <strong>+</strong> button (Create).</li>
<li>Select the project and the task you worked on.</li>
<li>Enter the date, the number of hours, and, if there is a field for it, a short description of what was done.</li>
<li>Click <strong>Save</strong>. The entry appears in the list and adds to the project total.</li>
</ol>

:::tip
Log your hours on the same day you work them. Entries made from memory at the end of the month are almost always wrong.
:::

## Correct an entry

Picked the wrong project, date, or number of hours? Edit the record instead of creating a new one.

**Menu path:** *Timesheet*

<ol class="steps">
<li>Open <strong>Timesheet</strong> and find the entry in the list.</li>
<li>Click the record's edit action.</li>
<li>Correct the necessary details.</li>
<li>Click <strong>Save</strong>. The totals are updated.</li>
</ol>

:::warn
Deleting an entry removes the hours from the project totals. Prefer editing when the error is only in the amount or date.
:::

## Review hours by project

Before billing a client or closing a project, check the total hours spent on it.

**Menu path:** *Timesheet*

<ol class="steps">
<li>Open <strong>Timesheet</strong>.</li>
<li>Use the available filters to limit the list to the project and period you want.</li>
<li>Check the entries and the total hours shown.</li>
<li>Compare with the plan and with progress in <em>Project > Projects Report</em>.</li>
</ol>

## Review hours by person

The per-person view shows who is overloaded and who has spare capacity for new tasks.

**Menu path:** *Timesheet*

<ol class="steps">
<li>Open <strong>Timesheet</strong>.</li>
<li>Filter by the user and the period you want to review.</li>
<li>Check whether the logged hours match the expected work schedule.</li>
<li>Talk with the person about gaps or overages before closing the period.</li>
</ol>

## Complete flow

1. The project and tasks are created in *Project > Projects*.
2. Each member logs their hours in *Timesheet*, ideally daily.
3. The manager reviews by person every week and corrects what is needed.
4. At close, the manager reviews by project and uses the total to bill or assess profitability.

## Frequently asked questions

### Can I log hours on a project I am not a member of?
Usually not. Logging depends on being linked to the project. Ask the project owner to add you as a member in *Project > Projects*.

### Does the Timesheet calculate payroll automatically?
No. The Timesheet records project hours. Payroll is generated in the HRM module, in *Payslip > Payroll*, based on the salary defined in *Set Salary*. Use the hours as support when checking it. See [HR, attendance, leave, and payroll](#/hrm).

### What is the difference between the Timesheet and Attendance?
Attendance, in *HRM > Attendance*, records presence during the workday. The Timesheet records which project and task that time was spent on. The two complement each other.

### How often should I review the hours?
A weekly review by person and a review by project at month-end close are usually enough. The sooner an error is found, the easier it is to fix.

## Next steps

Use the hours to track your projects and check on the team's routine.

:::related
project, hrm, dashboards
:::
