Fichaloto

Blog Capacity

Planned, clocked, charged: three numbers that should match and usually do not

7 min read

Most companies can tell you what they planned and what they invoiced. Very few can tell you, for a given week, whether those two things are related.

The gap nobody measures

A services company runs on three numbers per person per week, and they live in three different places. Planned hours sit in whatever tool does resourcing. Clocked hours sit in the time-and-attendance system, usually bought to satisfy a legal obligation and never looked at again. Charged hours sit in the project tool, typed in on Friday afternoon from memory.

Because they live apart, nobody compares them, and the interesting questions have no answer. Is the person we planned full time on the migration actually spending their week on it? Are we invoicing hours nobody clocked? Is somebody quietly working fifty hours while the plan says thirty-five?

What each number is actually good for

They are not three attempts at the same measurement. Each answers a different question and it is worth keeping them separate rather than picking a favourite.

  • Planned is an intention. It is what you promised the client and what you told the person to work on. It is the only one of the three you can change in advance, which makes it the one worth arguing about.
  • Clocked is presence. It says somebody was working, when, and where. It is the number with legal weight and the one you cannot negotiate after the fact.
  • Charged is attribution. It says which piece of work the time went to. It is the one that feeds margin, and the one most likely to be a rounded guess typed in three days late.

Make the clock do the attribution

The cleanest fix is to stop asking people to remember. If somebody is assigned to exactly one project, the clock can attribute their day to it without asking. If they are on several, the clock asks once, at the moment they start — which is the only moment they actually know the answer — and the day flows into that project when they clock out, to the exact minute.

That single change collapses two of the three numbers into one. Clocked and charged stop being separate acts of data entry with a three-day gap and a rounding error between them.

What is left is a comparison worth putting on a screen: planned against clocked, per person, per week. Not to police anybody — to notice that the migration you staffed full time is getting twelve hours a week, four months before the deadline makes that obvious.

The line between measuring and surveilling

This is worth stating plainly, because tools in this category tend not to. Comparing planned to clocked hours is a management question. Tracking keystrokes, taking screenshots or logging idle time is a different thing, it damages trust faster than it recovers hours, and in much of Europe it is also unlawful without a specific justification and a works-council agreement.

A well-drawn line is: measure the work, not the worker. When they started, when they stopped, which job it went to, and where they clocked from if the job needs a site record. Nothing about what was on their screen.

Frequently asked questions

What if somebody works on three projects in one day?

They clock out of one and into the next, or they charge the split by hand afterwards. Both are supported. What does not work is guessing on Friday, which is what happens when the clock never asked.

Does this need everybody to clock in?

It needs the people whose time you want to compare. In Spain everybody has to anyway, so the marginal cost is choosing a project from a dropdown once a day.

All of this is built into Fichaloto. See how it works.

Keep reading