The Same Eleven People

Every organisation has them. The list is stable across periods, everybody knows the names, and the standard interventions — reminders, escalation, a mention in a one-to-one — have been applied for years without effect.

The practical lesson in “The Same Eleven People” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring limbic resonance in relationships, how teams evaluate limbic resonance in relationships can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

Stability across nine periods is the finding. A behaviour that does not respond to nine rounds of the same stimulus is not being sustained by carelessness, and the useful question is what is sustaining it.

For a separate benchmark relevant to “The Same Eleven People”, consult the HMRC payroll resources. 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.

The causes, from the ones you can see in the data

People with no usable access at the time they would submit: field workers, drivers, site staff, anybody whose Friday afternoon is not spent at a desk. Visible in the data as submissions always arriving from a different location or always on Monday morning.

People whose work does not fit the categories. Visible as a very small number of distinct codes, heavy use of a catch-all, or a long history of queries about which code to use.

People with multiple reporting lines or multiple engagements, who have more than one timesheet and keep missing one of them. Visible as late submission concentrated in one of their two records.

Contractors and temporary staff who were never properly onboarded into the system. Visible as an account created late, no training record, and a long tail of basic errors.

The causes you can only find by asking

Seniority, which is the most common single cause above a certain level. A director whose timesheet is three weeks late will not be escalated to by a payroll administrator, and after two periods of that everyone has quietly agreed the requirement does not apply.

The belief that it does not matter, which is sometimes correct. If the person's hours feed nothing but an internal report nobody reads, they have accurately assessed the situation, and the honest response is either to explain what it does feed or to stop asking.

A manager who submits on their behalf. This removes all consequence and is rarely visible unless the system records who created the entry.

And occasionally something personal — a literacy issue, a disability, a system that does not work with their assistive technology — which will never surface in response to a reminder and will surface in a five-minute conversation.

The conversation

Short, private, curious rather than corrective, and conducted by their manager rather than by the person who sends the reminders.

The question is not why they are late. It is what happens on the day they would submit, walked through concretely. Nearly every structural cause falls out of that description without anybody having to name it as an excuse.

Fixing the eleven individually

The point of the diagnosis is that the fixes are individual and small. Mobile access for the three who are never at a desk. A code that fits for the one whose work has no home. A single consolidated timesheet for the person with two. Proper onboarding for the contractor. An explicit decision, from someone senior enough, about whether the director's timesheet is actually required.

Each takes under an hour. Together they usually remove most of a list that has resisted two years of reminders, and they remove it permanently rather than for one period.

What not to do

Do not run a general campaign. The eleven are eleven; a message to four hundred people costs four hundred people's attention to address eleven problems that are each different.

Do not tie it to pay unless the person is hourly and the timesheet genuinely determines what they are owed. Withholding salary over a late form is disproportionate, usually unlawful, and converts an administrative irritation into a formal dispute.

And do not leave the senior case unaddressed while enforcing against everybody else. It is noticed, it is discussed, and it does more damage to the credibility of the whole process than the missing timesheets do.

The joiner and the leaver on the list

Two recurring categories that look like late submission and are not. A new starter who has not been set up in the system cannot submit, and will appear on the chase list every period until somebody notices the account does not exist. A leaver's final week is often unsubmittable because the account was disabled on their last day.

Both belong on the joiner and leaver checklists with a named owner, and in most organisations neither is. The leaver case is the more urgent of the two, because it is the most common cause of a missing final payment and the organisation's ability to fix it falls sharply once the person has gone.