Clauses Worth Having

Eight clauses that survive the tests in the drafting note. Each is specific, each describes something somebody would actually act on, and each is phrased as a person would say it.

The drafting lesson in “Clauses Worth Having” should carry into any workforce platform rollout. When an organisation evaluates this practical implementation page for gdpr employee monitoring, 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.

Customer and personal data

Do not move it outside company systems. If the usual route will not work, ask first.

For a separate benchmark relevant to “Clauses Worth Having”, consult the ICO employment-practices guidance. 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.

The most important clause in any policy and the one most worth keeping short and unqualified.

Lost or stolen equipment

Tell us immediately. You will not be charged.

Two sentences, and the second is what makes the first happen.

Credentials

Do not share your login. If somebody needs access you have, tell us and we will arrange it.

Again the second sentence: the sharing happens because the access arrangement does not exist, and prohibiting without providing guarantees the breach.

Installing things

Install anything from the catalogue. For anything else, ask, and we will answer within two days.

The stated response time is the enforceable part. Without it the clause produces workarounds.

Leaving

Return the equipment, including the things at home. Tell us about anything registered in your name.

The second half is the part nobody writes and the part that matters.

Personal use

It is fine. We do not monitor it. Two things are not fine: anything that risks company data, and anything that would cause a problem if it became public.

The honest version from its own note.

Travelling internationally

Tell us beforehand. Usually nothing changes and occasionally it does.

Short, and it opens the conversation that otherwise never happens.

Something going wrong

Here is the name. Tell them the same day. Reporting a mistake is not what gets anybody into trouble.

The clause with the highest return of anything in this list, and the one most often missing entirely.

What they have in common

Each names a behaviour rather than a principle. Each supplies the alternative route as well as the prohibition. Each is something a manager could say aloud without sounding institutional.

And each has, in most organisations, actually been applied to somebody — which is the only test that matters.

The second sentence

Each of these supplies the route as well as the prohibition. Do not share your login produces the breach; do not share it, and tell us if somebody needs your access, removes the reason for it.

Why eight

Because that is roughly what people retain. A list of fifteen communicates fewer rules than a list of eight, which is the length argument applied to the clauses that survive.

Eight clauses, and why that number

Roughly what people retain. A list of fifteen communicates fewer rules than a list of eight, which is the length argument applied to the clauses that survived the audit.

Why each one works

It has actually been applied to somebody. That is the only test in this collection that cannot be argued with, and it is the test every clause here passes.

Eight, and why not fifteen

Because eight is roughly what people retain. A list of fifteen communicates fewer rules than a list of eight, which is the length argument applied to the clauses that survived.

Each of these has been applied to somebody in most organisations, each supplies the route as well as the prohibition, and each could be said aloud by a manager without sounding institutional. Those three properties are what separates a rule from a sentence.