Resource Planning Rule: Bill Utilization Only Against Work a Client Will Pay For
Which hours on the schedule actually convert into invoiced revenue, and which ones quietly consume retainer capacity? Separate billable, non-billable, and speculative hours in the schedule before you use utilization as a staffing signal.
By InnovaAI ResearchPublished
“Which hours on the schedule actually convert into invoiced revenue, and which ones quietly consume retainer capacity?”
Separate billable, non-billable, and speculative hours in the schedule before you use utilization as a staffing signal.
Treating a high utilization figure as proof of health and staffing up to protect it, when the real problem is that a third of booked hours sit on internal work, pitch decks, or retainer scope that was never priced.
Utilization percentages only predict revenue when every booked hour maps to work a client has agreed to pay for; speculative pitches, internal tooling, and unbilled revision rounds inflate the number while margin erodes. Time capture is the input that makes this distinction possible, and platforms such as Toggl, Everhour, and Hubstaff exist precisely because hours logged inside the project tool of record stay accurate enough to bill against. The same discipline applies to capacity views: Runn and Resource Guru both separate availability from demand, which is what lets an agency see that a 90% booked designer is 90% booked on work nobody invoiced.
- •Billable utilization is reported above 75% but monthly invoiced revenue is flat or falling
- •The schedule mixes client work, internal builds, and pre-sales scoping on the same capacity view
- •Retainer clients receive unlimited revisions or open-ended support windows with no hour ceiling
- •Time entries are logged after the week closes rather than as work happens
- •More than one person is booked on the same deliverable without a named owner