How a single word – “variance” – travelled through an investigation and came out the other side as “discrepancy,” and why that matters for anyone who commissions, conducts, or is subject to a workplace investigation.
Key points
- An investigation can inherit an assumption through its commissioning, its terms of reference, or the framing of its questions… then interpret evidence in relation to that assumption.
- A careful investigation report can still be overtaken by an outcome that does not reflect what the investigation actually established.
- “Could have acted more carefully” is not the same as “breached a requirement.” A failure to follow up is not proof of knowledge.
- A decision-maker who reaches a different conclusion from the investigator must explain the evidential basis for doing so. Disagreement is permissible; an unexplained disagreement is much harder to defend.
- A fair process is not defined by whether it reaches a particular conclusion, but by whether the organization can explain how it got there.
The monthly report
The monthly performance report had already been published when the problem came to light.
A data-mapping issue had caused certain pending transactions to be recorded incorrectly, affecting the report’s figures. The report had been circulated on Monday and had already influenced a resource-allocation decision. The error was material: it had changed what the organization did.
On Wednesday, an analyst in the reporting team noticed something unusual.
She emailed Marcus, the team’s manager.
I’ve noticed an unusual variance in the pending transactions. I’m checking whether this is a mapping issue. Will update.
Marcus replied:
Thanks. Please check and let me know.
The analyst opened a support ticket and continued investigating. The following Monday, the error was formally identified.
By then, the department head had begun asking questions about Marcus’s handling of the matter.
In the department head’s account, Marcus had been told there was a problem and had not escalated it. He was responsible for the reporting team, and the report containing the affected figures had already been published.
It was reasonable to ask whether a manager in Marcus’s position should have considered the possible implications of the variance.
But the management referral went further. It said: Marcus was aware of a reporting discrepancy and failed to escalate it appropriately.
That description became the starting point for an investigation.
The question that had already been answered
Elaine was appointed to investigate.
The initial terms of reference asked her to establish why Marcus had failed to escalate a material reporting discrepancy despite being aware of it.
The wording contained an assumption: Marcus had known about a material discrepancy and had failed to escalate it. The investigation was being asked to establish why.
An investigation can inherit an assumption without anyone explicitly instructing it to adopt one. It can enter through the commissioning conversation, the wording of the referral, or the way questions are framed. Once it has entered the process, subsequent evidence may be interpreted in relation to it.
Elaine began with the analyst.
The analyst explained that she had noticed an unusual variance and suspected a possible mapping issue. She had opened a support ticket because that was the normal route for investigating technical anomalies.
She did not know at the time that the published report contained incorrect figures. Nor could she recall telling Marcus that the variance might affect a report that had already been circulated.
Elaine returned to the email.
It did not say that the published report was wrong. It did not identify a material reporting discrepancy. It described an unusual variance that the analyst was checking.
There was a difference between what Marcus had been told and what the organization now believed he should have understood.
That did not settle the matter. It did give Elaine a reason to examine the assumptions behind the allegation.
The reporting procedure required material discrepancies affecting published management information to be escalated. Technical anomalies were initially handled through the operational support process.
But the procedure did not clearly explain when an unusual technical variance became a material reporting discrepancy. Nor did it specify precisely what a manager was expected to do while that distinction remained unresolved.
Elaine spoke to the procedure owner.
He explained that issues affecting published figures should be raised with management. If something appeared to be a system anomaly, the operational support process should be started. Managers were expected to use their judgement and seek advice where necessary.
Elaine then put the question about the connection between Wednesday’s variance and Monday’s report to the department head. He said Marcus should have made that connection.
The report contained pending transactions. The variance concerned pending transactions. Marcus had access to the report.
The connection was plausible.
But the analyst’s email did not identify the report, the reporting period, or any known impact on published figures. There was no explicit instruction requiring managers to revisit published reports whenever a technical anomaly was identified.
The organization now knew that the variance had contributed to an error in a published report. Marcus had not known that when he opened the analyst’s email.
That distinction mattered.
Marcus confirmed that he had received the email, understood that the analyst was investigating a variance, and had not followed up independently.
He had assumed she was handling the matter through the support process. He had not understood that the published report might be affected.
“I suppose I assumed that if it turned out to be something serious, she’d come back to me.”
It was not an especially strong account of managerial vigilance. Marcus could have checked whether the issue had been resolved. He could have asked for an update.
But the investigation was not simply about whether a different course of action might have been preferable. It was about what Marcus had known, what he could reasonably have understood, and whether his actions amounted to the conduct described in the allegation.
What the evidence could (and could not) establish
Elaine examined three earlier cases involving technical anomalies. They did not reveal a consistent practice.
| Case | Manager was told | Route taken | Outcome |
| 1 | An unusual variance | Operational support | Reporting impact became apparent only after technical investigation |
| 2 | An unusual variance; not told published figures were affected | Operational support | Handled as a technical issue |
| 3 | Reporting impact already established | Escalated immediately | Escalated |
The first two resembled Marcus’s situation. They did not establish that he had been given the same information, or that managers were expected to act the same way in every case.
Elaine began to separate two questions that had been bundled together. She revised the terms of reference, and Marcus was given an opportunity to respond to the revised scope.
TERMS OF REFERENCE: VERSION 2
Matters to be examined:
- Whether Marcus knew, or had sufficient information to understand, that the published management report might contain a material discrepancy, and whether he failed to escalate it as required.
- Whether Marcus, having been informed of an unusual variance in pending transactions, failed to take reasonable steps to establish whether the issue had been resolved.
The support-ticket records showed that the analyst had opened a ticket. Marcus was not copied into it, and the system did not notify him automatically. Elaine returned to the procedure owner.
INTERVIEW NOTE: PROCEDURE OWNER (EXTRACT)
Is there an expectation that managers monitor unresolved issues?
Where they could affect reporting, yes.How was that expectation communicated?
It’s a general expectation. I can’t point to a specific instruction.
There was a general expectation of oversight. There was less clarity about what it meant in practice.
Marcus accepted that he had not checked the ticket. He had believed the analyst was managing it, and had not understood that he was independently expected to monitor it.
The fact that he had not checked was established. Whether that omission breached an explicit and consistently understood expectation was another matter. There was a managerial shortcoming. That did not automatically establish either allegation.
What the investigation actually found
Elaine’s report was careful about what it claimed.
INVESTIGATION REPORT: EXTRACT
Finding 1: Knowledge of a reporting discrepancy
The investigation considered whether Marcus knew, or had sufficient information to understand, that the published management report might contain a material discrepancy.
Marcus received the analyst’s email on Wednesday. It referred to an unusual variance in pending transactions and said she was checking whether it was a mapping issue. It did not refer to the published report, the reporting period, or any impact on management information. The analyst did not recall telling Marcus that published figures might be affected, and did not herself know this at the time.
The reporting procedure does not require managers to revisit published reports whenever a technical anomaly is identified.
The investigation did not establish that Marcus knew, or had sufficient information to understand, that the published report might be affected. The allegation that he knowingly failed to escalate a material reporting discrepancy is not substantiated.
Finding 2: Follow-up
Marcus did not check the status of the support ticket after being informed of the variance. He accepted that he could have followed up, but understood the analyst to be managing the issue through the support process.
The procedure does not require managers to monitor every ticket raised by their teams. The procedure owner stated that managers were generally expected to monitor unresolved issues that could affect reporting, but could not identify a specific instruction or established process describing how.
The investigation considers that Marcus could have taken more active steps to establish whether the variance had been resolved. However, it did not establish a sufficiently clear and consistently applied expectation that he was required to do so in these circumstances. The separate concern regarding his failure to follow up is therefore not substantiated.
Observation and recommendation
These findings should not be read as an assessment that Marcus’s handling of the matter was without shortcoming. They reflect what the evidence was able to establish.
The investigation recommends that the organization clarify managerial responsibilities for monitoring unresolved technical issues that may affect reporting, and for assessing whether such issues could affect published management information.
The department head’s response
The department head was invited to submit a management response.
He did not agree with the report’s assessment.
Marcus had been aware of the variance in pending transactions, he argued, and the report containing those figures had already been published. The department considered that the investigation had not given sufficient weight to Marcus’s responsibilities as manager of the reporting team.
That disagreement was not inherently improper.
The department head could reasonably believe that Marcus should have recognized the potential connection and taken more active steps. He was entitled to explain that view.
But a managerial concern and an established allegation were not the same thing.
When the conclusion changes
The final decision-maker considered Elaine’s report and the department’s response.
Before reaching a final decision, the decision-maker sent Marcus a proposed outcome.
PROPOSED OUTCOME: EXTRACT
Having considered the investigation report and the department’s response, I am minded to conclude that Marcus failed to escalate a reporting discrepancy of which he was aware.
Before reaching a final decision, Marcus is invited to comment on this proposed conclusion.
Marcus replied.
RESPONSE TO PROPOSED OUTCOME: EXTRACT
I do not dispute that I was aware of the variance the analyst reported on Wednesday.
The investigation report did not find that I knew the published report was affected, or that I had enough information to understand that it might be. It treated the allegation as originally framed and the separate question of follow-up as distinct matters, and found neither substantiated.
I would be grateful if the decision-maker could identify the evidence on which the proposed conclusion relies, and explain how it differs from the findings of the investigation.
The final outcome letter arrived the following week.
OUTCOME LETTER: EXTRACT
Having considered the investigation report and the department’s response, I have concluded that Marcus was aware of a reporting discrepancy and failed to escalate it appropriately.
As the manager responsible for the reporting process, Marcus was expected to take appropriate action when made aware of an issue that could affect the integrity of management information. The decision-maker considers that his responsibilities required him to recognize the potential implications of the variance and ensure that the matter was appropriately followed up.
The organization has therefore concluded that his handling of the discrepancy fell short of the required standard.
Marcus read it twice, then went back to the original email. It said variance.
The management referral had called it a discrepancy. The terms of reference had carried that description forward, and the outcome letter used it again.
He read the documents once more.
The difference was only one word. But it was the difference between what he had been told and what the organization now said he had known.
The word had travelled through the process. By the end, the qualification had largely disappeared.
There was another problem with the wording.
The letter concluded that Marcus was aware of a discrepancy. It then shifted to saying that his responsibilities required him to recognize the implications of the variance.
Those were not quite the same proposition. The investigation had distinguished between what Marcus knew and what he might reasonably have been expected to do. The outcome letter moved between the two without explaining how its reasoning addressed the investigation’s separate findings.
Two questions worth asking
When an investigation begins with a suspicion, the obvious concern is whether the investigator has tested it fairly.
But there is another question: what happens after the investigation is complete?
An organization can commission a competent investigation, receive a careful report, and still produce an outcome that does not accurately reflect what the investigation established.
The first question is: what could the investigator have discovered that would have made them less confident in the original suspicion?
This is not an invitation to search for reasons to dismiss an allegation. It is a test of whether the investigation is genuinely capable of changing its view.
Investigators should consider evidence both for and against an allegation. They should also be prepared to reconsider what they have already collected in light of new evidence. Evidence does not become more reliable simply because it was gathered first.
The second question is: does the organization’s account accurately reflect what the investigation established, including what it could not establish?
A finding that someone could have acted more carefully is not necessarily a finding that they breached a particular requirement.
A failure to follow up is not automatically proof that someone understood the significance of the issue.
And a decision-maker who reaches a different conclusion from the investigator needs to explain the evidential basis for doing so. A different conclusion is possible. An unexplained one is much harder to defend.
For Marcus, the distinction was between knowing about a variance and knowing about a reporting discrepancy. The investigation had examined whether those were the same thing. The final account treated them as though they were.
An investigation intended to establish facts must be capable of examining evidence that challenges its starting view. The organization must also avoid turning a qualified finding into a more definite conclusion simply because the original account is easier to communicate.
You can take an allegation seriously without treating the explanation the organization has constructed around it as already established.
If you are the person being investigated
If you are the subject of an investigation, it can be difficult to know whether the process is examining what happened or simply building a case around an existing account.
You may find it useful to ask:
- What exactly am I alleged to have done? What evidence supports that specific allegation?
- What has been inferred? Is the organization treating what I knew, what I should have known, and what it now knows as though they were the same thing? Marcus knew about a variance. Did he know about a discrepancy?
- What circumstances have been considered? Were the procedures, information available at the time, normal working practices, and relevant constraints examined?
- Have alternative explanations and contrary evidence been properly examined? Or has the investigation mainly gathered information that supports the original account?
- Does the final account reflect what the investigation actually established? If the decision-maker has reached a different conclusion from the investigator, has the reasoning and evidential basis been explained?
These questions do not guarantee a particular outcome. Nor should you assume that every disagreement with an investigation means the process is unfair.
But they can help you identify where the organization’s account may have moved beyond what the evidence supports.
If the matter carries significant employment, legal, or professional consequences, consider obtaining advice from a lawyer, union representative, or other appropriate adviser.
The point is not to make an investigation easier to defeat. It is to make sure that, whatever conclusion is reached, the organization can explain how it got there.
