Organization against last month
- Hours
- Activity
- Change
Total hours, activity level, projects and people, each with the change since last month.
+12%hours vs last month
Teams get compared on impressions, so every review starts from a different story. TeamTrek sets each team’s hours, activity level and project effort side by side, giving every conversation the same figures.
Every row here opens into the weeks, projects and people behind it.
One week across four teams. Design tracked three hundred and twelve hours at seventy-four per cent activity over five projects, with six people. Engineering tracked four hundred and forty hours at seventy-eight per cent over eight projects, with eight people. QA tracked one hundred and sixty-eight hours at sixty-nine per cent over three projects, with four people. Support tracked two hundred and thirty-two hours at seventy-two per cent over four projects, with six people. That is one thousand one hundred and fifty-two hours across twenty projects for the week. A representative week; the figures are illustrative.
Whether you are preparing a review, weighing one team against another or answering leadership, these eight views give you figures to point to.
Total hours, activity level, projects and people, each with the change since last month.
+12%hours vs last month
Reports by team put each team’s hours, activity level and project effort in one view.
4teams in one report
A list of each person’s hours logged, number of projects and activity level.
63people in one overview
Hours and activity level for each project, with its client and number of members.
31projects in one table
Project tables show net, manual, and idle time in separate columns.
45midle, in its own column
Weekly and monthly charts of hours and activity level show how a team’s pattern runs.
4weeks charted
Pick a week, a month, or a custom date range, and every number follows.
30days in one report
Reports download as CSV, and custom reports can be shared with leadership.
CSVdownload and share
The top track sets two teams beside each other for one month. The bottom track is one person’s day inside Team A.
One team, Design, over four weeks. Week forty-four took two hundred and eighty-eight hours at seventy-one per cent activity. Week forty-five took three hundred and twelve hours at seventy-four per cent, twenty-four hours more. Week forty-six took two hundred and sixty-four hours at sixty-nine per cent, forty-eight hours less. Week forty-seven took three hundred and twelve hours at seventy-four per cent, forty-eight hours more. That is one thousand one hundred and seventy-six hours over the four weeks, an average week of two hundred and ninety-four hours, and seventy-two point one per cent activity across them.
A representative team. Everything the figure shows is visible to the people it describes, in the same detail.
In TeamTrek, an admin switches on the signals that record the work, and every team report, person view, and project table is built from them, so a comparison never mixes one measure with another.
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.
Switch on the signals once, so every team’s hours, activity and projects are recorded the same way.
Step 1 of 4 · Record alike
Choose which teams to compare and a week, a month or a custom range, and every number follows.
Step 2 of 4 · Pick the view
See each team’s hours, activity level and project effort in one view, then open a person or a project for detail.
Step 3 of 4 · Read together
Use the comparison in reviews and coaching, decide whom to support, and share one report with leadership.
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
weeks of history before a review
AgencyOne team looked like it was falling behind for a month. Its weeks were normal; the other three had taken on extra work.
A team cleared by its own record
StudioReviews used to open with somebody’s impression of the quarter. Now they open with the weeks, and the conversation is about the work.
A review that starts from the record
DeliveryThe quiet week turned out to be a release freeze. Nobody had to guess, because the week before and the week after were right there.
A dip explained, not assumed
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 team performance analytics, no credit card required, or book a demo.