Project time tracking in the timesheet your team already uses

Know where working hours go, project by project, without collecting spreadsheets at month end. Employees pick one of their assigned projects when they clock in or add an entry, and each project's monthly hours are ready to review and export.

Project time tracking in the timesheet your team already uses

How it works

From a project list to hours per project

Set projects up once. From then on, each entry carries the project picked when it's logged, so there is nothing to sort out later.

Step 1
Create projects and assign people

Create projects and assign people

Add a project with a name and an emoji, plus a code and a description if you use them, then assign the employees who work on it.

Step 2
Clock in to a project

Clock in to a project

Employees pick one of their projects in the Time tracker before Clock in, or on an entry they add for a past day.

Step 3
Review hours per project

Review hours per project

Each project has a monthly view with the hours logged per day and each person's worked and break hours.

Project hours

Hours per project, ready when the month closes

When project time lives in spreadsheets and chat, the start of every month goes on chasing team leads for numbers that rarely match attendance. Here each project has its own monthly page, built from the timesheets people already fill in.

  • Logged hours per day

    A chart of the hours logged on the project each day of the month. Current month and the arrows move between months.

  • Worked and break time per person

  • Filters by team, department and location

preview

Logging time

Project chosen when time is logged

Hours pieced together at the end of the week tend to come out rounded and incomplete. When the project is picked at clock-in, the record is right from the first minute. Employees see only the active projects they're assigned to, and can search them by name or code.

  • Time tracker before Clock in

    Pick a project in the Time tracker in the top bar, then clock in. Breaks count toward the same project as their shift.

  • Project on manual entries

  • One project for the whole autofill

preview

Export

Project hours for payroll, finance and client reports

Each of them needs the same numbers in a different shape. Export a month of attendance to Excel or CSV, grouped by project for totals or by entry for detail, and nobody retypes hours from one file into another.

Group by Project

  • One row per project, with its project code.
  • Worked and break hours for the month.
  • Approved overtime logged on the project.

Group by Entry

  • One row per time entry, plus rows for overtime, leave and public holidays.
  • The project and project code on each time entry.
  • The comment added to each entry.

Attendance policy

Required project per attendance policy

An optional field gets skipped, and a free-text note turns one project into five spellings. Turn on Project required in an attendance policy, and every entry from the people on it needs a project from their list. Add Comment required when you also want a note on the work. People on other policies log time with the project field optional. An employee on that policy who has no projects yet sees a message to contact their manager, and can clock in once they're assigned to a project.

Required project per attendance policy

Employee time

Hours by project for each employee

When someone splits the week across several projects, the split is usually the first thing people ask about. In an employee's Time section, the Projects view lists their hours on each project for the month, with worked and break time. In the timesheet, the project filter switches the Worked, Break and Overtime totals to one project.

Hours by project for each employee

Discover how PeopleForce
can benefit your time tracking

Project hours sit in the attendance record, so they follow the same rules, approvals and exports as every other hour, with no second system to reconcile.

A fixed project list for each person

People log time only to projects they're assigned to, so hours can't land on a project someone doesn't work on.

A fixed project list for each person

One approval for attendance and projects

Project hours are part of the timesheet each employee submits, so the approvals in their attendance policy cover both.

One approval for attendance and projects

Overtime linked to projects

Where overtime tracking is on, an overtime request can carry a project, and the project export shows approved overtime next to worked hours.

Overtime linked to projects

Archive for finished projects

Archived projects leave employees' project lists, and the hours logged to them stay for later reports.

Archive for finished projects

More in Time

Explore the rest of Time

Timesheets, overtime and project hours share one attendance record, and attendance policies set the rules for all of them.

Monthly timesheets with approvals

Clock in and out, add entries or autofill working days where the policy allows it, then submit the month for approval.

Learn more
Timesheets
icon

Leader

Summer 2026
icon

Users Love Us

Milestone Summer 2026
icon

Regional Leader

Europe Summer 2026
icon

High Performer

Europe Summer 2026

Security and operational continuity

Certifications, granular access and full control over what happens to your data and equipment.

ISO 27001 certified, GDPR compliant, Google Cloud data centres in Europe
G2Best Support

Frequently asked

Do we need a separate tool to track time by project?

Can employees see every project?

Can we require a project on every entry?

How is a day split across several projects?

What happens when a project ends?

How do project hours get to payroll or finance?

Is overtime linked to projects?

Is there an API for projects?

See where your team's hours go, project by project

In a demo, we'll walk you through Time from start to finish: projects and the Time tracker, monthly timesheets and their approval, overtime requests, and the attendance export grouped by project.