Should You Track Fractional Hours on Projects?

Every consulting firm has a policy for fractional hours. Very few have the right one.

I have spent over 30 years managing audit and professional services teams, and in that time I have seen the full spectrum — from teams that systematically rounded down and gave away hundreds of billable hours, to managers who tracked every minute so obsessively that they lost clients over it.

The question of whether to track fractional hours sounds like a technical decision about timesheets. It is not. It is a management philosophy question disguised as an administrative one, and getting it wrong costs you in ways that do not show up on the invoice.

The 370 Hours That Disappeared

In the early 2000s, I witnessed a large engagement at one of Brazil's ten biggest banks. A team of 12 auditors was working on a complex, multi-month project — the kind of engagement where hours run high and every week matters for budget execution.

The team had a habit, inherited from a previous manager, of consistently rounding down their fractional hours. A task that took an hour and forty minutes got logged as 1.5 hours. A two-hour-and-ten-minute review became 2 hours flat. It was not intentional underbilling — it was just what they had always done. Round down, keep it clean, move on.

Nobody questioned it. The timesheets looked tidy. The weekly reports seemed fine.

When the firm's quality control partner reviewed the engagement at the end of the project, the numbers told a different story. After reconciling actual work performed against logged hours, the audit revealed that the team had failed to bill approximately 370 hours to the client.

Three hundred and seventy hours. At professional services billing rates, that is not a rounding error — it is a mid-size car. And it happened not because anyone was dishonest, but because twelve people each shaved a few minutes off their entries every day for months.

The math is relentless. If each team member rounds down an average of 10 minutes per day, that is 50 minutes per person per week. Across 12 people over a 5-month engagement, that is roughly 360–400 unbilled hours. The numbers matched almost exactly.

This is the invisible cost of rounding down: it is never dramatic enough to trigger an alarm on any single day, but it compounds silently until someone runs the reconciliation and discovers the gap.

The Manager Who Tracked Every Minute

Around the same period, I worked alongside a project manager who took the opposite approach. He ran engagements at mid-sized food industry companies, and he demanded absolute precision from his team. Every minute was to be logged. Every entry required a daily description of the specific activities performed. No rounding. No estimation. No shortcuts.

On paper, this sounds like the solution to the 370-hour problem. In practice, it created a different one.

His team spent a meaningful portion of their day documenting their day. The overhead of minute-level tracking, combined with mandatory daily narratives, shifted the team's focus from doing the actual work to proving they were doing the work. The administrative burden became a drag on the engagement itself.

More importantly, it created a culture of micromanagement that the team felt every hour. When your manager reviews your timesheet entries to verify whether a task really took 23 minutes or 28 minutes, the implicit message is: I do not trust your professional judgment. Over time, that message corrodes morale, initiative, and the quality of the work itself.

The result was predictable. The quality of the audit work declined — not because the team was incompetent, but because their energy was being redirected from substance to surveillance. The firm lost one of the clients served by that manager. Not over billing disputes. Over the quality of the deliverables.

Precision without purpose is just overhead.

The Real Question Behind the Question

These two stories sit at opposite ends of the same spectrum, and both ended badly. That is not a coincidence — it is the nature of the problem.

The question "should I track fractional hours?" is actually three questions bundled together, and each one has a different stakeholder:

The partner or business owner asks: "Are we capturing all the revenue we earned?" They want granularity because every unbilled minute is lost margin. Their fear is the 370-hour scenario.

The project manager asks: "Can I see if this engagement is on track against budget?" They want accuracy because they need to make staffing and scope decisions in real time. Their fear is discovering a budget overrun after it is too late to correct — a pattern that drives most consulting projects over budget.

The consultant on the team asks: "Can I just do my job without spending 20 minutes a day on timesheets?" They want simplicity because the administrative burden feels disproportionate to the value it creates. Their fear is the micromanagement scenario.

A good fractional hours policy satisfies all three. A bad one optimizes for one at the expense of the others.

What Actually Works: The Practitioner's Framework

After three decades of experimenting, failing, and refining, here is the approach I have settled on. It is not perfect, but it balances accuracy with sanity.

Track in 15-minute increments. Not to the minute (too granular, too much overhead), and not in full hours (too much revenue leakage). Fifteen-minute blocks are the smallest unit that captures meaningful billing differences without turning timesheets into a surveillance tool.

There is an argument for the legal industry's 6-minute model (tenths of an hour), and it works well in law because legal billing has trained clients to expect that granularity. In consulting and auditing, 6-minute increments tend to create more administrative friction than the additional precision justifies.

Round to nearest, not down. This is the single most impactful policy change a firm can make. When teams habitually round down, the losses compound invisibly. When they round to nearest — 22 minutes becomes 0.25 hours, 38 minutes becomes 0.5 hours — the over-rounds and under-rounds tend to cancel each other out over time, and total billed hours stay much closer to actual hours worked.

Require task-level descriptions weekly, not daily. A weekly summary of what was accomplished on each project is useful for quality control, client reporting, and institutional memory. A daily minute-by-minute narrative is surveillance. The weekly cadence gives managers the context they need without burdening the team with daily paperwork.

Make the tool fast enough that compliance is not a burden. This is the part most firms get wrong. They set a reasonable policy — 15-minute blocks, round to nearest, weekly descriptions — and then force the team to enter it into a tool that takes 90 seconds per entry. Multiply that by 8–10 entries per day across a 12-person team, and the tool itself becomes the bottleneck.

The entry mechanism matters as much as the policy. If logging time takes more than a few seconds, people will defer it. And deferred entries become estimated entries, which become the rounding-down habit that cost someone 370 hours.

The Uncomfortable Truth About Fractional Hours

There is a deeper question here that most articles about time tracking avoid, and I think it is worth stating plainly.

Every fractional hours policy is a compromise between two realities that cannot both be fully satisfied: the firm's right to be paid for the work it performed, and the team's right to work without being monitored at the minute level.

If you optimize entirely for revenue capture, you get micromanagement. If you optimize entirely for team autonomy, you get revenue leakage. The skill of managing a professional services team is finding where the line sits for your firm, your clients, and your people — and being honest that whatever you choose involves a trade-off.

The firms that handle this well are not the ones with the most precise timesheets. They are the ones where the team understands why the policy exists, trusts that it is fair, and has a tool that makes compliance effortless.

Key takeaways

• Rounding down fractional hours compounds silently — a 12-person team can lose 300+ billable hours on a single engagement without anyone noticing.
• Tracking to the minute creates overhead and a micromanagement culture that can degrade work quality and cost you clients.
• 15-minute increments with round-to-nearest is the sweet spot for most consulting and auditing teams.
• The tool matters as much as the policy — if logging time is slow, people defer it, and deferred entries become inaccurate entries.

The best fractional hours policy is the one your team follows consistently — not the one that looks most rigorous on paper. Build for compliance, not for control.