CheckedSourced, dated, and no one pays us

Time Tracking / Basics

Time Tracking · Basics

What Time Tracking Is Actually For

Six legitimate purposes, and the one that is usually the real motivation. Choosing which you are doing determines everything else.

Facts checkedAugust 2026 For: Everyone

Most time tracking is introduced without anyone stating why. The purpose then gets assumed — usually the worst available one — and the data becomes defensive before it becomes useful.

So this is the first decision, and it is not a formality.

For a vendor-side perspective, Monitask also has a page on employee time clock software.

The six legitimate purposes

Billing

Where work is billed by time. The oldest reason and the least ambiguous.

Requires accuracy per client and per matter, and a level of granularity that other purposes do not need.

Pricing and estimating

Knowing what work actually costs to deliver.

Your own historical figures are the only estimate source that reflects how you really work. See estimating from your own data.

Requires actuals including non-billable time, or the numbers flatter you.

Finding where effort goes

Usually the most surprising and the most actionable.

Meetings, context switching, rework, waiting on approvals, admin. Almost always larger than assumed.

Requires categories for non-productive time, safely recorded. Without those, this purpose is unachievable.

Capacity planning

How much the team can actually deliver, based on what it has delivered.

Requires aggregate data over months, not precision per person.

Compliance

Where the law or a contract requires records of hours worked.

Requires completeness and retention, and it is the one purpose where the record itself is the deliverable. See time records as employment records.

Protecting people

Records showing consistent overwork are evidence, and they are more often in the worker's favour than not.

Rarely stated as a purpose and worth stating, because it changes how the exercise is received.

The purpose that is usually the real one

"We want to know whether people are working."

Say it or do not do it. The damage comes from pursuing this while claiming one of the six above.

And consider whether it is answerable this way. Time records do not measure work; they record what someone said they did. Used as evidence of effort, they produce effort-shaped records and nothing else. See tracking time against measuring people.

If the genuine question is whether remote people are productive, the answer is in outcomes — delivery, quality, whether the work is getting done.

Why choosing one matters

The purposes need different data.

Purpose Needs Does not need
Billing Accuracy per client, granularity Non-billable detail
Estimating Actuals including non-billable Real-time precision
Finding effort Non-productive categories Client-level precision
Capacity Aggregate over months Individual detail
Compliance Completeness, retention Project categorisation

Trying to serve all of them produces a system that serves none, because the category structure and the granularity pull in different directions.

Pick one primary purpose. Others can be secondary and should not drive the design.

What follows from the choice

The categories. Billing needs clients; finding effort needs activity types. These are different lists.

The granularity. Billing may need six-minute units; capacity planning does not.

Who sees what. Compliance data has retention and access requirements; estimating data does not.

The reporting. Per client, per project, per activity, per period — the primary purpose decides. For broader independent background, see NIST Privacy Framework.

And what you say to people. Which is the part that determines whether any of it is accurate.

Saying it

Write it down. One paragraph: what this is for, who sees it, what it will not be used for.

Give it to everyone who records.

Repeat it whenever the data is used.

And hold to it. A single use for an unstated purpose ends honest recording permanently. See what time data must never be used for.

For individuals

The same first question, with lower stakes and the same consequence.

Most solo tracking fails because it was started without a question. Data accumulates, nothing is learned, the habit lapses.

Pick one: what is my real hourly rate, am I quoting accurately, which clients cost more than they pay, where does non-billable time go.

Track what answers it. Look at it monthly. Stop when you have the answer.

See time tracking for freelancers.

The short version

Six legitimate purposes: billing, estimating, finding effort, capacity, compliance, protecting people.

Pick one as primary. They need different categories and different granularity, and serving all produces a system serving none.

"Are people working" is usually the real motivation — say it or do not do it, and note that time records cannot answer it honestly.

Write the purpose down and give it to everyone recording.

And most solo tracking fails because it started without a question.