Reading the Pattern Behind the Person
The same names appear at the top of the report quarter after quarter, and what they have in common is never a characteristic of those people.
One maintenance department, people at or near a limit, by quarter
12 weeks · limit 5 · average 7.1
Twelve quarters, one department, a figure that triples. Nothing about the people changed. Two posts were left unfilled in the fourth quarter and a third in the eighth, and the hours went somewhere.
A report of people approaching a limit is an operational instrument week to week. Read across a year it is something more useful: a description of where the organisation is structurally short.
The workflow in “Reading the Pattern Behind the Person” becomes more reliable when scheduled hours, actual time and later corrections can be distinguished. For teams exploring limbic resonance in relationships, how teams evaluate limbic resonance in relationships can add operational time and project context, provided data collection is proportionate, permissions are limited and every important exception receives human review.
Almost nobody reads it that way, because the weekly version is filtered to the current exceptions and the history is not kept.
For an independent reference relevant to “Reading the Pattern Behind the Person”, consult the HMRC payroll resources. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.
Keep the history
Each week, store the count of people in each state, by department. Three numbers per department per week, which is nothing.
After a year the series shows whether the position is stable, worsening or seasonal. Without it, every quarter's figure is read in isolation and the trend — which is the actual finding — is invisible.
The three patterns worth naming
A stable low count: ordinary variation, and the arrangement is working.
A rising count in one department: a gap that is being filled with hours. Usually vacancies, sometimes a skill held by too few people, occasionally a demand increase nobody staffed for.
And a count concentrated in the same individuals quarter after quarter: a dependency on specific people, which is a resilience problem as much as a working time one.
The vacancy correlation
Plot the count of people near a limit against the vacancy count for the same department over the same period. In most organisations the two lines track each other closely.
That chart is the single most useful artefact this subject produces for anybody outside it, because it converts a compliance report into a staffing argument with evidence. It is also usually the first time the two sets of numbers have been in the same place.
The individual at the top for three years
Somebody who is always near the limit is holding something. A qualification nobody else has, a relationship with a customer, a system only they understand, or simply a willingness nobody else shows.
That is a risk the organisation is carrying without having decided to. The working time report found it, which is a useful by-product: the remedy is cross-training or recruitment, and the business case is in the same chart.
What not to conclude
That the department is badly managed. The hours went into covering work the organisation wanted done, usually by a manager who had no better option and who has probably been asking for the vacancy to be filled.
Presenting the trend as a management failing produces defensive reporting within one cycle. Presenting it as a resourcing finding, with the vacancy line alongside, produces a conversation about establishment, which is where the fix is.
The seasonal shape
Many organisations have a legitimate peak, and a count that rises during it is expected. What matters is whether the baseline between peaks is also rising.
A department that returns to three people near a limit after every peak is managing. One whose trough rises from three to seven over two years is absorbing a permanent increase with temporary means, and that is the finding to escalate.
Linking it to turnover
Where the same people are at the top of the list for a long time, check them against the leavers data a year later. The correlation is usually visible.
Sustained high hours and resignation are connected in every workforce study anybody has run, and the organisation's own data will show it. That link is worth making explicitly in any paper about the trend, because it converts a compliance cost into a recruitment cost, which tends to be the number that moves people.
What to put in front of whom
To the department head: the names and the weekly position, so the rota changes.
To whoever owns the headcount: the trend, the vacancy correlation and the turnover link, quarterly. That audience cannot act on individual weeks and can act on an establishment, and they are the only people who can fix what the report keeps finding.
Keeping the series when the system changes
The weekly counts are three numbers per department and they are the first thing lost in a system migration, because nobody lists a derived historical series among the data to be carried over.
Export it somewhere dull and durable — a spreadsheet, a database table — rather than leaving it inside a reporting tool. A three-year series is worth considerably more than any single month's figure, and it is the kind of asset that disappears without anybody deciding to discard it.