Time tracking for software teams
- Projects
- Tasks
- Timer
Hours land on the project and task a developer picks, as the work happens, not from memory at the end of a sprint.
342htracked across four projects
Track hours against projects, tasks and clients, with the activity and apps behind them and a record every developer can read, from a tracker light enough to run beside an IDE.
04:20 tracked today 71% average activity 45m idle, marked separately
00:42:19
Atlas API·PR #482 · rate limiting Northwind
Every client project starts with an estimate of hours. TeamTrek records the actual hours, by project and task, so the next quote starts from what the work really took.
Four projects, this quarter's hours against last quarter's. Atlas API, a hundred and twelve this quarter against eighty last, forty percent more. Mobile v3, sixty-eight against sixty, thirteen percent more. Client portal, a hundred and four against a hundred and twenty, thirteen percent less. Support retainer, fifty-eight against forty, forty-five percent more.
A representative quarter. Figures are illustrative until your own first month is tracked.
One light desktop app records the work while the timer runs, so a delivery lead can see the result without chasing the team.
Hours land on the project and task a developer picks, as the work happens, not from memory at the end of a sprint.
342htracked across four projects
Every hour carries the project and task it belonged to, ready to roll up by client.
4projects, one record
Keyboard and mouse input as a percentage of each interval. Never what was typed.
64%average activity this week
Which app or URL held focus, from code editor to browser, tied to the project.
12apps and URLs
Visual context when a team wants it. Developers see their own.
12captures across 4h 20m tracked
Share custom reports, and give clients visibility into the work on their projects.
1client, seeing their work
A small desktop app that keeps CPU and memory use low, and shows its own.
0.4%CPU used by the tracker
The same record wherever people work, and tracking continues offline.
3ways of working, one record
The hours are already recorded. See how many projects each person is on and how much time each spends on each one, then assign next month’s work to match.
An illustration of the idea. Figures are representative until your own first month is tracked. One person is 160 hours a month, and the people beside each project are derived from that.
620h available this month · 0h unallocated
Three things an organisation sets, and three every engineer can always see.
An admin sets the signals. Typed content isn’t recorded.
An admin sets the interval, or leaves them off.
Each person starts, pauses and stops their own timer.
The same list of signals, and their own activity record.
Any screenshot taken of their screen is open to them.
A running timer shows whenever tracking is on.
Rules on monitoring differ by location, and this page is not legal advice.
Anything else? Write to us at hello@teamtrek.app.
Track hours by project, task and client, and give clients visibility into the work on their projects. Start your 14-day free trial, or book a demo.