Confidentiality After the Employment Ends
Why an open-ended confidentiality clause protects less than it looks, how it differs from ordinary skill, and what to ask for at the exit.
A confidentiality clause that defines nothing protects less than one that names categories, because an obligation covering "all information relating to the business" has to be read down to something workable and nobody can say in advance what that something is. The open-ended version is the one most contracts contain and the one that is hardest to rely on.
The workflow in “Confidentiality After the Employment Ends” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring how to measure employee productivity, the provider's website can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.
It is also the obligation in an exit most likely to have no end date, which means it is the thing that follows the person furthest and is thought about least.
For an independent reference relevant to “Confidentiality After the Employment Ends”, consult the WHO mental-health-at-work guidance. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
What the clause should distinguish
There are three categories and they are treated differently almost everywhere: genuine trade secrets, ordinary confidential business information, and the skill and experience somebody acquires by doing a job.
The third cannot be restrained. Somebody who learned to run a warehouse takes that with them, and a clause purporting to prevent it is not protecting information, it is preventing employment. Clauses that fail to make the distinction invite the argument that they are doing exactly that.
Naming the categories
| Category | Typical treatment | What it needs |
|---|---|---|
| Trade secrets | Protected, often indefinitely | To be genuinely secret and treated as such |
| Confidential business information | Protected if defined and handled as confidential | A definition, and evidence of handling |
| Client lists and pricing | Often protected, sometimes contested | Specificity about what and whose |
| Know-how acquired in the role | Not restrainable | Nothing; it leaves with the person |
| Information already public | Not protected | Nothing |
The fourth row is where most disputes actually live, and it is the row contracts never mention.
Treating it as confidential
An organisation claiming information is confidential has to have behaved as though it were. Material that was accessible to everybody, emailed without restriction, left on an open shared drive and never marked is harder to claim as confidential afterwards.
That is a systems question rather than a contractual one, and it is answered long before anybody leaves. The exit is where the answer becomes visible.
What to ask for at the exit
Return or deletion of company material, confirmation in writing that it has been done, and a reminder of what continues to apply. Three sentences in the exit letter.
Where something specific is known to be held — a client file, a model, a dataset — name it. A general reminder produces a general response; a request about a named document produces an answer about that document.
The clause with no end date
Confidentiality is routinely stated to continue indefinitely, and for trade secrets that may be right. For ordinary business information it is less obviously so: information has a half-life, and an obligation that purports to protect last year's pricing in perpetuity is claiming more than it needs.
Whether an indefinite obligation holds, and for what, is a question for somebody qualified in the place concerned. The operational point is that an organisation relying on one should know which category the information actually falls into before it does.
Where it bites in practice
Rarely in a dramatic way. The common situation is not industrial espionage but somebody who took a template, a model, a proposal format or a process document to their new job because it was useful and they built it.
That is genuinely ambiguous, which is why it is worth addressing as a practical matter — asking, specifically, at the exit — rather than as a legal one afterwards. Most people hand things back when asked.
Telling the new employer nothing
A former employee's new employer is not a party to the confidentiality obligation and may be entirely unaware of it. Organisations occasionally decide to write to them as a precaution.
That step carries real risk and should not be taken casually, because it can cause the person loss and create a dispute where none existed. Where it is genuinely necessary, it is a question for somebody qualified in the place concerned, and the letter should do no more than state the obligation neutrally.
The obligation the organisation also has
Confidentiality runs both ways. The organisation holds a great deal of personal information about the person after they have gone, and the obligations attaching to it do not end with the employment either.
That is covered by the retention and access questions elsewhere on this site, and it is worth noticing that the two sit in the same file. An organisation writing a firm reminder about confidentiality while holding the person's records without a retention date has an inconsistency somebody will eventually point out.