The Broken Week

A process designed around a five-day week fails several times a year in ways that are known well in advance and planned for in almost none of them.

The record described in “The Broken Week” should be created close enough to the work that people are not reconstructing a polished week from memory. When teams assess see the complete product overview for employee monitoring software with screenshots, they should keep entry, project selection and correction simple, while explaining which optional activity data is collected and how employees can review it.

Public holidays, seasonal shutdowns, part-weeks at the start and end of a period, and the week where the payroll cutoff falls on a Tuesday all produce the same effects: confusion about what to submit, approvals rushed or skipped, and a period of data that is quietly wrong.

For a separate benchmark relevant to “The Broken Week”, consult the IRS recordkeeping guidance. 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.

Public holidays

The question is what the person records for a day they did not work and were paid for. The answers in use include nothing, the contracted hours against a holiday code, the contracted hours against their normal project code, and whatever they did last time.

All four appear in most datasets, often within one team. The consequence is that project cost figures include or exclude public holidays unpredictably, which makes period-on-period comparison meaningless in any month containing one.

Decide, write it down, and configure it so the person does not have to remember. A system that knows the calendar can pre-populate the day, and pre-population is the only approach that produces consistency.

Shutdowns and collective leave

A fortnight when most of the organisation is closed produces a period with half the usual hours and a timesheet process that still expects submissions.

The specific failure is the approver who is also away. A period that closes during a shutdown, with approvers absent and deputies not set, is the single most reliable generator of auto-approvals in the year. December data in most organisations is visibly different from every other month and the difference is not seasonal work patterns.

Part-weeks at period boundaries

Where the pay period is monthly and the timesheet week is Monday to Sunday, the two disagree every month. A week split across two periods has to be apportioned, and the apportionment rule is either in the system or in somebody's head.

Where it is in somebody's head, the same week gets split differently by different people, and the reconciliation between timesheet hours and payroll hours never quite closes. This is the source of a surprising proportion of the small unexplained variances finance teams carry.

Joiners and leavers

A person who starts on a Wednesday has a three-day first week, and a system expecting 37.5 hours will flag it as a variance every time. A person who leaves mid-period has a final week that must be approved after they no longer have an account, which in several systems means it cannot be submitted at all.

The leaver case is worth special attention because it is both the most common cause of a missing final payment and the moment when the organisation has the least ability to fix it afterwards. The final timesheet should be a step in the leaver process with a named owner, and in most organisations it is not in the checklist.

The predictable calendar

Every one of these is known a year in advance. The fix is a dated plan, prepared once, that says for each affected period what changes: the deadline, who covers approval, what pre-population applies, and which checks are suspended or added.

Preparing it takes an afternoon in January. The alternative is discovering each one in the week it happens, which is what currently happens and why the same conversation occurs every Easter.

Checking afterwards

For any period containing a break, run two numbers before closing it: the proportion of records auto-approved, and the hours recorded against holiday or absence codes compared with the calendar's expectation.

Both are quick, both catch the common failures, and both are far easier to resolve in the week than in the following March when somebody is reconciling the year.

Who is covering approval over the break

The question that is never asked in December and always asked in January. A period closing during a shutdown has submissions due from people who are away and approvals due from managers who are also away, and the auto-approval rule resolves both.

Name the cover before the break, in writing, with the dates. This is five minutes of work in November and it is the single intervention that removes the largest annual cluster of unreviewed approvals. Where no cover is genuinely available, move the deadline instead — a period that closes a week later is a smaller problem than a period nobody approved.