The Project Where Two of Us Tracked Time Differently

We Thought We Were on the Same Page

I brought in a collaborator for a mid-sized web project. We split the work cleanly, or so I thought. She handled design, I handled development and client communication.

We agreed to split the fee based on hours contributed. Seemed fair. We'd both track our time and compare at the end.

We did not agree on what to track.

What I Tracked

I tracked everything. Development sessions, obviously. But also client calls, feedback reviews, revision rounds, the twenty minutes I spent reformatting her design files so they'd work with my build, the follow-up emails after each meeting.

By the end of the project I had about sixty-two hours logged.

What She Tracked

She tracked design sessions. Pure heads-down work. She did not track the calls she joined. She didn't count the time she spent reviewing my staging builds to check how her designs were rendering. She didn't log the revision rounds.

She came in at thirty-one hours.

The Problem

The project paid a flat fee. We had agreed to split it proportionally based on hours. When I shared my log, she was surprised. When she shared hers, I was frustrated.

She had genuinely worked more than thirty-one hours. I had seen her online at all hours. But she hadn't tracked it. So from her perspective, her number was accurate. From mine, it looked like she had under-reported.

We spent an uncomfortable afternoon trying to reconstruct her actual hours. We never got it right. We eventually agreed on a split that neither of us fully believed in.

What This Did to the Relationship

We finished the project. The client was happy. But something shifted between us. Not dramatically. Just a low-level friction that hadn't been there before.

We've worked together since, but I always think about that conversation now. The one where two people with genuinely good intentions looked at the same project and came up with completely different realities.

The Mistake Was Not Agreeing Upfront

We should have defined what counts as billable before the first timer started. Calls, yes or no. Review time, yes or no. File prep, yes or no. Admin, yes or no.

Instead we both made individual judgment calls and then collided at the end.

I was not wrong to track the calls. She was not wrong to focus only on design work. We were both following our own logic. But we needed shared logic.

What We Do Now

Before any shared project, we set up the same time tracker with the same project and the same task categories. We define what goes in each bucket before anyone starts a timer.

Calls get logged under client communication. Review time gets logged under review. Neither of us makes a unilateral call about whether something counts.

We also do a midpoint check. We look at both logs halfway through and flag anything that looks off. That way the conversation happens in the middle of a project, not at the end when money is already sitting on the table.

The Bigger Lesson

Tracking time is not just about billing clients. On collaborative projects it is how you stay fair to each other.

If you and a partner have different definitions of what counts as work, you are not splitting a project, you are each running your own version of it and hoping the numbers line up at the end.

They won't. They never do unless you agree first.

A shared tracker and a shared definition of billable time costs nothing to set up. The alternative cost us a lot more than money.

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