The Claim That Arrives Two Years Later

The reason employers give for keeping everything is the claim that might arrive later. It is a real risk, and it justifies a defined period rather than an unlimited one.

The practical lesson in “The Claim That Arrives Two Years Later” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching remote employee monitoring software, the provider website can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

What the risk actually is

Employment claim windows are finite. They vary, and in most places they are measured in months rather than years for the common claims, with longer periods for some categories.

For a separate benchmark relevant to “The Claim That Arrives Two Years Later”, consult the SANS insider-threat resources. Use it to test purpose, data flow, retention, access and response procedures rather than substituting a generic checklist for the organisation’s actual records.

Retention for defence should match the longest realistic window plus a margin, which produces a period of a few years rather than an indefinite holding.

The hold, which is different

Once a claim is received or reasonably anticipated, relevant material must not be deleted.

This is a separate arrangement from the retention schedule. The schedule says delete on a date; the hold says not this material, not yet.

Most organisations have the schedule and no concept of a hold, which produces the serious version of the problem: an automatic purge running during a live dispute.

Reasonably anticipated

Earlier than the claim form arriving.

A grievance that is plainly heading somewhere, a resignation letter alleging constructive dismissal, a solicitor's letter — each is enough to trigger a hold, and waiting for formal proceedings is too late.

Telling people not to delete

Including managers with their own folders, which the manager-notes problem makes relevant here.

An instruction that names the material, says not to delete it, and says who to ask if unsure. Verbal instructions are not evidence that it was given.

Deletion during a dispute

If material relevant to a live claim is destroyed, the organisation is in a materially worse position than if it had produced something unhelpful.

Adverse inferences, cost consequences and a credibility problem that attaches to everything else it says. The unhelpful document would almost always have been less damaging.

Releasing the hold

When the matter concludes, the hold comes off and the schedule resumes.

Almost nobody does this, which means holds accumulate and the organisation retains indefinitely the material from every dispute it has ever had — arriving back at the indefinite retention the schedule was meant to prevent, by a different route.

Reasonably anticipated, not received

A grievance plainly heading somewhere, a resignation alleging constructive dismissal, a solicitor's letter. Each triggers a hold, and waiting for proceedings is too late.

Releasing it afterwards

Almost nobody does, which means holds accumulate and the organisation retains the material from every dispute it has ever had — arriving back at indefinite retention by a different route.

Destroying during a dispute

Worse than producing something unhelpful. Adverse inferences, cost consequences, and a credibility problem attaching to everything else the organisation says.

Including managers with their own folders. An instruction naming the material, saying not to delete, and saying who to ask. Verbal instructions are not evidence that it was given.

The hold that outlives the matter

Released when the dispute concludes, and almost never released. Which means holds accumulate and the organisation retains the material from every dispute it has ever had.