Billable percentage
What would helpThis is a problem on our side. It is being monitored and does not need action from you.
This is a problem on our side. It is being monitored and does not need action from you.
Where it stands
Weekly, up to the latest week on file
Why it is where it is
This accounts for the hours that were not billable, out of 23709 hours logged, 4919.8 hours in all.
2993.7 hours logged against it, of which 2382.7 hours are billable.
How this was measured: The hours booked to this project that are not marked billable, summed from the entries themselves. Each entry is counted once, under whatever it was booked to.
2093.3 hours logged against it, of which 1665.9 hours are billable.
How this was measured: The hours booked to this project that are not marked billable, summed from the entries themselves. Each entry is counted once, under whatever it was booked to.
842.8 hours logged against it, of which 667.6 hours are billable.
How this was measured: The hours booked to this project that are not marked billable, summed from the entries themselves. Each entry is counted once, under whatever it was booked to.
653.5 hours logged against it, of which 517.9 hours are billable.
How this was measured: The hours booked to this project that are not marked billable, summed from the entries themselves. Each entry is counted once, under whatever it was booked to.
478.1 hours logged against it, of which 380.8 hours are billable.
How this was measured: The hours booked to this project that are not marked billable, summed from the entries themselves. Each entry is counted once, under whatever it was booked to.
These are attributed and are inside the total above. They are folded together because a list this long stops being something a person reads, and the ones worth acting on are at the top. Real logged time that does not trace to a project on the tracker. It is inside the total and cannot be named, which is a gap in how the time was booked rather than in the hours.
Every entry is counted once, under what it was booked to. The share above is billable hours over logged hours, so this is the other side of it: moving any of the time below into client work is the only thing that moves the number, and some of it should not move. The buckets are what each entry was booked to. The hours grain carries no admin or internal classification of its own, so this page names the work rather than inventing a category for it. 3376.5 hours of non-billable time could not be traced to a project on the tracker, and is carried here rather than dropped from the total.
What we checked, in order
We read this workspace and nothing in it answers this.
There is no ruled order of checks for Billable percentage yet. Three of these ordered diagnostics exist and they attach to the profit share, an account under the floor, and absorbed work. This metric is not one of them.
An ordered set of checks is worth more than a list of things to look at, because the order is what stops the most expensive move being tried first. Writing one for this metric is a decision about how it should be diagnosed rather than a gap in the data.
Root cause
This is a share of hours that were LOGGED, so both halves deserve naming. It falls when client work loses ground to internal projects, admin and meetings, which is the reading it is usually given. It also falls when internal work is logged promptly and client work is logged late, because then the denominator is complete and the numerator is not. Those two look identical on this tile and they need opposite responses: one is a calendar problem and the other is a recording problem. On this workspace the non-billable side is spread rather than concentrated, across 6 buckets, the largest being Q2 Rebrand and Packaging Refresh at 611.1 hours. Spread like that it is usually a recording question before it is a mix question, so read this next to timesheet completion first.
What to do now
The audit is done and it is in the section above. Start with Q2 Rebrand and Packaging Refresh and DTC Site Replatform. Ask of each one whether the firm still means to buy it, which is a different question from whether anybody is working hard enough.
Adding process here is the expensive mistake, because it costs everybody time to fix something that is usually concentrated in a few commitments, and the section above shows which. Of 23709 hours logged, 18789.2 hours were billable. One caution before acting on the list: if client hours are simply being logged late, more process makes this number worse by adding to the non-billable pile, and timesheet completion is the tile that tells you which of those you are looking at.
This closes no measured driver above, and does not claim to.
What stops it coming back
Decide what internal time the firm is buying, name it, and hold the rest to the band. This share holds where somebody has decided what non-billable work is for.
The share is a residual of decisions nobody made in one place: an internal project here, a standing meeting there, each defensible alone and none of them weighed against the others. Naming the internal commitments the firm intends to carry turns the leftover into a budget rather than a surprise, and it makes an overrun visible while it is still one meeting rather than a quarter. The two-sided half matters as much: a share running well above the band for a long stretch means nothing is going into the firm itself, and that bill arrives later as stalled process and no training.
This closes no measured driver above, and does not claim to.
What happens if this is ignored
A sagging billable share is capacity the firm is paying for and not selling, and it does not announce itself, because everybody is occupied the entire time. It surfaces two layers away: income per person slides while headcount holds, that reads as a revenue problem, and the answer is a sales push made against hours that were never actually free. The reverse case is quieter and also real. A share running high for long enough means the firm's own work is getting none of the week, and the cost of that arrives as the thing everybody complains about and nobody has time to fix.
Is this target still telling you anything
We read this workspace and nothing in it answers this.
The window spans a measurement change, so its periods are not one series: compute path changed: demo-history-seed@1 to live-serving-rollup@3
How this metric is measured changed inside the period this section would look back over, so counting hits across it would be counting two different measurements as one. This fills in once the whole window sits on one basis.
Share of logged hours that are billable to clients. Hours logged as billable to clients divided by all hours logged.
Of the hours the team actually works, how many are on client work rather than internal projects, admin, and meetings about meetings. The healthy level is about 75%. It reads work mix, where utilization reads capacity: the two fail differently. It sits on this board against target ~75%.
- Window
- Stated as of Oct 9, 2026. The period the reading covers is set by its source and is not stated on this tile.
- How it is counted
- Hours logged as billable to clients divided by all hours logged.
- Source
- Time tracking, as of Oct 9, 2026
- Drivers
- Reasoned from this metric's own definition and sources. The driver breakdown is not composed for this tile yet, and the section below says what it would take.