Time tracking software
for project performance

Understand the effort behind every project: review last week’s record, adjust this week, and start the next project from what the last one took.

  • This period beside the last
  • Hours by project, task and phase
  • Activity level beside the hours
Five projects, by kind of work 2,862h tracked · 2,600h estimated 1,600h on build
Platform rebuildAcme Corp 980h +180h
Support retainerNorthpeak 612h +72h
Mobile releaseOrbit Studio 520h −80h
Brand siteQuay Studio 410h +10h
Internal toolinginternal 340h +80h

Every hour carries its project, task and kind of work Nothing here grades a project An illustrative portfolio. Projects and figures are examples.

Five projects, each divided by the kind of work inside it. Platform rebuild for Acme Corp: 470h of build, 210h of rework, 180h of meetings and 120h of admin, 980h against a 800h estimate. Support retainer for Northpeak: 380h of build, 70h of rework, 92h of meetings and 70h of admin, 612h against a 540h estimate. Mobile release for Orbit Studio: 300h of build, 40h of rework, 110h of meetings and 70h of admin, 520h against a 600h estimate. Brand site for Quay Studio: 250h of build, 60h of rework, 60h of meetings and 40h of admin, 410h against a 400h estimate. Internal tooling for internal: 200h of build, 30h of rework, 70h of meetings and 40h of admin, 340h against a 260h estimate. Across the five, 2,862h against 2,600h estimated, of which 410h was rework.

A project can take twice the effort before anyone notices.

Projects that run over rarely do it all at once: the weekly hours climb for weeks, and TeamTrek’s time tracking software shows the climb while the project is still running.

Week 1 24h
Week 2 26h
Week 3 31h
Week 4 38h
Week 5 46h
Week 6 57h

222h across six weeks

One project over six weeks, in hours: week 1, 24 hours; week 2, 26; week 3, 31; week 4, 38; week 5, 46; week 6, 57. That is 222 hours across the six weeks.

Which week did the effort start to climb?
Week 3, at 31h.
How much more is the latest week?
57h, up from 24h in week 1.
What shows where the extra hours went?
Hours by task, and who carried them.

A representative project over six weeks. Figures are illustrative.

A project total that opens into tasks and people.

Set up each phase as a task, and every phase shows the hours, activity and people behind it, with the change since last week.

Atlas redesign project 128h 72% +11h
Planning phase · task 14h 81% 0h
Design phase · task 41h 74% −6h
Build expanded phase · task 58h 67% +14h
Jonas K. person 34h 66% +9h
Maya R. person 24h 68% +5h
Review phase · task 15h 79% +3h

One project, Atlas redesign, 128 hours this period at 72 percent average activity, 11 hours more than last period. Planning 14 hours at 81 percent, unchanged. Design 41 hours at 74 percent, 6 hours fewer. Build 58 hours at 67 percent, 14 hours more, expanded: Jonas K. 34 hours at 66 percent, 9 more, and Maya R. 24 hours at 68 percent, 5 more. Review 15 hours at 79 percent, 3 hours more.

One IT and tech services project, one period. Each total is the sum of the rows beneath it, and phases are tasks.

Pick the projects and the period, and the report is built.

Project performance software built on tracked time keeps each project’s hours and activity in reports: pick the projects and the dates, choose what the report carries, and download it as CSV.

TeamTrek shows the hours and activity, and the review is yours to run. Figures here are illustrative.

teamtrek.app/reports/projects
Project report · Atlas redesign, Mobile app v2, Brand site 285h this week
Compare with the previous period Each project set beside the period before.
Task breakdown Each project opened into its tasks.
Member breakdown Who the hours belong to, by name.
Activity context The average activity behind each line.

Download as CSV, filtered to the period above.

A project performance question, answered from the record.

When someone asks why a phase took 58 hours, TeamTrek already holds the answer: the tasks, the people, the activity and how the effort moved, beside a similar finished project.

Review line · Atlas redesign · Build: 58h

Question from leadership: why 58 hours?

By task Components 31h · Integration 15h · Fixes 12h
By person Jonas K. 34h · Maya R. 24h
How the effort moved 16h, 19h, 23h across three periods · 67% average activity
Beside a similar finished project Mobile app v1 · Build: 52h at 77% activity

One review line, the Build phase of the Atlas redesign at 58 hours, with the records under it. By task: components 31 hours, integration 15 and fixes 12. By person: Jonas K. 34 hours and Maya R. 24. The effort moved 16, 19 and 23 hours across three periods, at 67 percent average activity. A similar finished project, the Mobile app v1 build, took 52 hours at 77 percent activity.

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

Understand project performance with TeamTrek in four steps.

  1. 01

    Track to the project

    People start the timer on a project and task, online or offline, with each phase set up as a task of its own.

    Atlas redesign · Build 58h

  2. 02

    Read hours and activity

    Open the project table to see each phase’s hours with the activity level beside them, and who spent them.

    Build 58h · 67%

  3. 03

    Compare the periods

    Set any period beside the one before, and one project beside another, to see where effort is climbing or easing.

    Atlas redesign +11h

  4. 04

    Keep the finished record

    When a project ends, its record by task and period stays on hand as the reference for the next project’s review.

    Mobile app v1 · Build 52h

Fair questions about time tracking software for project performance

Anything else? Write to us at .

Know every project’s performance
from the hours behind it.

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