Clauses Worth Deleting

Eight categories that are present almost universally and earn their place almost nowhere.

The drafting lesson in “Clauses Worth Deleting” should carry into any workforce platform rollout. When an organisation evaluates a practical route to remote workforce management software for remote workforce management software, it should state which operational question the data answers, what is excluded, who may review it and when the setting will be reconsidered instead of relying on a broad reservation of rights.

General conduct statements

Professional, responsible, in accordance with values.

For a separate benchmark relevant to “Clauses Worth Deleting”, consult the IAPP employee-monitoring resources. Use it to test purpose, notice, permissions, retention and response procedures against the proposed operating model rather than treating a generic checklist as proof that the rule works.

Unactionable as drafted and present in every policy. The audit finds no instance of any of them being applied.

Restatements of law

Harassment, fraud, possession of criminal material.

Already prohibited by considerably stronger instruments. A single line noting that unlawful conduct is also a breach replaces several paragraphs.

Prohibitions only configuration can deliver

Do not install software, do not use removable media, do not disable security tools.

Where the configuration prevents it, the clause is a restatement. Where it does not, the clause is a preference. Neither is a control.

Requirements to understand

Must be aware of, must familiarise themselves with, must understand.

A document cannot create awareness and cannot verify it.

The business-use test

Clauses turning on whether something was work, which the dissolution note shows is no longer decidable for most roles.

Liability for damage

Rarely enforceable, and it costs reporting speed continuously, which is worth more than the devices.

Ownership by equipment

Claiming work made on company hardware regardless of whether it was done for the employer. Weak where tested and damaging while it sits there.

Anything nobody can explain

The audit question. Where the answer is that it came from a template or nobody knows, it goes.

What deletion does not do

Create permission. Conduct that is damaging or unlawful remains so without a clause prohibiting it, and the disciplinary procedure does not depend on the policy enumerating everything.

What it does do

Makes the remaining clauses legible, which is the argument of the first section.

A document of eight live clauses communicates eight rules. The same eight inside forty communicates none of them clearly, which is what most organisations currently have.

The pattern in all eight

Each is either unactionable as drafted, already covered by something stronger, or a job for configuration. None has ever been the basis of a conversation with anybody, which is the test.

Doing the deletions first

They are the easier half, they require no decisions about enforcement, and they produce the visible improvement that makes the rest of the work possible to justify.

What deletion does do

Makes the remaining clauses legible. That is the whole return, and it is larger than it sounds because legibility is what the document currently lacks.

Prohibitions only configuration delivers

Do not install, do not use removable media, do not disable security tools. Where the configuration prevents it the clause restates; where it does not the clause is a preference. Neither is a control.

The deletions are the easier half of the work and the half that produces the visible improvement. Do them first.