Blog · 4 August 2026 · Jon McLachlan

Held. Not hidden.

When an hour crosses a client’s budget, software can tell you later, refuse the hour, or hold it for a decision. Only one of those keeps both the hour and the decision in the record. Updated in September 2026 with five recordings, four threads, four posts from X, the research on monitoring, and six books.

Forty hours bought. Forty logged by the eighteenth. On the nineteenth, someone on the team does two more hours of good work for the client and logs them. What happens next is the whole design question of a system that runs a firm’s money, and there are only three answers.

An alert is a report.

The first answer is to tell you. Most time trackers do this: the budget passes a threshold and an email goes out, within the hour on some, the next morning on others. It is useful. It is also history. By the time you read it the hours are in the month, the work is delivered, and the choice about who pays for it has been made by default. An alert changes what you know. It does not change what happened.

The people who build these tools know it. The budget email is a project feature, built to keep a project near its estimate. It was never built to hold a rule at the moment the rule is tested.

Ron Baker, who has argued since the 1990s that professional firms should abolish the timesheet, said the sharpest version on The Soul of Enterprise in 2016: “By definition, once you see something on a timesheet, it can no longer be managed.” We keep the timesheet and we take the point. A report about last week is a history lesson. Baker made the longer case to an accounting audience in 2011, in eight minutes.

The alert has a second cost. IDC’s February 2026 survey of 100 professional services firms for Kantata found a “3% delay in invoices being issued” at firms running on reports rather than records. The hour that is found late is billed late, if it is billed at all.

A refused hour disappears.

The second answer is to refuse the hour. Some trackers and suites can do this: at the budget, the timer stops or the entry is rejected with a message to contact the budget owner. It sounds like discipline. In practice it is the oldest failure in professional services with a new interface. An engineer described the older version on Hacker News in 2010. Told he was over budget at 54 hours on a 50-hour estimate, he “was not to charge any more time to that ticket. This essentially means ‘work for free.’”

The work still happens. The client still needed it. The record now says it did not happen, and the hour is eaten before anyone with authority has looked at it. Thomas Ptacek, who co-founded two security consultancies, put it plainly in 2024: “Serious consultancies routinely eat billable weeks of time in order to meet client success criteria and retain relationships.” David C. Baker has said for years that the average creative firm captures about 42% of its time rather than the 60% it should. A refusal makes that gap policy.

The people inside the refusal describe it in detail, and the threads about it are among the most upvoted in their fields. In November 2021 a first-year accountant wrote in r/Accounting that timesheets were the worst part of the job, “worrying about getting my hours up without going over budget on what I’m assigned on.” The thread reached 1,578 points and 171 comments. The reply with 851 points described a firm that sold itself as having no timesheets and then wanted an email to the partner every evening listing the day’s work. The reply with 103 gave the honest version of the rule: “If you spend 6 hours on something, put 6 hours on your timesheet even if the project budget you’ve been given is 2 hours,” followed by the admission that nobody had ever been spoken to for going over budget, only for logging too few billable hours. Another, at 369 points, said the trick was several hours of unpaid overtime a day so the numbers look right.

Four months earlier a thread titled “Everything they said about billable hours is true” had reached 1,109 points with the same shape: bill less than the schedule and the client is upset, bill more and the client is upset. “By far one of the worst thing in PA is charging times and the sweating over the budget,” wrote one reply at 255 points. Another, at 115, described managers who hand out ninety hours of work a week and want a meeting if anyone charges more than fifty-five. Every one of those firms had a budget and a wall. None of them had a decision.

Blair Enns, who has spent his career telling creative firms to stop selling hours, has the three-word version.

They are lies when the wall makes them lies. A record that stops at the budget is a record of the budget, not of the work. Jonathan Stark’s ten minutes on why nobody can buy an hour is the cleanest statement of what the client actually purchased, and it is not the entry the timer refused.

It also teaches the team the wrong lesson. Buddy Punch’s 2025 survey of 534 US workers found 30% feel time tracking is surveillance and 47% want access to their own records. A wall at the budget says the system is there to police them. The truth is the other way around. Every hour your team works counts. The only question is who pays for it, and that question belongs to the firm, not to the person who did the work at eleven at night.

A held hour waits.

The third answer is the one Ceed gives. The hour that would push a client over budget is saved, marked, and held. It waits for a named person, the account leader or an owner, to say yes or no. Nothing is billed quietly. Nothing disappears.

1. Logged

   2.0 h · Harbor & Vine · Revisions, round 3

2. Held

   Over the 40 h budget. Waiting for Dana.

3. Approved

   On the March invoice, at $150 an hour.

Approved, the hour lands on that month’s invoice at the rate in the agreement. Declined, it stays on the record and off the invoice, and the firm knows exactly what it chose to give away, when, and to whom. Both answers are true. Both are in the record. The budget held either way, because the rule was enforced at entry and not read about the morning after.

There is a quieter benefit. The system takes the question, so the account lead does not have to. Over-servicing is mostly people-pleasing at the account level, a yes said to be liked. A hold turns that yes into a decision made by the person whose margin it is, on the record, with the hours in front of them.

What the person logging sees.

One message a day. No timers, no screenshots, no wall.

The hold is framed as the client’s budget in question, never as the person’s hour. Everyone sees their own hours. The person who logged the two hours on the nineteenth knows at once that they are held, and knows by that afternoon whether the client is paying for them. Nothing they did is lost.

The threads on the other side of the timesheet are about walls and screenshots, not about hours. In August 2025 an engineer told r/ExperiencedDevs about a profitable startup that suddenly required everyone to log everything, then announced a loss three months later, a thread that reached 800 points and 179 comments. Two of the replies are the two designs in this post. One, at 127 points: “I work for a consultancy, here we track time to invoice our customers.” Another, at 54: “Honestly, this is better for the engineer. Lost 2 hours in a meeting? It now shows.” When the hour is counted for the client’s budget and the person’s own record, it protects the person. When it is counted to watch them, it does the other thing.

In May 2026 someone at a managed services provider asked r/sysadmin about tracking non-billable time in five-minute increments, 195 points and 157 comments. The top reply, at 287: “Make sure to add at least 30 minutes a day on the time sheet card for time spent updating time sheets.” Another, at 153: “all this leads to is employees padding their time.” The same month, one salaried remote worker’s answer to a new timesheet policy was liked 39,000 times.

Sixty-eight hours is the record the manager did not want. It is also true, and the only design that survives contact with a true record is one in which the hours are the person’s and the decision is the firm’s. Basecamp drew that line in its own terms of service in 2020, when it barred third parties from using its interface for anything that “remotely records, monitors, or reports” a user’s activity, with one exception.

Monitoring is the other design.

The hold is sometimes mistaken for surveillance, so it is worth saying what surveillance is. In August 2022 The New York Times reported that eight of the ten largest private employers in the United States track the productivity of individual workers, many in real time, where a pause can cost pay and, at one large insurer, low keyboard activity can cut a bonus. Jodi Kantor, who reported it with Arya Sundaram, explained it on CBS the next morning and on The Daily ten days later.

The American Psychological Association measured what that does to the people being watched. In its 2023 Work in America survey of 2,515 employed adults, 51% knew their employer monitored them. Of those, 56% said they typically felt tense or stressed at work, against 40% of the unmonitored, and 28% said they had experienced harm to their mental health at work, against 16%. Tara Behrend of Michigan State University, then president of the Society for Industrial and Organizational Psychology, said the data showed the tools do not make people work better: “They are counterproductive for the organizations that use them.”

Cory Doctorow, reading the same Times story, named the mechanism in a thread that August.

Bloomberg had filmed the industry two years earlier, twelve minutes on the software that watches while you work, and CBS returned to it in 2025 with the numbers larger. A hold measures none of that. It does not know when the person was at the keyboard, what they typed or whether they were idle. It knows one thing: that an hour, logged by the person who worked it, would take a client past the budget the client bought, and that someone with authority should say yes or no before the invoice does.

Closed means closed.

The last thing a hold gives you is a month you can close. Every hour was either within budget, approved past it, or declined past it, by a named person, on a dated record. When the month closes, the invoices, the statements and the margin are frozen and nothing in them changes after. That is a record a buyer, a lender or your own bookkeeper can read without asking what really happened, because what really happened is what it says.

What the books say.

Six books on trust, rules and records, none of them about time tracking, all of them about why a hold works and a wall does not.

• The Speed of TrustStephen M. R. Covey, 2006. Trust as an economic quantity, and why a firm that checks everything moves slower than one that checks the right thing once.
• DriveDaniel H. Pink, 2009. Autonomy, mastery and purpose, and what happens to all three when people are watched.
• It Doesn’t Have to Be Crazy at WorkJason Fried and David Heinemeier Hansson, 2018. The Basecamp position on time, attention and not watching people, from the people who wrote the policy quoted above.
• NudgeRichard H. Thaler and Cass R. Sunstein, final edition 2021. Choice architecture, which is what a hold is: the default keeps the hour, and the decision is made by the person whose margin it is.
• The Checklist ManifestoAtul Gawande, 2009. Why a rule enforced at the moment it applies beats a rule everyone knows and nobody checks.
• Measure What MattersJohn Doerr, 2018. What to measure and what not to, from the man who brought objectives and key results to Google. A held hour is a measure. A screenshot is not.

The firm behind Ceed also hosts The Security Podcast of Silicon Valley, 100 conversations since 2021 with the people who build and run security. Three of them are about walls, signals and who owns a decision.

• 95
  Pranava Adduri and George Gerchow of Bedrock DataMay 2026 · Stop saying no. Security leaders who put in guardrails instead of walls, which is the hold in another trade.
• 84
  Jack Cable, co-founder and CEO of CorridorDecember 2025 · What gets missed when nobody reviews the code, and why a signal beats a wall of alerts. The hour has the same problem.
• 91
  Neatsun Ziv on why asking developers to fix everything is a bad ideaMarch 2026 · Who should own a decision, and what happens when it lands on the person nearest the keyboard instead.

Two other shows have the long version. The Soul of Enterprise spent its 109th episode, in 2016, on trashing the timesheet. The Daily spent 24 August 2022 on the rise of workplace surveillance, with Jodi Kantor. Listen to both and the hold sits exactly between them: a record without a wall, a rule without a watcher.

Where the time trackers, the suites and the agreement-billing tools stand on this, row by row and dated, is on the comparison page. It credits them where they are ahead, which is real, and it names the one thing that happens here and nowhere else. The month that made us build it, with the numbers behind it, is in The invoice told us last. Why we built Ceed. The held hour as the stop loss against late payment is in The client paid late. The invoice was later., and as the change order at the hour in The agreement said 40 hours. The month said 47.

Sign upOr write to hello@ceed.so.

Questions.

Jon McLachlan is a co-founder of Ceed and of YSecurity, whose team logs its hours on the page pictured above. Published 4 August 2026, updated 11 September 2026. Corrections to hello@ceed.so, and they are dated when made.