Planned vs actual: how to see where your team loses hours

Planned vs actual is not just a reporting line. It is the fastest way to see where your team really spends time, where a project is leaking hours and where estimates were too optimistic.

If you only need to total hours at the end of the month, a spreadsheet is enough. If you want to understand why something took longer, what keeps repeating and where margin is slipping, you need to compare the plan with what actually happened.

What planned vs actual means

Planned hours are the hours you reserved in advance for a task, project, phase or week.

Actual hours are the hours that were truly spent on the work.

The gap between those two numbers is variance. In healthy teams, variance is not random noise. It is a signal.

Why the gap appears

The usual reason is not “people are slow”. In practice, one or more of these is happening:

• the scope was underestimated
• the work was interrupted by urgent requests
• part of the work was never planned
• hours were entered late and without context
• the task was not clearly defined
• the team was switching between too many things at once

In other words, planned vs actual is rarely an accounting problem. It is a process problem.

How to read the variance

Variance is not a problem by itself. The problem is not being able to explain it.

Situation	What it usually means	What to do
Actual is slightly above planned	Normal variation or a small underestimation	Review the estimate and record the reason
Actual is much higher than planned	Too many interruptions, hidden work or vague scope	Break the work into smaller pieces
Planned is much higher than actual	Too much buffer or a blocked delivery	Check whether the plan was realistic
The same gap repeats every week	The process is the issue, not one task	Add a review and adjust the planning method
One person is always off-plan	Overload or too much ad hoc work	Rebalance workload and priorities

If your team is always “late” against the plan, that does not automatically mean the team is disorganised. Very often it means the plan was never based on real data.

Which numbers matter

For most teams, a few clear indicators are enough:

1. planned hours per week or project
2. actual hours for the same period
3. the gap between planned and actual
4. repeated unplanned work
5. hours by employee, client or project
6. how often the plan changes during the week

If you do all of that manually, you quickly end up in yet another spreadsheet nobody wants to maintain. That is why the system needs to connect planning and time tracking in one place.

What it looks like in UnitLook

In UnitLook, planning, time tracking and projects are not three separate islands.

• in Capacity Planning, you reserve hours in advance
• in Time Tracking, you log what was actually done
• in Projects, you follow phases, deadlines and progress

When those three layers are connected, planned vs actual becomes simple to compare. You do not need to gather data from multiple sheets, emails and chat threads. You can see where the gap happened and react while the project is still alive.

That is especially useful for:

• service companies working by the hour
• project teams with fixed-fee work
• agencies that need to protect margin
• internal teams balancing planned and unplanned work

How to reduce the gap without micromanagement

The biggest mistake is using planned vs actual as a way to control people. That usually creates resistance.

A better approach is this:

1. Plan on the same rhythm

If work changes every day, do not plan only once a month. A weekly rhythm is realistic for most teams.

2. Log actual work every day

If hours are entered on Friday from memory, you are not tracking work. You are reconstructing it. Daily entry gives you a much cleaner signal.

3. Separate planned work from unplanned work

If support, incidents or internal admin keep leaking into project hours, the result will never be clear. Make that visible.

4. Look at patterns, not just one project

One project can slip off plan. If it happens repeatedly, the problem is in estimation or in the way the team works.

5. Turn variance into a rule

If a type of task is regularly underestimated, give it a more realistic buffer next time. That is how planning becomes better over time.

The real value

Planned vs actual is not just a metric for a manager. It is useful for the whole team.

The manager sees overload. The team sees where focus is slipping. The owner sees where margin is leaking. And everyone gets a more realistic view of what the work actually costs.

Conclusion

If you want to manage work properly, do not look only at total hours. Look at the relationship between what was planned and what was actually delivered.

That is where you will quickly see:

• where estimates were too optimistic
• where the team is losing time
• where the work is going off plan
• where you need a better system, not another spreadsheet

If you want to see how this works in a tool that connects planning, time tracking and projects, take a look at capacity planning, time tracking and pricing, or reach out for a demo.