Time tracking and billing belong together
Time tracking and billing belong in the same system because tracked hours that never reach an invoice are not billable, and unbilled work is the most common way a growing agency loses margin without noticing. A 2026 review of 168 agency engagements found a median 9% of paid delivery time was delivered and never invoiced. Keeping the two apart is what makes that number invisible.
Key Takeaways
A 2026 review of 168 agency engagements across 42 agencies found 9% of paid delivery time was delivered but never invoiced.
The gap appears in three forms: forgotten entries, time filed to the wrong project, and unrecorded scope creep.
Realization rate is the share of tracked time that reaches an invoice. Most agencies have never calculated it.
You can measure your own leakage in one afternoon by comparing tracked hours against invoiced hours for a single month.
The gap between hours worked and hours billed
The Landing Platform Agency Margin Report 2026, published 5 July 2026, reviewed 168 agency engagements across 42 agencies with teams of 5 to 60 staff. Its figures come from Landing Platform's own agency account base, so read them as one vendor's sample rather than a census. It compared hours logged against hours actually billed. The finding was that 64% of time was billable and invoiced, 19% went to admin and coordination, 8% was leave and internal work, and 9% was delivered but never invoiced.
That last 9% is the number most agencies never see, because it is invisible in a tool that only records hours and invisible again in a tool that only records invoices. It only becomes visible when you compare the two. The same report found that 62% of the agencies it onboarded had no live per-client view of profitability, and where one existed it was usually a spreadsheet reconstructed quarterly. The leak is not discovered by analysis. It is discovered, if at all, when the financial year closes.
Why separate tools create the gap
Billable leakage is the term for work that was performed for a client and never turned into an invoice line. It happens in three recurring forms, and none of them are caused by dishonesty.
The first is forgetting. A designer finishes a comp, moves to the next task, and the ninety minutes they just spent never gets logged. Three days later they reconstruct Tuesday from memory and a Slack timestamp, and the reconstructed number is lower than the real one. The second is misfiling: the time lands against the wrong project, so the project that lost money looks healthy while the project that made it looks like it overran. The third is absorption, where the extra revision was never written down, the work was done, and the contract was never amended.
Each of these is small, which is exactly what makes them expensive. Ten minutes a day per person across a ten-person team is roughly 300 hours a year. At a 150 dollar blended rate, that is 45,000 dollars of work that was performed and never invoiced.
What putting them together actually changes
Time-to-invoice integration means a time entry attaches to a project and the invoice draws from that tracked work, so there is no copy step between them. That matters more than it sounds, because a copy step is a step that can be skipped, rounded, or forgotten, and nobody has to notice when it is.
Three practical gains follow. You can answer how much time a project actually took without exporting anything into a spreadsheet. You can see a project approaching its budget while the work is still in progress, which is the only point where changing scope is still a conversation rather than a dispute. And month-end stops being a reconstruction exercise, because the hours and the money already agree with each other.
Realization rate: the metric worth watching
Realization rate is the percentage of tracked time that actually gets invoiced. Billable utilization is a different number: the share of your team's total time that is billable at all. Most agencies know their utilization. Far fewer know their realization rate, and it is usually lower than they expect.
The distinction matters because you can have healthy utilization and poor realization. That is precisely what happens when time is tracked carefully and then lost during invoicing. Track realization per client rather than in aggregate, because an agency can sit at an acceptable average while one client quietly runs at half, and the average is exactly what conceals it.
A useful review takes an afternoon. Pick your last quarter, total the tracked hours per project, total the invoiced hours per project, and compare them. The projects with the widest gap are the ones where your estimate is wrong, and your estimates are what you price future work on.
Fixed-price work still needs tracked time
There is a common argument that time tracking is pointless on fixed-price projects because you are not billing by the hour anyway. This is backwards, and the same report supports the correction: 52% of the projects in the sample hit scope creep within a year, and scope creep is only measurable if the hours are captured.
This is the reason Agencly attaches every time entry to a project rather than keeping a standalone timesheet. A timesheet is a report about the past. A time entry that carries a project, a budget, and a billable rate is a billing instruction, and it cannot drift away from the invoice because they are the same record. The discipline is to separate two questions. What did the client agree to pay for, and what did the work actually take? Only the second question is affected by your time entries, and it is the one that tells you whether the next project of this shape is profitable or whether you are subsidising it. An agency that never tracks fixed-price time is not protected from overruns. It is simply unable to prove them, which means it repeats them.
A worked example
Take one client, one month, three projects. The team logged 412 hours across all three. The invoices for the same period covered 361 hours. That is a realization rate of 87.6%, which puts this client in the leak the report describes.
Now break the 51-hour difference down. Eleven hours were internal meetings that were never client work and correctly excluded. Six hours were a scope change the client approved verbally but nobody added to the contract, so nobody billed them. Six hours were admin on their account. That leaves 28 hours, about 7% of everything logged, which was client work performed and never invoiced.
That 28 hours is the useful output, not the 87.6%. At a 150 dollar rate it is 4,200 dollars for a month, and it is the same project every month. The fix is not a new timesheet. It is a rule: any work on a project attaches to that project the day it happens, and anything logged against a project is reviewed before the invoice goes out, so the gap has to be explained before it can be invoiced. Run this exercise quarterly and the number either falls or it becomes something you have priced into the rate card.
A practical way to check your own leakage
You do not need new software to find out whether you have a problem. Pick one month, export the hours your team logged, and export the hours you invoiced. Compare the two per project.
If the tracked total is materially higher than the invoiced total, you have a realization gap. Subtract the parts that are legitimately explainable: non-billable internal time, approved write-offs, and scope genuinely outside the signed contract. Whatever remains is the work you performed for free. Most agencies running this exercise for the first time find a figure in the high single digits, which is consistent with the 9% median in the report.
Run it again the following month after changing how time is captured. If the gap does not move, the problem is the process rather than the tooling, and no software will fix it for you.
Where this belongs in your stack
Time tracking is not a feature to bolt onto invoicing, and invoicing is not a feature to bolt onto project management. All three describe the same event: work happened for a client, it took time, and money is owed. When one system holds that whole chain, the time entry, the project budget, and the invoice line all describe the same reality, and client disputes stop being about whose spreadsheet is right.
If you are deciding what to connect first, start with the time entry. It is the cheapest field to add and the hardest to reconstruct weeks later. Our guide to agency management software covers how the rest of the chain fits together, and the time tracking module shows how entries attach to projects and flow into billing. The money side of the same problem is covered in what an agency finance dashboard should track.
Frequently asked questions
Do we need time tracking if we mostly do fixed-price work?
Yes, and especially then. You will not bill the hours, but they are the only objective evidence you will get about whether you underquoted. Without tracked time a fixed-price overrun stays invisible until the project ends, so you repeat the same mistake on the next one. Track the time, then bill the agreed scope.
What is a good realization rate for an agency?
Most teams never measure it, which is the real problem. The 2026 review of 168 agency engagements found 9% of paid delivery time was delivered but never invoiced, so anything under roughly 90% is worth investigating. Track it per client rather than in aggregate, because a healthy average can hide a single client running at half.
Should time tracking be automatic or manual?
Manual entry is accurate right up until the moment it becomes tedious, and then it is wrong. The failure is rarely dishonesty, it is the ninety minutes nobody wrote down. The practical middle ground is to lower the cost of entry: fewer fields, the project picked from context, and a weekly review instead of a daily one.
How do we stop scope creep from eating our margin?
Capture it, then bill it. The same 2026 review that found 9% of delivery time unbilled also found 52% of projects hit scope creep in a year. Scope creep only destroys margin while it stays invisible. Once the extra work attaches to the project as it happens, the conversation about charging for it happens while it is still a small change rather than a year-end surprise.
Is this the same as improving utilization?
Related but not the same. Utilization is how much of your team's time is billable at all. Realization is how much of the billable time you billed actually made it onto an invoice. You can have healthy utilization and poor realization, which is what happens when time is tracked carefully and then lost during invoicing. Our [agency ops stack guide](/blog/agency-ops-stack-2026) covers where the two overlap.
Run your agency from one workspace
Projects, billing, contracts, and client communication in one place. 14-day free trial.