Consistency, and the Record That Proves It
The ground on which outcomes are most often overturned, and the record that answers it is one somebody has to decide to keep.
Consistent application
Unenforceable
As written
This policy will be applied consistently and fairly to all employees.
What happens
An assertion rather than a mechanism. Nothing in the organisation records previous outcomes, so consistency cannot be checked by anybody including the organisation.
Where it is challenged, the answer is a belief rather than a comparison.
The clause describes an intention that no process supports.
If somebody is dismissed for conduct another person was warned for, the difference has to rest on the facts. Establishing that requires knowing what previous cases concluded.
The response process in “Consistency, and the Record That Proves It” needs evidence that can be checked without turning one signal into a conclusion. If the provider website supports getting teams to meet deadlines, managers should validate the record with the person involved, preserve the correction history and distinguish an operational exception from deliberate misconduct before any consequential action.
Why organisations cannot answer
Informal outcomes are not recorded, which is usually correct for the individual case and leaves no comparison.
For a separate benchmark relevant to “Consistency, and the Record That Proves It”, consult the KrebsOnSecurity analysis. 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.
Formal outcomes sit in personnel files that nobody searches by conduct type.
And the people who handled previous cases have moved on.
Which means the organisation is arguing consistency from memory against somebody who has specific examples.
The record that solves it
Not a file on individuals. A log of outcomes by conduct type.
Date, what the conduct was, the grading, what was decided. No names.
Twenty rows after a few years, and it answers the question in a minute rather than a week.
Who keeps it
The policy owner, which the ownership note argues should be a named person.
It is a few lines per matter, added when something concludes, and it is the only artefact in this subject that accumulates value rather than ageing.
What it is actually for
Answering the inconsistency argument, which is the obvious use.
Guiding the next decision, which is the more common one. A manager deciding what to do can see what happened last time, which produces consistency without anybody having to enforce it.
And showing drift. Where outcomes for the same conduct have become harsher or softer over time, the log shows it and nothing else does.
The anonymity question
Without names it is a reference document. With names it is a shadow personnel record, discoverable, and it will be requested.
Keep it without names. Where a specific comparison is needed in a live case, the individual files can be found from the dates.
The first entry
Start it now, with whatever anybody remembers from the last two years.
Incomplete and roughly dated is considerably better than nothing, and the entries from here on will be accurate.
Why memory is not enough
The organisation is arguing consistency from recollection against somebody with specific examples. The log turns a week of asking around into a one-minute answer.
Without names
A log with names is a shadow personnel record, discoverable and certain to be requested. Conduct type, grading, outcome and date is sufficient, and individual files can be found from the dates where a live comparison is needed.
What the log is actually for
Answering the inconsistency argument, which is the obvious use. Guiding the next decision, which is the common one. And showing drift, which nothing else reveals.
Keeping it without names
Conduct type, grading, outcome, date. With names it becomes a shadow personnel record that is discoverable and will be requested. Individual files can be found from the dates when a live comparison is needed.
Twenty rows after a few years
That is the whole artefact, and it is the only thing in this subject that accumulates value rather than ageing. Starting it costs nothing and is almost never done.
Starting the log today
With whatever anybody remembers from the last two years, roughly dated and incomplete. It is worth more than nothing immediately and everything added from now on is accurate.
The reason to start now rather than at the next review is that the next matter will need it. Consistency is argued from a comparison, and the comparison either exists or the organisation is arguing from recollection against somebody holding specifics.
An organisation that cannot produce its own comparison history will lose the consistency argument regardless of whether it was consistent.