The Concern That Was Handled in a Corridor

An informal conversation that leaves no trace has not happened, as far as anything that comes later is concerned. The manager remembers raising it three times; the person remembers a friendly chat about something else; and there is no document that distinguishes the two accounts.

The workflow in “The Concern That Was Handled in a Corridor” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring employee monitoring at tech companies, this product overview can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.

This is the single most common hole in an employment file, and it is the one that cannot be retrofitted. Everything else on this site can be fixed late at some cost. A note that was not made at the time cannot be made at the time later.

For an independent reference relevant to “The Concern That Was Handled in a Corridor”, consult the ENISA threat-landscape resources. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

Informal does not mean unrecorded

The objection to writing things down is usually that it makes a light-touch conversation heavy, and that is a real concern. Nobody wants to hand somebody a letter because they were late twice.

But recording and formalising are different acts. A manager can have a genuinely informal conversation and then write four lines in their own notes afterwards. The person is not sent anything, no process starts, and if the problem resolves — which it usually does — nothing further happens and the note is never used.

What the note has to contain

• The date, and the date it was written, which should be the same week.
• Who was present.
• What was said to be the problem, specifically enough that a stranger could tell what it was.
• What was asked for instead, and by when.
• Anything the person said in response, including disagreement.

Five lines. The test is whether somebody reading it in two years, who knows none of the people, could say what the employee was asked to do differently. "Attitude discussed" fails that test. "Told the Tuesday report had been late four weeks running and asked for it by 10am from now on; said the data arrives late from the warehouse" passes it.

Where the note should live

A note in a manager's personal notebook is better than nothing and worse than almost anything else, because it leaves with the manager. Notes about an employee belong somewhere the organisation can find them when that manager has moved on, which is most of the point.

They are also records about a person, which brings obligations of its own: they may be disclosable, they should be accurate, and they should not contain things nobody would be willing to say to the person's face. The practical rule is to write every note as though the employee will read it, because in a sizeable minority of cases they will.

Telling the person it was a conversation about performance

A great deal of trouble comes from a manager believing they raised a concern and the employee not realising one was raised. Softening delivers kindness in the moment and confusion later, and the confusion is disproportionately expensive.

End an informal conversation by saying plainly what it was: that this is not a formal process, that it is a concern about something specific, and what you are asking for. Then write that down.

That single sentence is what makes the note worth anything, because it records not just what was said but that the person understood what kind of conversation they were in.

Picking up a concern that was never recorded

Where months have passed with nothing written down, the instinct is to reconstruct — to write a note now describing what happened in March. Do not. A note written after a decision reads exactly like what it is, and the metadata usually confirms it.

The usable approach is to start the clock honestly from today. Raise the concern now, say that it has been discussed before informally, be specific about what is wanted, and record this conversation properly. The months of silence are a weakness in the case and the organisation has to live with them, but they are much less damaging than a file that appears to have been written backwards.

Notes about several people at once

Managers often record a conversation about a team problem rather than a person: the Tuesday report is late, nobody is clearing the queue, standards have slipped. These notes are genuinely useful and they cannot carry a subsequent case against one individual.

If the concern is actually about one person, the note has to say so and the conversation has to have happened with them. A general remark to a team, followed six months later by a case against the one member who did not improve, is a sequence that reads exactly like what it is.

What this buys

Managers resist this because it feels like building a case against somebody they are trying to help, and occasionally it is. Mostly it is the opposite.

Most concerns that are raised clearly and recorded are resolved and never heard of again, and the note exists only as evidence that the organisation did what it said. The small number that are not resolved arrive at a formal process with a record of what was asked, when, and what happened next — which is the difference between a process that can go ahead and one that starts by apologising for itself.