Where Team Hours Leak Before You Notice the Margin Problem

When a solo freelancer loses an hour, it hurts. When a small team loses an hour per person per day, that is 25 hours a week disappearing into nothing. Across a month, that is real money, and it rarely shows up clearly until a project closes and the margin looks wrong.

The leak usually is not laziness. It is structure. Or the lack of it.

The Handoff Gap

Every time work moves from one person to another, there is a gap. Someone has to get up to speed. They read the notes, check the files, maybe ask a question or two. That ramp costs 15 to 30 minutes per handoff depending on how well things were documented.

If you have three handoffs per day across a two-person team, that is an hour of overhead before anyone does anything billable. Over a week, it is five hours. Nobody logged it because nobody had a task to log it to.

Fix: set up a handoff task in every project. Make it a real time entry. When you can see it, you can manage it.

Internal Meetings Without a Budget

Team syncs, status calls, quick check-ins. These feel necessary. Some of them are. But they eat into project hours and most teams never track them accurately.

The problem is not that the meetings happen. The problem is that the time goes somewhere vague, like a general overhead category, and never gets looked at. So it keeps growing.

Log internal meeting time separately from client work. Every project, every week. When you run your monthly reports, you will see exactly how much meeting overhead each project is carrying. Some of it will surprise you.

The Approval Loop Nobody Counts

Client feedback cycles are part of the work. Everyone knows that. But most project estimates assume a clean loop: you deliver, client responds, you revise once, done.

In reality, the loop has more steps. You send the work. You wait. You follow up. You get partial feedback. You clarify the feedback. You revise. You send again.

Every one of those steps is time. Most of it goes unlogged because it feels like the cost of doing business rather than billable activity.

Track it anyway. Even if you never bill the client for approval overhead, seeing the real cost tells you what your project margin actually is. It also tells you which clients have expensive feedback loops and whether your rate accounts for that.

Context Switching Between Projects

Small teams often run three or four projects at once. Every time someone switches from one project to another mid-day, they lose focus time. Not a little. Research puts the number at 15 to 20 minutes to fully re-engage.

If someone switches context four times in a day, that is potentially an hour of output gone. Across a team of two, across a month, you are looking at a significant chunk of capacity that was never captured anywhere.

This is one of the reasons automatic screenshots are useful beyond proof of work. They create a passive record of when you were actually working on what. When you review them, the switching patterns become visible in a way that self-reported time logs rarely show.

What to Do With What You Find

You do not need to eliminate all overhead. That is not realistic. But you do need to see it.

Once you have a few weeks of honest data, you can set realistic overhead allowances per project, build those into your estimates, and stop acting surprised when margins come in thin.

A project that looks profitable at the proposal stage often is not by the time you account for all the hours nobody logged. The fix is not to track less. It is to track everything and then price accordingly.

The leak does not stop until you can see where it is.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots