Hours by team
- Teams
- Hours
- Period
Every team’s hours for any period, in one report.
6teams in one report
TeamTrek shows how hours were spent by team and project, who has room, and whether a busy month was a one-off or the new normal, so you can place next month’s work and rebalance before you hire.
Every planned hour here opens into the months it was drawn from.
A capacity plan for December across three teams. Design tracked three hundred and twelve hours in November and is planned for three hundred and forty of its three hundred and sixty hours of capacity, leaving twenty hours free. Engineering tracked four hundred and eighty-six hours and is planned for four hundred and fifty-five of its five hundred and twenty, leaving sixty-five free. QA tracked one hundred and sixty-eight hours and is planned for two hundred against a capacity of one hundred and sixty, which is forty hours over. Nine hundred and ninety-five hours are planned in all against one thousand and forty hours of capacity. A representative plan; the figures are illustrative.
Whether you are placing next month’s work, planning for a busy season or deciding whether to hire, these eight views put the actual hours in front of you.
Every team’s hours for any period, in one report.
6teams in one report
How many hours each project took, and which teams carried them.
112hon one project this month
Reports show who is logging fewer hours than expected, and who is logging more.
3people with room this week
How each person’s hours split across projects and tasks.
4h 50mon Atlas redesign today
Trends show whether a busy month was a one-off or the new normal.
3months side by side
Set a quarter beside the same quarter last year, for a team or a project.
+9%hours vs the same quarter
Apps and URLs tied to tasks, and screenshots where used, show what the hours went on.
2apps on Atlas redesign
Managers assign next week’s or next month’s projects and tasks, with the hours in view.
5assignments for next month
Read the top track first: the team’s month, split by project. The bottom track is one person’s day inside it.
One team, Engineering, over four months. September took four hundred and sixty-two hours, October four hundred and seventy-one, and November four hundred and eighty-six, each against a capacity of five hundred and twenty hours a month. Those three months average four hundred and seventy-three hours. Sixty-five hours of leave are already booked for December, which leaves four hundred and fifty-five hours of capacity, and that is what December is planned for.
A representative plan. Everything the figure shows is drawn from hours the people it describes recorded themselves.
In TeamTrek, an admin switches on the signals that record the hours, and every team, project and person view is built from them, so the plan you make rests on the same facts as the report you read.
Employees see their own record and the same settings as everyone else.
Only an admin can change these settings. Everyone on the team can see them.
People start the timer on a project and task, and the hours are recorded as they work.
Step 1 of 4 · Record the hours
Read hours by team, project and person for any period, and see who has room.
Step 2 of 4 · See the hours
Set this month beside last month and the same month last year, to see whether a busy month was a one-off.
Step 3 of 4 · Check the pattern
Place next month’s work, rebalance before you hire, and have the hours to back a hire if rebalancing isn’t enough.
Step 4 of 4 · Act on it
Three things an organization sets, and three the person whose work gets tracked can always see.
Team leaders and managers see their teams, the owner sees all.
An admin switches on the signals. Screenshots are optional.
Time and activity are recorded while tracking is on.
Their own hours, projects and tasks, in the same detail.
Every team member can see which signals are on.
A running timer shows whenever tracking is on.
Rules on monitoring differ by location, and this page is not legal advice.
0.0M+
hours tracked every month
0
teams run their week on TeamTrek
0%
of planned months finished inside capacity
AgencyWe said yes to a project in March that there were never going to be hours for. The plan would have shown us that in ten seconds.
A commitment caught early
StudioOur planning numbers used to be what somebody thought a month took. Now they are what the last three months actually took.
Planning from the record
DeliveryThe hiring case wrote itself. Three months of hours against the capacity we had was the whole argument.
A hire, argued from hours
Names, quotes and figures on this page are placeholder content for a representative team. Replace them with verified customer results before launch.
Anything else? Write to us at hello@teamtrek.app.
Start a 14-day free trial of TeamTrek’s capacity planning, no credit card required, or book a demo.