Who Owns the Clock

Ask who is responsible for the time clock and you will get four partial answers.

The practical lesson in “Who Owns the Clock” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring getting teams to meet deadlines, the provider website can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

Facilities installed it and fixes it. IT maintains the network and the software. Payroll consumes the output and chases the exceptions. HR writes the policy about clocking in. Operations lives with whatever the arrangement produces.

For a separate benchmark relevant to “Who Owns the Clock”, consult the Microsoft Project documentation. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

Each is responsible for a piece. The question this collection is about — where the paid day begins — sits between all of them and belongs to none.

What the absence of an owner produces

Terminal placement decided on cabling, which sets the boundary.

Prompts added to the punch screen by whoever needed data, which lengthens the queue.

Rounding and grace periods changed during an upgrade, which changes pay.

A security search introduced after the clock was installed, which moves the boundary again.

Each change was reasonable within the department that made it, and none of them was assessed against the question nobody owns.

The symptom

Nobody can answer a simple question: which activities are inside the paid day at this site, and who decided.

Every department can answer their part — the terminal is here because of the cable, the policy says clock on arrival, the rounding is five minutes — and none can answer the whole.

What the owner needs

Not a new department. One named person with a standing responsibility and enough authority to be consulted.

They need the boundary document described earlier in this collection, and the right to be told before a change that affects it: a terminal moved, an entrance closed, a search introduced, a uniform rule changed, a rounding setting altered, a shift pattern adjusted.

That consultation list is the whole mechanism. It is four or five triggers added to existing change processes.

Where the role usually sits best

Not with facilities, who do not see the pay consequence. Not with IT, who see neither the pay nor the operation.

Payroll has the data and frequently lacks the standing to question an operational decision.

HR has the standing and often not the data.

In practice the arrangements that work put it with whoever owns workforce or people operations, with payroll producing the figures and a standing line into the site change process. What matters more than the department is that it is a named person rather than a committee.

The annual job

A page per site, reviewed: the boundary document, the terminal positions, the queue measurement, the rounding settings, and the edge figure from the access-to-punch join.

Half a day per site per year. It is the entire ongoing cost of having this under control, against an exposure measured in thousands of hours.

The change trigger that matters most

A refurbishment. Sites are reorganised every few years and the clock gets moved, the entrance changes, the changing room relocates, and the boundary shifts without anybody recording that it did.

A single line in the project checklist — confirm terminal position against the boundary document — catches nearly all of it, and it is the cheapest control described anywhere in this collection.

What to do if nobody owns it now

Produce the boundary document for one site and circulate it. It is an afternoon's work and it has the useful property of being unanswerable: nobody can read it and continue to believe the question has been decided.

The owner usually emerges from the conversation that follows, because once the gap is visible somebody will want it closed and that person is the right one.

The budget question that follows

An owner without a budget can describe the problem and not fix it, and the fixes in this collection sit in other people's budgets: a terminal is capital, a shift pattern is payroll, a changing room is facilities.

So the ownership has to come with a route to those budgets, which in practice means the role reports somewhere senior enough to ask for them. Where it does not, the predictable outcome is an accurate annual report describing the same unresolved items for years, which is worse than no owner because it documents the knowledge without the remedy.

The interim version, where nobody senior will take it, is to give the role to whoever already runs the clock and to give them a standing item on an existing agenda. It is weaker and it is not nothing.