What project time tracking is
Project time tracking is recording hours against the thing they were spent on: a customer, a project, a task or an activity. The point is not surveillance. It is to give three people the answer they need: the consultant (what did I do this week?), the project manager (am I within budget?) and the owner (where is the capacity going?).
It works when it is cheap to log and specific enough to use. Too coarse (everything on "Customer A") and you cannot tell design from rework. Too fine (twelve codes per project) and people stop logging truthfully.
Track by project, task and activity
Start with two levels. A project says who is paying, and a task or activity says what kind of work it was.
- Project. One per engagement. This is what you invoice and budget.
- Task. The unit of planned work inside a project. Tasks carry the estimate, so you can compare estimate and time spent.
- Activity. Work that does not belong to a project: internal meetings, training, sales support, breaks. Keep a short list so not billable time is visible and not hidden inside a project.
In Matrix, the free Timesheet lets each employee log with a timer, a week sheet, from and to times, or just a total. With Project management, a person picks the task the time belongs to, also in the timer and on the phone. The task field can be off, optional or required, as you choose.
Each task then shows its estimate, the time spent and what is left. A task can have several employees, each with their own estimate, including external people such as a subcontractor.
Billable and not billable time
Billable time is time a customer pays for. Not billable time is everything else a person does at work. Both are legitimate. The mistake is not having not billable time. It is not seeing it.
A short list of not billable activities does most of the work: internal meetings, training, business development, admin. Review them monthly. If the admin and coordination overhead on a project is growing, that is information about the project.
Expenses follow the same rule. In the Timesheet, expense categories each have a rate, a unit and a suggestion of whether the expense can be billed.
For the effect on invoicing, see billable hours tracking software.
Utilisation rate, from the same hours
Utilisation rate is billable hours divided by the hours an employee had available. It is the number that connects project time tracking to the firm's revenue. Matrix's Timesheet shows it for each employee, team and week, and the available hours follow working hours and holidays.
What counts as a good rate depends on the role and the firm. Rather than repeat it here, read utilisation rate in consulting for how to calculate and define it, utilisation rate benchmarks for what a published benchmark shows, and how to improve consultant utilisation for what to do about it.
With Standard hours, utilisation is measured against each employee's own schedule. With Allocation and Resources, fixed reports on capacity and utilisation can also be downloaded as a file.
Watch the budget while there is time to act
Hours registered after the project ends are a report. Hours registered while it runs are a steering wheel. With Project management, a project has a budget in hours, a warning at the limits you choose, and the date the budget runs out at today's pace.
If the plan says the project needs 3 more weeks, you have a problem while you can still talk to the customer. Work that arrives after the plan is locked is collected in one place, as a basis for a change request.
To see the money, add Costs and rates. Every hour then gets a cost price and a rate, and the project shows budget, forecast and margin. See project profitability tracking for the metrics.
What Matrix shows
| You want to see | Where | Part |
|---|---|---|
| Your hours, expenses and utilisation | Week sheet, timer, utilisation per employee, team and week | Timesheet (free) |
| Time against tasks | Estimate, time spent and what is left on each task | Project management |
| Time against the budget | Hour budget with warnings and a run-out date | Project management |
| Money per project | Budget, forecast and margin | Project management with Costs and rates |
| Who is free | Booked and free per day, week or month | Allocation and Resources |
| Time against the schedule | Registered time and the difference each day | Standard hours |
Rolling it out in a firm
Project time tracking fails when it is introduced as a control and works when it is introduced as a tool. A short rollout helps.
- Decide what you want to answer. For example: is each project within its hours, and what share of our time is billable? Two or three questions are enough.
- Set up only the projects and activities you need to answer them. You can add more later. You cannot easily remove a messy list.
- Start with everyone, not a pilot group. Time tracking is only useful when the gaps are small. The Timesheet in Matrix is free for every user, so there is no login to ration.
- Run one payroll period, then review. Look for empty days, projects nobody uses and activities that swallow too much.
- Close the loop. Show the team the utilisation and the budgets they helped produce.
Common mistakes in project time tracking
Too many codes
Every extra choice is a decision the employee makes at the end of a tired day. Keep the list to what you will read.
Logging only billable work
If not billable time is missing, utilisation looks better than it is, and you cannot see where capacity goes.
Logging at the end of the week
Reconstructed weeks drift towards round numbers. Log daily, or let calendar suggestions do the first draft.
Never reading it
If nobody looks at the numbers, people notice, and the entries get worse.
Three questions for the weekly meeting
- Which projects are using hours faster than the plan?
- Which people are below or above their usual utilisation, and why?
- How much time went to work outside the plan, and does it need a change request?
Habits that keep the data honest
- Log daily, not weekly. A week's memory is thin by Friday. A timer or calendar suggestions help. In Matrix, Outlook and Google Calendar meetings appear as suggestions, and the employee approves each one.
- Keep the list short. Fewer projects and activities means better data.
- Approve weekly. Approval is when mistakes get caught, before the numbers are used.
- Remind, do not chase. Reminders for an unsent week or a forgotten timer replace emails.
- Read it back. Time nobody reads is time nobody logs well. Put utilisation and budgets in the weekly meeting.