What a Manager Should See
Managers need enough to allocate work and to notice someone struggling, and less than most systems give them by default.
Reference
The default manager view in most time products is everything about everyone they line-manage, in daily detail. That is more than the job requires and it creates the drift this collection warns about.
What a manager actually needs
Team capacity against commitments, to allocate work.
Project effort against estimate, to know whether something is going wrong.
Hours beyond contracted, to notice someone working excessively.
Approval exceptions: the unusual entries that genuinely need a decision.
Unbilled effort distribution, to see who is carrying the invisible work.
All five are answerable at team level or as exceptions, and none requires browsing a person's daily record.
What they do not need
Everyone's daily start and finish times, routinely.
A comparison of individual hours.
Individual billable percentages.
Detail of what someone worked on hour by hour.
Any activity data, which should not exist.
The test: what decision does this view inform? Most detailed individual views inform none, and they exist because the product displayed them.
The exception principle
Show what needs a decision, not everything.
A total far from the person's normal range.
A retrospective edit near a payroll cut-off.
A missing clock-out.
Hours beyond a threshold, sustained.
A dispute raised.
This is both less intrusive and more useful: a manager looking at six exceptions attends to them, where one looking at forty timesheets attends to none.
When detail is legitimate
A specific query from the worker about their own record.
A wage dispute, where the record is the evidence.
A specific investigation, authorised and scoped.
Approving an unusual entry the exception view surfaced.
In each case the access should be logged with a reason, and reviewed — which protects the manager as much as the worker.
Configuring it
Default the manager view to team aggregate and exceptions.
Individual detail available on a click that records why, rather than open by default.
No cross-team visibility unless the role requires it.
Review permissions quarterly, which reliably finds people who changed role and kept access.
Telling managers why
Worth doing explicitly, because otherwise the restriction reads as distrust of them.
The record is written by the person it describes, so its accuracy depends on their cooperation.
A team that believes their daily pattern is being read writes defensively, and the manager loses the capacity data they actually needed.
Logged access protects the manager too, in any subsequent accusation.
Most managers accept this readily once the reasoning is given, and resent it if the restriction arrives without one.
Explaining the restriction to managers
Without the reasoning, a limited view reads as distrust of the manager.
Say that the record is written by the person it describes, so accuracy depends on their cooperation.
Say that a team who believe their daily pattern is read will write defensively, and the manager loses the capacity data they needed.
Say that logged access protects the manager in any subsequent accusation.
Most managers accept this readily once it is explained and resent it when the restriction arrives without a reason.
Configuring the default view
The setting that determines how the system is experienced.
Default to team aggregate and exceptions.
Individual detail behind a click that records why.
No cross-team visibility unless the role requires it.
No routine display of anyone's daily start and finish times.
Review permissions quarterly.
Most products default to the opposite and it is a settings change rather than a product limitation, which means it is a decision someone made or failed to make.
Check the difficult case
Use project time tracking application to frame one representative test for this issue. The useful evidence is not the marketing description itself but the record created when a worker corrects an entry, a manager reviews it and an administrator exports it.