What an Inspection Asks For

An inspection asks for the chain, and the gaps it finds are almost always retention decisions rather than accidents. Raw time data purged for space, configuration never versioned, an edit log with an empty reason field — each was a reasonable-looking choice made by somebody who did not know what the record was for.

The recordkeeping discipline in “What an Inspection Asks For” should also apply to workforce technology. When a team evaluates the product page in relation to task switching cost, it should document purpose, access, retention and deletion, then preserve the source entry, approvals and correction history needed to explain the final figure.

The request itself is usually narrow and predictable. What makes it difficult is that the organisation has never assembled the pieces together and does not know, until asked, which ones it no longer has.

For an independent reference relevant to “What an Inspection Asks For”, consult the FTC data-security guidance. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.

The usual request

• Payroll records for a period, for named employees or for a group.
• Time records for the same period.
• The statements issued.
• Written policies on hours, breaks, overtime and pay.
• An explanation of how a particular figure was arrived at.
• Records of any corrections made.

The fifth is the one that cannot be answered without the configuration and the rate build, and it is the one most likely to be asked.

Preparing without a fire drill

Run the request on yourself, once, as an exercise. Pick three employees and a period two years ago and assemble everything above.

The exercise takes a day and produces a precise list of what is missing. That list is far more useful than any general assurance, and it can be acted on calmly rather than under a deadline.

The gaps that recur

Raw time data purged. Configuration not versioned. Reason fields empty. Policies undated, so nobody can say which version applied. The rate build not stored. Records held in a system that has been replaced.

Every one of those is fixable going forward in a few hours of work and unfixable backwards, which is the recurring shape of everything in this collection.

Answering accurately

Where something cannot be produced, say so plainly and say why. An honest statement that detailed time data is retained for twelve months and that the period requested is outside it is a different thing from a vague response that invites a follow-up.

What is not advisable is reconstructing a record and presenting it as the original. A reconstruction clearly labelled as one, with its basis stated, is legitimate and useful; the same document presented as a contemporaneous record is not.

Who handles it

One named person, with authority to get data from payroll, the time system, IT and HR, and with somebody senior informed.

Inspections handled by whoever picked up the letter tend to produce partial answers in several instalments, which extends the process and creates an impression of disorganisation that may not be deserved.

What the absence of records implies

In many systems the practical consequence of missing records is that the employee's own account carries more weight, which is a strong reason to have them beyond any formal requirement.

That is worth saying internally when somebody proposes purging detailed data for storage reasons. The cost of keeping it is measurable and small; the cost of not having it is contingent and large.

The interview alongside the documents

Inspections usually involve talking to people as well as reading records, and the accounts of managers and employees are weighed against the paperwork.

That is worth knowing before it happens, for an unglamorous reason: managers who have never been told how the premium is calculated will say so, and an organisation whose own supervisors cannot describe its pay rules looks different from one whose can. A single-page briefing for managers — what the week is, what the threshold is, what goes in the rate — costs an afternoon and is useful whether or not anybody ever asks.

The period they choose

Inspections rarely look at everything. They pick a period and a group, often on the basis of something specific: a complaint, a sector focus, a pattern in a return.

Knowing which period has been chosen shapes everything about the response, and it is always stated in the request. Reading the request carefully before starting to assemble documents saves days of producing material nobody asked for, which is the most common way an organisation makes an inspection longer than it needed to be.

After it is over

Record what was asked, what was produced, what was not, and what was changed as a result. Two pages.

An inspection is an unusually clear description of what an outsider expects an employer to be able to show, and most organisations learn more from it than from any internal review. Writing that down is what turns an uncomfortable fortnight into something the organisation keeps.