Skip to content
What You Have to Produce

Home / The requests

The Request Made During a Dispute

Most requests arrive from people in conflict with the employer. The motive is irrelevant to the obligation, and the temptation to treat it otherwise is the main risk.

The requests · Analysis

1 monthruns regardless of the disputeA grievance in progress does not pause it

HANDLING NOTE

Where a request arrives alongside a dispute

  • Separate owner
    Request handled by somebody not running the disputeThe single most useful arrangement
  • Clock
    Started on receipt, unaffected by the disputeDelay here is the finding, not the content
  • Scope
    What they asked for, not what you think they wantNarrowing by inference is how omissions happen
  • Legal advice
    Privileged material identified individuallyNot the whole file because a lawyer is involved
  • Disclosure in the dispute
    Separate process, separate rulesConfusing the two produces inconsistent positions
  • Tone
    Administrative, in writing, datedEvery message will be read back later
  • Response
    On time, complete, with the redaction logLateness is the thing most likely to be raised

A grievance is running, or a dismissal is being contested, and a request for data arrives. This is the normal case rather than the exception.

The response discipline in “The Request Made During a Dispute” also applies to records created by workforce software. A team using this workforce software resource in relation to how to handle multiple clients should know where data is stored, who can export it, how long it remains available and how a person can challenge a misleading record before a request arrives.

Why the motive does not matter

The right exists regardless of why it is exercised. Somebody gathering material for a claim is using it for exactly the purpose it was created for.

For a separate benchmark relevant to “The Request Made During a Dispute”, consult the TechTarget insider-threat reference. Use it to test purpose, data flow, retention, access and response procedures rather than substituting a generic checklist for the organisation’s actual records.

An employer that treats the request as hostile responds defensively, and every defensive choice — narrow scope, slow handling, broad redaction — is visible later as a pattern.

What actually goes wrong

Lateness. The dispute consumes attention, the request slips, and a month passes. Lateness is the easiest thing to establish and the first thing raised.

Conflation. The person handling the dispute also handles the request, and decisions about disclosure get made with one eye on the litigation. It produces inconsistent positions that are visible when both processes are examined together.

Over-claiming privilege. Everything touched by a lawyer is marked privileged. Legal advice is privileged; a document copied to a lawyer is not, and the over-claim damages the genuine claims.

The arrangement that works

Different people. The request is run by somebody not involved in the dispute, to a timetable, as an administrative matter.

It costs an hour of coordination and it removes almost every risk described above.

Disclosure in the dispute is a different process

A tribunal or court process has its own rules about what must be disclosed, and they are not these rules.

Material withheld from a data request may be disclosable in litigation. Material disclosed under a data request is not thereby admissible or privileged.

Treating the two as one conversation produces errors in both.

The posture to hold

Administrative, prompt, complete, documented. Nothing in the handling that would read badly if quoted.

An employer whose request handling is visibly correct removes an entire line of argument from the dispute, which is worth considerably more than whatever narrow advantage a defensive response might produce.

Separating the two processes

Disclosure in litigation has its own rules and they are not these. Material withheld from a data request may be disclosable in proceedings; material disclosed here is not thereby admissible. Treating them as one conversation produces errors in both.

The posture that removes an argument

Administrative, prompt, complete, documented. An employer whose request handling is visibly correct removes an entire line of attack from the underlying dispute, which is worth more than any narrow advantage.

Over-claiming privilege

Legal advice is privileged. A document copied to a lawyer is not, and the over-claim damages the genuine claims when the log is examined.

Different people, one hour

The request run by somebody not involved in the dispute, to a timetable, as an administrative matter. It costs an hour of coordination and removes almost every risk in this note.

Everything will be read back

Every message in a dispute is quoted later. The administrative posture is not caution for its own sake; it is recognising that the handling becomes evidence about the organisation.

Why defensive handling backfires

Narrow scope, slow handling and broad redaction each look reasonable alone and form a visible pattern together. That pattern becomes an exhibit in the dispute the defensiveness was meant to win.