From a project management and financial control perspective, the lack of a clear separation between billable and non-billable tracked time creates significant issues, not only in reporting but also in day-to-day project governance.

In particular, time analysis becomes difficult to manage because Time Remaining for a task or project should consider only billable hours. Non-billable hours may legitimately exist (for example: bug fixing, rework caused by unclear or incomplete customer requirements, internal alignment, or corrective activities), but they represent overhead or inefficiency, not contractual delivery capacity.

If a Project Manager wants to understand how many hours can still be spent on a project according to what has been contractually agreed, the remaining effort should be calculated by subtracting only billable hours from the planned estimate. Mixing billable and non-billable time in the same “Time Tracked” value leads to distorted remaining hours, unreliable forecasts, and poor decision-making.

Having separate columns (or native fields) for billable and non-billable tracked time would significantly improve:

• accuracy of Time Remaining calculations

• project forecasting and EAC analysis

• transparency on inefficiencies and rework

• overall trust in time-based KPIs

As a final (slightly sarcastic) note: I keep seeing a growing number of releases focused on AI features and automation, while some fundamental aspects of project management data modeling remain unresolved. Leveraging AI or advanced automations on top of incorrect or ambiguous base data does not add value — it only accelerates wrong decisions.

Solid project management starts with solid data foundations.

Honestly, These columns should have been available since version 1.

Brendan W

What I honestly fail to understand is that the database already had the data.

It's not like we are asking ClickUp to change the infrastructure or anything.

All we want is to have a field that only sums-up the time entries that includes the billable boolean in the db.

That's something that it is already exposed in the API, so why on earth can't be achievable by a formula field?

Above all, it would be important to be able to calculate the billable times with their costs. A pure inf is only half...

Of course it's important!

I support. It is useful to be able to track estimates and time in the list, but less useful when non-billed time is included as it is now. This requires going to the dashboard to check.

This is so needed. I have an agency team with over 40 people and cannot get a simple report or view where I can view total time, billable time, non-billable time all within 1 single table or view. I have to have 1 card for billable time, 1 card for non-billable time and 1 card for combined/both meaning a whole heap of manual list scrolling, making paper notes to try and get a realistic view.

I would like to see billable and non-billable hours in the list view without having to go to a dashboard. I would also like to be able to sum each column.

These resources would be perfect for the financial.

They need to focus on work receivables and not just on monitoring the team and services performed.

I would like to see billable and non-billable hours in the list view without having to go to a dashboard. I would also like to be able to sum each column.