What Your Projectworks Utilisation Numbers Are Really Telling You

A utilisation percentage can look like a simple number on a dashboard, but there is a lot more going on behind it.

If you are using Projectworks to keep an eye on utilisation, it is important to understand that the number you see means something different depending on which month you are looking at.

Last month tells you what actually happened. This month gives you a combination of actuals and plans. Next month is based entirely on what your team currently intends to do.

That distinction matters, particularly when you are using utilisation data to make decisions about capacity, scheduling, profitability and margins.

Last month's utilisation is a look backwards

When you look at last month's utilisation percentage in Projectworks, you are looking at actual activity.

The calculation is based on submitted timesheets, so the figure represents the hours your team actually recorded against the work they completed.

This makes it useful for understanding what happened and for spotting trends over time. You can look back and ask questions such as:

• Were people sufficiently utilised?
• Did actual hours broadly match what was expected?
• Were certain team members consistently under or over capacity?
• Did the amount of project work available match the team's capacity?

The catch is that last month's number is already history.

By the time you are reviewing it, the work has happened, the hours have been recorded and the opportunity to change that month's utilisation has passed.

That does not make the number less valuable. It simply means you should use it for learning rather than trying to use it as a lever for something that has already happened.

This month's number is a moving target

The current month is where things get a little more interesting.

Your utilisation figure is based on a combination of hours that have already been recorded through timesheets and the work that is still planned for the remainder of the month.

In other words, part of the number is actual and part of it is expected.

That means it can change.

Someone might log additional hours. A project might take longer than expected. A team lead might change a resourcing plan. Work might be added, moved or cancelled.

Each of these changes can affect the utilisation figure.

So if you check the number today and check it again next week, do not be surprised if it looks different. The month is still in progress, and the data is still developing.

This is where the number becomes particularly useful operationally.

Instead of simply asking, "What is our utilisation?", you can start asking, "What is changing, and why?"

That gives you a much more useful conversation.

Next month's number is a forecast, not a fact

Then we get to next month.

There are no timesheets for next month yet because, well, it has not happened.

That means the utilisation figure cannot be based on actual hours worked. Instead, it is calculated from the resourcing that has been planned by your team leads.

This makes next month's percentage a view of what the business currently expects to happen.

And that distinction is important.

A high forecast does not necessarily mean you are guaranteed to have a highly utilised team. It means the current resourcing plans suggest that is where you are heading.

Plans can change.

Projects can move. Clients can change their requirements. Work can be delayed. New projects can appear. People can become unavailable.

The forecast should therefore be treated as an early indicator rather than a promise.

Think of it less as a crystal ball and more as a weather forecast. It is incredibly useful for deciding whether you need to take an umbrella, but you might still get a surprise downpour.

The interesting bit is the gap between forecast and actual

This is where utilisation data can become much more valuable for decision-making.

Looking at one percentage in isolation only tells you so much. Comparing your planned utilisation with what actually happened can reveal where your assumptions are starting to drift.

For example, imagine your team was highly utilised last month, but the resourcing plan for next month shows an even higher level.

That might be exactly what you want to see.

Or it might be a warning sign.

Perhaps the team is being planned at a level that is difficult to sustain. Perhaps some projects are being scheduled too aggressively. Perhaps the forecast assumes work will start that has not yet been confirmed.

The number itself does not tell you which explanation is correct.

It tells you where to start asking questions.

And those questions are much easier to answer when you have visibility of both the actuals and the plans behind the percentage.

Why this matters for margins

Utilisation is not just a resource management metric.

It can have a direct impact on project profitability.

If your future resourcing plans look significantly stronger than what your recent actuals suggest is realistic, that difference deserves attention.

The earlier you identify it, the more options you have.

You might be able to adjust the schedule, redistribute work, review capacity with a team lead or have an early conversation with a client about timelines and scope.

Leave it until the work is already underway and your options become much more limited.

That is why reviewing utilisation regularly is about more than reporting a percentage to management. It is about using the information to spot potential problems while there is still time to do something about them.

Stop asking what the number is. Start asking what it means.

A utilisation dashboard is only as useful as the decisions you make from it.

Last month's figure can help you understand what actually happened.

This month's figure can show you how reality is developing alongside the plan.

Next month's figure can give you an early view of where your current resourcing decisions are taking you.

Put those three perspectives together and you have something much more useful than a single percentage.

You have a way to compare actual performance with current expectations, identify potential gaps and make better decisions before those gaps turn into bigger operational or financial problems.

Because the real value of utilisation data is not knowing the number.

It is knowing what the number is trying to tell you.