The Employee's Own Account
Why the person's account is evidence rather than a response, how to take it so it is worth something, and what an account that changes actually indicates.
The employee's account is evidence, and it is usually the cheapest available. Somebody who was there knows what happened, and asking them early — before a case has been assembled around a theory — produces information that no system holds and that frequently closes the matter.
The identity gap described in “The Employee's Own Account” matters when teams assess view the complete capability outline for limbic resonance in relationships. The platform may make an activity or timestamp visible, yet a responsible review still distinguishes the device or account from the person, checks another source and records what the evidence does not establish.
Most investigations take the account last, as a response to a finished case. By then it is a defence rather than an account, and the detail that would have explained everything has been displaced by the need to answer.
The New Zealand Privacy Commissioner resources offers another lens on the issue raised in “The Employee's Own Account”. Compare its principles with the actual record, ownership model and review route rather than importing a generic checklist unchanged.
Asking early
The first conversation should be a question, not an allegation: we are looking at the records for these dates and there are some things we do not understand — can you help us.
That produces explanations. The alternative produces denials, and denials contain almost no information.
What to ask for
- What they remember about the specific days, before being told what the issue is.
- What normally happens at the times in question.
- Whether anything was different in that period.
- Whether anybody told them to do anything differently.
- Whether they had any difficulty with the systems.
- Who else was there.
The fourth and fifth are the ones that surface the supervisor's instruction and the failing reader, which between them explain a large share of these matters.
Separating memory from routine
The same discipline as for any recollection: ask whether they actually remember the day or are describing what usually happens.
Most people answer honestly and it is usually the second. Recording that distinction protects the person from being treated as evasive for giving a general answer to a question about a particular Tuesday.
An account that changes
Treated as proof of dishonesty, and it is weaker evidence than that. A first account given without notice, under pressure, about something weeks ago, is frequently wrong in detail and corrected afterwards.
What matters is the shape of the change. Correcting a time, remembering a meeting, discovering a note — those are ordinary. An account that changes to meet each new piece of evidence as it is disclosed is a different pattern, and it is worth describing that way rather than asserting dishonesty.
Giving them what they need to answer
Somebody cannot account for a Tuesday six weeks ago without their own records: their calendar, their messages, their tickets, their rota.
Suspending access and then asking for an explanation is a combination that does not survive being described out loud. Where access has been restricted, arrange a supervised route to the material they need.
Putting the records to them properly
In advance, in full, with enough time to look at them. Showing somebody a log in a meeting and asking for an immediate explanation tests their composure rather than their account.
The same applies to anything produced later: new material means another chance to respond, not a conclusion.
Recording it fairly
Take a note, send it, invite corrections, record disagreements rather than arguing about them. The same as any meeting note.
For this kind of matter the note is particularly important because the account will be compared with later accounts, and a disputed note makes that comparison worthless.
Who takes it
Not the person who built the case, where that can be avoided. An account taken by the investigator is taken by somebody with a hypothesis, and the questions follow the hypothesis.
Where separation is impossible — which is most small organisations — the mitigation is a written question list agreed in advance, so that the questions were decided before the answers started arriving.
Accompaniment
Somebody who may bring a colleague or representative gives a fuller account, not a narrower one, because they are less frightened.
That is the practical argument alongside the procedural one. An investigation meeting where the person is alone and anxious produces short answers and missed explanations, and the explanation is what everybody actually needs.
When they say nothing
Silence is not an admission and should not be recorded as one. People decline to answer because they are advised to, because they do not understand the question, or because they are frightened.
Record that no account was given, offer another opportunity in writing, and proceed on the evidence. What should not appear in the file is an inference drawn from the silence itself.
What a good account does to the case
Usually ends it. The large majority of time anomalies have an explanation the person can give in a sentence, and the investigations that run for weeks are frequently investigations where nobody asked.
That is the practical argument for taking the account first: it is the fastest route to the answer, and the answer is nearly always ordinary.