The simple definition
You quoted a project at 200 hours. Your team delivered it. When you reconciled at the end, they'd actually spent 260 hours. The extra 60 hours — paid out as salary, not invoiced to the client — is effort leakage.
Multiply that across every active project and every retainer client, and the picture gets uncomfortable fast. A services team that quotes consistent 28-30% margin will often close their year at 12-18%, and they won't have a single moment they can point at and say "that's where it leaked". It leaks slowly, in small pieces, across dozens of small decisions. That's why it's hard to fix.
The five places it actually hides
In our experience watching services teams across agencies, MSPs and consultancies, effort leakage shows up in five predictable patterns. None of them are dramatic. They're all small.
1. Scope creep (the obvious one)
The client asks for "just one more revision". The PM says yes. The designer spends 4 hours. Nobody logs it as scope. It comes out of the project's contingency — except contingency was 10% and you've already burned it. Multiply by 8 small additions on a 6-month engagement. That's 30+ hours of margin gone, and you don't have a change request to point at.
2. Untracked client tickets
For MSPs and agencies that mix project work with ongoing client support, this is the biggest leak we see. The client emails "quick question about Y". The engineer answers in 25 minutes. The 25 minutes don't get logged because "it's just an email reply". By the end of the month you've given away 15 hours of support work that the retainer didn't cover. The client doesn't know. You don't know. The margin sheet just looks slightly worse than expected.
3. Context switching
An engineer assigned 80% to Project A, 20% to Project B, actually spends 40 minutes a day switching mental context. The 40 minutes don't appear in time tracking — they're between tasks. But they're real, and they come out of your effective utilisation. A team built on heavy context switching has a measurable productivity ceiling that doesn't show up in any dashboard until you go hunting for it.
4. Rework and handoff loss
Designer hands off to developer. Developer asks questions that designer already answered in a comment thread the developer didn't read. Developer rebuilds something the way they understood it. Designer reviews, requests change, developer redoes it. Two hours of net delivered work cost six hours. None of it was malicious. All of it was avoidable. The handoff loss adds up to a measurable fraction of every multi-discipline project.
5. "Quick favours"
The client calls Friday afternoon — "any chance you could…?" Senior engineer spends 90 minutes Friday plus an hour Monday morning. It's not on the SOW. It's "relationship". On its own, fine. Across a year with three retainer clients, that's 100+ unbilled hours from your most expensive person. It doesn't feel like a problem until you total the column.
Why it stays invisible
The reason effort leakage is so persistent is that most services teams' tooling is structurally bad at catching it. Three reasons:
- Time goes into one tool, money lives in another. Time tracker is one app. Cost rates and bill rates are a spreadsheet maintained by finance. Project status is a third tool. By the time the three are reconciled, the leak is two weeks in the rear-view mirror.
- "Tickets" don't get tracked as hours. If your support work doesn't have a timer attached to it, the hours disappear into nobody's budget. They paid out of salary, but nothing visible debits the client retainer.
- Margin is a month-end question. Most teams compute margin once a month when finance runs the numbers. By then, you've already over-delivered. The signal arrives after the damage is done.
The four numbers that catch it
You don't need a complex margin model. You need four numbers visible to your delivery lead, every day:
- Hours worked vs hours budgeted, per project. Updated live as time is logged. If a project at 50% calendar time is at 65% hours, you have a leak forming.
- Effective bill rate per project. What you're collecting per hour of effort delivered. If quoted bill rate is $150/hour and effective rate is $120/hour, the difference IS the leakage — expressed in money.
- Untracked time per support client. For retainer clients, every email reply, slack thread, "quick call" should have a timer. If it doesn't, you can't tell if you're losing money on them.
- Utilisation per person, weekly. If your team is at 95% utilisation, you're either delivering with no slack or you're missing tracked hours. Both are red flags.
What "live" actually means
The biggest single change a services team can make is to move margin from a month-end report to a live number. Every hour logged should immediately:
- Move the project's actual-vs-budget bar
- Reduce the project's effective margin against the SOW value
- Flag if the project crosses a warning threshold (70% budget burnt at 50% calendar?)
That's not a sophisticated finance model. It's just connecting the time-tracker, the rate table, and the project plan into one live view. Most stitched-tool stacks can't do this because the three lived in separate apps. A services-team-shaped workspace can.
What the fix is not
The temptation is to clamp down with policy: "everyone must log time daily", "all email replies must be timed", "scope creep means a formal change request". Those policies aren't wrong, but they fail in practice because they shift the burden onto the people doing the work without giving them anything in return.
The better fix is to make the leak visible, not the policy stricter. When a delivery lead can see "Client A has consumed 14 untracked support hours this month" on a dashboard, they have a conversation with the client about a retainer adjustment. That's how the leak closes — by becoming visible enough to negotiate, not by being illegal to commit.
How BrioSync handles it
This was the design goal for BrioSync from the start: one workspace where projects, tickets, hours, cost rates and bill rates share a data spine, so margin is a live number rather than a month-end report. The features page goes into the specifics; the Free plan lets you put one project, one client and your team in for free, forever. If you'd rather see a walkthrough with your numbers, book a 25-minute demo.
The honest bottom line
Effort leakage isn't a discipline problem. It's a visibility problem. The teams that close at the margin they quoted aren't more strict — they just see the leak the day it happens, when it's still small enough to negotiate. Everything downstream of that — better SOWs, tighter retainers, healthier P&L — falls out of the visibility.
If you've never measured it, the most useful thing you can do this week is compute one number: across your last three closed projects, total the actual delivered hours and divide by the quoted hours. If the ratio is over 1.1, you're leaking. Most teams the first time they do this discover the ratio is closer to 1.3.