Time tracking software
for workforce planning

See where team capacity is going: how much of the week reaches project work, who has room, and what past work took, in hours as TeamTrek recorded them.

  • Hours by team, member and project
  • This period beside the last
  • Project and routine work, shown apart
The next eight weeks 4 teams · 45 people · 1,800h a week 410h free in week 7
Delivery14 people 812h
Studio12 people 504h
Support10 people 404h
Accounts9 people 622h

Commitment is counted from tracked hours, not from a wish TeamTrek shows the weeks; the plan is yours An illustrative quarter. Teams and figures are examples.

How committed each team is for the next eight weeks. Delivery, 14 people: W1 98%, W2 96%, W3 95%, W4 92%, W5 88%, W6 74%, W7 60%, W8 52%. Studio, 12 people: W1 86%, W2 94%, W3 97%, W4 99%, W5 95%, W6 88%, W7 72%, W8 64%. Support, 10 people: W1 70%, W2 78%, W3 85%, W4 90%, W5 93%, W6 95%, W7 96%, W8 92%. Accounts, 9 people: W1 55%, W2 60%, W3 72%, W4 80%, W5 96%, W6 98%, W7 90%, W8 76%. Across the four teams there are 1,800 hours in a week.

A 40-hour week is rarely 40 hours of project work.

Meetings, admin and task-switching take time a plan never counts. TeamTrek’s time tracking software shows where a team’s hours went: project work, operations or internal work.

Weekly target, four people 160:00
Project work 98:00
Ongoing operations 35:00
Internal meetings and admin 21:00

154:00 recorded · 6:00 below the target

One week for a team of four. The weekly target is 160:00. Project work took 98:00, ongoing operations 35:00, and internal meetings and admin 21:00, which is 154:00 recorded in all, 6:00 below the target.

How much of the week reached project work?
98:00 of the 160:00 target.
Where did the rest of the hours go?
Operations 35:00, internal work 21:00.
What stays apart from project work?
Each kind of work, set up as its own project.

A representative week for a team of four. Figures are illustrative.

Total work hours, detailed by person, team, task, project and client.

See who carries the load and on what: hours and activity open from a team to each person, and from a project to its tasks and clients, beside last period.

Read the same hours By team By person By project By client

Engineering 3 people team 412h +51h
Maya R. person 148h +22h
Jonas K. expanded person 139h +9h
Client A · Platform rebuild client · project 96h +4h
Build task 64h +2h
Review task 32h +2h
Support queue project · operations 28h +5h
Team meetings and admin project · internal 15h 0h
Priya S. person 125h +20h

One engineering team of three people, 412 hours this period, 51 more than the last. Maya R. 148 hours, 22 more. Jonas K. 139 hours, 9 more, expanded: Client A, Platform rebuild 96 hours, 4 more, of which the Build task is 64 hours and the Review task 32 hours; the Support queue project 28 hours, 5 more; team meetings and admin 15 hours, unchanged. Priya S. 125 hours, 20 more.

One IT and tech services team, one period. Each total is the sum of the rows beneath it, so every lens shows the same 412 hours.

One shared report of team hours for workforce planning.

Workforce planning software built on tracked time puts every team’s hours in one report: pick the period, set the last one beside it, and download it as CSV for the meeting.

TeamTrek prepares the hours, and the plan is yours to make. Figures here are illustrative.

teamtrek.app/reports/teams
Engineering and Design · This period beside last 680h this period
Compare with the previous period Each figure set beside the period before.
Member breakdown Who the hours belong to, by name.
Project and task workload Where the hours landed.
Activity context The average activity behind each line.

Download as CSV, filtered to the period above.

A workforce plan line, backed by the hours beneath it.

When someone asks why a line adds a person or moves work, TeamTrek already holds the answer: the trend, last period’s comparison and who has room, by team, project and task.

Plan line · Platform rebuild: add one team member

Question from leadership: why?

Project hours, six periods 120h to 186h, up every period
Against the last period +15h (186h against 171h)
Who carries it now Jonas K. 96h · Maya R. 62h · Priya S. 28h
Who has room, last week Priya S. −12:00 · Maya R. −3:30 · Jonas K. +1:15

One plan line, to add a team member to the Platform rebuild, with the records under it. The project ran from 120 hours to 186 hours over six periods, rising every period. Against the last period it is 15 hours more, 186 against 171. It is carried now by Jonas K. with 96 hours, Maya R. with 62 and Priya S. with 28. Against last week’s target, Priya S. is 12:00 under, Maya R. 3:30 under and Jonas K. 1:15 over.

A representative plan line for one consulting team. The line is the planner’s own, and TeamTrek holds the records beneath it.

Plan work from TeamTrek’s actual hours in four steps.

  1. 01

    Track the work

    The team starts the timer against a project and task, online or offline, with operations and internal work set up as projects of their own.

    Kinds of work 3, tracked apart

  2. 02

    Compare the periods

    Set this period beside the last, by team, member and project, over weeks, months, years or dates of your own.

    Engineering +51h

  3. 03

    Place the work

    See who has room against the weekly target, and managers assign the next project or task to the person who can take it.

    Priya S. −12:00 vs target

  4. 04

    Check the plan

    Set the period you planned beside the period that happened, and adjust the next plan from the difference.

    Platform rebuild +15h

Fair questions about time tracking software for workforce planning

Anything else? Write to us at .

Start every workforce plan
from the hours that happened.

Try TeamTrek’s time tracking software for workforce planning free for 14 days, no credit card required, or book a demo.