What It Is For, Stated Plainly
Three real functions, none of which is prevention. Being clear about which you are serving changes what gets drafted.
Scope
Enforced
As written
This policy applies to all employees, contractors, temporary staff and third parties who access company systems or equipment.
What happens
Enforced in the sense that nobody disputes it. Rarely communicated to the contractors and temporary staff it names.
Agency workers and contractors frequently never see the document, which makes the scope clause accurate and the coverage notional.
Worth checking who actually received it against who it claims to bind.
Policies are drafted without anybody stating what the document is supposed to achieve. Three functions are real and they pull in different directions.
The practical point in “What It Is For, Stated Plainly” is that a written rule becomes credible only through a consistent operating process. For teams exploring step rate compensation, view the solution can add time and project context, provided collection is proportionate, access is limited and every significant inference receives human review.
One: evidence that something was communicated
The function that works reliably.
For a separate benchmark relevant to “What It Is For, Stated Plainly”, consult the AWS incident-response guide. 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.
If conduct becomes a disciplinary matter, the organisation needs to show the expectation was communicated. A signed acknowledgement does that, whether or not anybody read it.
This is genuinely valuable and it is the function the acknowledgement clause serves. It requires the document to exist and to have been issued, and almost nothing else.
Two: a reference point for a manager
Second in value and usually overlooked.
A manager raising something with somebody is in a stronger position pointing at an existing expectation than inventing one in the conversation. The clause does not have the conversation, and it removes the need to justify the standard from scratch.
For this function the document needs to be findable, short enough to quote, and composed of things the manager would actually say.
Three: setting a baseline so the serious cases are clearly serious
The function that justifies keeping some specificity.
Where the policy states that customer data must not leave company systems, an incident involving customer data is unambiguous. Without it, the organisation is arguing about whether the person should have known.
What is not a function
Prevention, which belongs to configuration and has its own note.
Instruction, which belongs to induction and conversation.
Comprehensiveness. A document listing every conceivable misuse is not more protective; it is less readable and more dilute.
What follows for drafting
Decide which function each clause serves.
Evidence clauses can be broad and formal. Reference-point clauses should be short and phrased as something a manager would say aloud. Baseline clauses need to be specific about what matters most.
A document written with those three in mind reads differently from one written to cover everything, and it is shorter.
Checking who actually received it
The scope clause names contractors, temporary staff and third parties. Comparing that list against who was actually sent the document usually finds that the named groups were not, which makes the scope accurate and the coverage notional.
Three functions, three registers
Evidence clauses can be formal. Reference-point clauses should sound like something a manager would say. Baseline clauses need specificity about what matters most. A document written in one register is serving at most one of them.
The question for any proposed clause
Which of the three functions is this for? Where the answer is none, the clause is being added because something happened once and nobody has asked what it achieves.
Scope against coverage
The clause names contractors and agency staff. Checking who was actually sent the document usually finds they were not, which makes the scope accurate and the binding notional.
Deciding the function before drafting the words
Evidence, reference point, or baseline. Each produces different language, and a clause written without choosing reads as all three and serves none.
Writing to the function
A clause serving the evidence function can be formal, because its reader is a tribunal. One serving the reference-point function should be short and speakable, because its reader is a manager mid-conversation. One serving the baseline function needs to be specific about the thing that matters most.
Most documents are written in a single register, usually the first, which means two of the three functions are served badly by every clause. Deciding the function before the wording is the step that produces a document doing more than one job.
The question to put to any proposed clause: which of the three is this for? Where the answer is none, the clause is being added because something happened once.