When Your Former Employer Tells Your Story

When a former employer investigates events from your time in the organization, it may have years of records, witnesses and institutional context at its disposal. You may be asked to account for the same events without having equivalent access to the past.

Daniel arrived at the pub before Graham.

They had known each other since university. They had played on the same sports team, neither of them particularly well, and had stayed in touch over the years. They were not the sort of friends who spoke every week. They were, however, the sort who could resume a conversation after six months without having to explain the gap.

Graham arrived, put his bag down and looked at Daniel.

“You look as though you’ve been given homework.”

“Something like that.”

“Still doing it at the last minute?”

Daniel smiled, but only briefly.

“My old company has been investigating something from 2022. A reporting issue. Customer complaints, across several markets.”

“Your old company?”

“Yes. They commissioned an internal investigation into the old reporting arrangements. Apparently they’ve been going through the records and interviewing people. Someone I used to work with called me a few days ago. Asked whether I’d heard anything about the reporting issue.”

“And had you?”

“No. He said the investigation had been completed. The company had reached findings, and my name had come up.”

Graham waited.

“Then I got a letter from the regulator.”

Daniel took a folded sheet of paper from his jacket and placed it on the table.

The letter referred to enquiries concerning historical reporting arrangements during the period January to December 2022. It said the authority was examining the company’s reporting arrangements during that period and understood that Daniel had been Regional Director.

It asked him to contact the authority.

“Have you spoken to a lawyer?” Graham asked.

“Yes. As soon as I received this.”

“What did they say?”

“That I shouldn’t assume the company’s investigation and the regulator’s investigation are the same thing.”

“Are they?”

“Apparently not.”

Daniel explained that his lawyer had separated three things: what the company had investigated and concluded; what it had actually communicated to the regulator; and what the regulator was now investigating for itself.

“Surely the company has given them its investigation report?” Graham asked.

“We don’t know that. It might have given them the report, a summary, selected documents, or something else. The lawyer says we need to establish what was actually provided.”

“But if the company has reached findings about you, the regulator will have those findings.”

“Possibly. But the company’s findings aren’t the regulator’s findings. The regulator may use the company’s material as a starting point. It can also examine the underlying documents, speak to other people and reach its own conclusions.”

Graham looked at the letter.

“So the company has completed its investigation, and now the regulator wants to speak to you.”

“That’s about where I am.”

“And what does your lawyer want to know?”

Daniel thought for a moment.

“Quite a lot, apparently.”

What the company says happened

By the time Daniel met Graham, he had received a summary of the company’s findings, together with some of the material on which those findings appeared to rely.

He took the papers out of his jacket.

Graham read the relevant section of the summary.

It said:

In March 2022, Regional Compliance reported deficiencies in customer complaint reporting. The matter was discussed at the April management meeting. In May, Daniel approved continuation of the existing reporting arrangements. The deficiencies remained unresolved until December 2022. No adequate corrective action was initiated during this period. The investigation therefore found that regional management was aware of the deficiencies and failed to ensure timely remediation.

“That’s fairly definitive,” Graham said.

“Yes.”

Graham read the last sentence again.

“It says regional management. You were part of regional management.”

Daniel nodded.

“So even where it doesn’t name you, the conclusion reaches you through the position you held.”

“That’s how I read it.”

“Then let’s look at what they actually say you did.”

Daniel handed him three extracts.

The first was the March email:

Initial review has identified inconsistencies in the reporting of customer complaints across several markets. Further work is required to establish the extent and cause of the inconsistencies. We will provide an update following the regional review.

The second was from the April management meeting:

Regional reporting inconsistencies discussed. Further review to be undertaken by Compliance. Existing reporting arrangements to continue pending completion of review.

The third was the May approval record:

Continue current reporting arrangements pending completion of regional process review. Conditions: Compliance to complete review and escalate material deficiencies through established reporting channel.

Graham read the three extracts again.

“I’m not saying there wasn’t a problem,” he said. “But the wording changes quite a bit between these and the summary.”

Daniel showed him the comparison he had prepared.

Original material or evidence shown to DanielCompany’s summary
March: Compliance identified inconsistencies. Further work was required to establish their extent and cause.Compliance reported deficiencies.
April: The inconsistencies were discussed; Compliance was to undertake further review.Management was aware of the deficiencies.
May: Existing arrangements were to continue pending review, subject to conditions placed on Compliance.Daniel approved continuation of the deficient arrangements.
The material provided to Daniel did not identify the evidence supporting this particular conclusion.Daniel failed to ensure timely remediation.

“The May approval wasn’t unconditional,” Daniel said. “It allowed the existing arrangements to continue while Compliance completed its review. Compliance was also required to escalate any material deficiencies through the established reporting channel.”

Graham looked at him.

“So the approval depended on Compliance doing something.”

“Yes.”

“There’s another part,” Daniel said. “The problem wasn’t fully resolved until December. That’s seven months after the approval.”

“So the review was supposed to happen, and the problem was still there seven months later,” Graham said.

“Yes.”

“Then there are two things to establish. Whether Compliance completed the work and escalated what it found, and whether you were expected to check that it had happened.”

“That’s what I need to find out. I don’t remember checking.”

Graham put the papers down.

“Then that’s something you need to look at. But it’s not quite the same as knowing there was a serious problem and deciding to leave it there.”

“That’s what the lawyer said.”

“Good. At least someone’s asking the right questions.”

The documents did not settle the matter. The company might have other evidence. The regulator might have material Daniel had not seen. The extracts were enough, however, to show how the same events could be described differently.

An initial finding of inconsistencies had become a report of deficiencies. A discussion had become awareness. A conditional approval pending review had become approval of deficient arrangements. An unresolved problem had become a failure by Daniel to ensure remediation.

That progression is worth examining.

How an account becomes more certain

The company’s summary may have been prepared after months of reviewing records and interviewing people. It may have passed through several hands before reaching its final form.

At each stage, information can be summarized, filtered, categorized and interpreted. A preliminary observation becomes a reported issue. A reported issue becomes a known problem. A discussion becomes awareness. A decision made under particular conditions becomes approval. An unresolved problem becomes evidence of a failure to act.

Qualifications disappear. Distinctions become less visible. The account becomes easier to communicate and easier to use in a subsequent decision.

This is narrative hardening.

The final version may still contain statements that can be traced to genuine documents. That does not mean the overall conclusion preserves the limits of those documents.

The company may have a coherent account of what happened. The regulator may receive that account, examine the underlying material, test it against other evidence and reach its own conclusions.

But Daniel does not enter the process at the same point the company started.

The organization has already had an opportunity to assemble the history. It may have developed a coherent account before Daniel even knew that he was relevant to it.

This is not proof that the account is dishonest. Nor does it mean the regulator will accept it uncritically.

It means that the account may have acquired institutional solidity before the person most directly affected has had an equivalent opportunity to examine it.

What the lawyer is looking for

When Daniel first met the lawyer, they had started with the March 2022 email.

It came from Regional Compliance. Its subject was customer complaint reporting across several markets.

“What did you understand when you received this?” the lawyer asked.

“That Compliance had found inconsistencies in the reporting. That they were looking into them.”

“Did you understand that the full extent of the problem had been established?”

“No. It says further work was required.”

“Did anyone subsequently tell you that the problem was more serious than the email suggested?”

Daniel had paused.

“I can’t remember being told that. But I can’t say categorically that nobody did.”

“That’s important. We need to establish what the evidence shows was communicated to you, and what you understood from it.”

The lawyer turned to the April meeting minutes.

“These say the inconsistencies were discussed. Do you remember the meeting?”

“I remember there was a discussion about reporting. I don’t remember the exact wording.”

“Do you remember anyone explaining the extent of the problem?”

“Not specifically.”

“Then we need to be careful about what those minutes establish. They show that you were present and that the subject was discussed. They don’t necessarily establish what you understood or what conclusions you drew from it.”

The lawyer turned to the May approval record.

“And this one. What did you think you were approving?”

“Continuation of the existing arrangements while Compliance completed its review. With the conditions recorded here.”

“Did you understand that as accepting a known risk?”

“No. I understood that the review was still under way and that Compliance would escalate anything material.”

“Did you check whether they did?”

Daniel paused.

“I don’t remember checking.”

“That’s something we need to examine. It may be relevant to your responsibilities. But it is a different question from whether you knowingly approved continuing arrangements that you understood to be deficient.”

The lawyer put the papers down.

“I’m not saying the company’s conclusions are wrong. There may be other evidence we haven’t seen. But we need to know what each piece of evidence establishes, what it doesn’t establish, and how the company has moved from one to the other.”

Daniel had looked at the papers.

“So we’re taking apart the conclusion?”

“We’re examining how it was reached. If the reasoning is sound, it should withstand that examination. If there are gaps, we need to understand what they are and whether they matter.”

There was another issue.

The company’s findings referred to deficiencies that remained unresolved until December 2022. The May approval had recorded what Compliance was expected to do, but the problem had continued for another seven months.

“Was it your responsibility to make sure the review was completed?” the lawyer had asked.

“Some of it, yes. I was responsible for the regional operation. But Compliance had been given the review and escalation responsibilities.”

“Those responsibilities don’t necessarily remove yours. We need to establish what you were expected to follow up, what Compliance was supposed to report back, and what you were actually told.”

Daniel had acknowledged that he might not have done enough.

He might have assumed the review was progressing. He might have failed to check whether the conditions attached to the May approval had been met. That could matter.

But it was not quite the same question as whether he had knowingly approved continuing a process he understood to be defective, then deliberately allowed it to remain that way.

The lawyer warned him not to approach former colleagues or try to assemble his own version of events before they understood the scope of the enquiries.

“First, we need to establish what the regulator is asking you about, what material it is relying on, and what opportunity you have to respond. We also need to understand what the company has actually provided. Don’t assume that its findings summary is the evidence itself, or that anything you say to the company will necessarily reach the regulator in the form you intended.”

“There’s a lot we don’t know yet,” Daniel had said.

“Exactly. Let’s not fill the gaps with assumptions.”

The organization has a head start

Graham looked again at the papers.

“There’s something else here,” he said.

“What?”

“They’ve had a head start. They still have the systems, the people, the correspondence, the meeting records. They can go back and look at what happened from inside the organization.”

Daniel nodded.

“You can’t do that anymore,” Graham continued. “You’re trying to reconstruct the same period from outside. You might have an email, but they have the chain, the attachments, the records that followed it, and whatever internal discussion took place afterwards.”

“So what am I supposed to do with that?”

“Recognize that you’re not starting from the same position.”

This is more than a difference in the number of documents each party possesses. The organization still has access to the environment in which those documents were created: the systems, procedures, reporting relationships, people and surrounding events that may help explain them.

Even where both sides have the same document, they may not have equivalent access to the context that gives it meaning.

Evidential possession is not evidential completeness.

The documentary record of a decision is not necessarily the decision environment in which it was made.

The organization’s records may be extensive, but they are not the past itself. They are what survived in its systems, what people recorded, and what the subsequent investigation was able to assemble.

Daniel is facing an account constructed from that material. He may have to answer for events whose full context is no longer available to him.

The part that cannot be recovered

There is another difficulty, and it is not solved by obtaining more documents.

A record can show what was written, sent, approved or recorded. It may not show what people understood at the time, what was said informally, what other information was available, or what a decision meant in the circumstances.

A meeting minute may record that an issue was discussed. It may not capture the questions asked, the answers given, or whether participants understood the same thing by the words they used.

A decision paper may record an approval. It may not preserve every conversation that led to it, the competing priorities in the room, or the practical constraints affecting the people responsible for carrying it out.

Some of that context may be recoverable from other records or witnesses. Some may not.

And time makes the problem harder.

Daniel may remember the general issue, the people involved and the broad sequence of events. He may not remember precisely which conversation came before another, whether a particular qualification was discussed in a meeting or in a later call, or what he was told about the progress of the review several months afterwards.

His memory is not an archive.

The company may have been able to reconstruct a timeline by searching records Daniel can no longer access. It may have interviewed people while the events were still relatively fresh. Daniel is now being asked to respond to a version of the past that has already been assembled without him.

The documents and descriptions put to him may bring back some recollections. They may also leave other events untouched. People remember associatively. A particular email may bring back a meeting. A name may evoke a conversation. A phrase may remind someone of a disagreement.

But a person cannot reliably summon every unrecorded conversation or forgotten detail simply because it has become important.

“Remember better” is not a useful instruction.

If a conversation was never recorded and the people involved no longer remember it, the detail may simply be gone. The individual may be able to challenge an inference, identify a missing qualification or show that a document has been interpreted too strongly. But they cannot necessarily recreate the entire decision environment in which they once operated.

Graham and Project Meridian

Graham had been quiet for a while.

“Something similar happened to me,” he said. “Not a regulator. Different situation. Project Meridian. Years ago.”

Daniel looked up.

“I nearly didn’t keep any notes. I thought I’d never forget it. But I knew things were going badly, and eventually I started writing down what happened at meetings and conversations.”

“Good thing you did.”

“Yes. But even with those notes, if you asked me now to give you a complete timeline, I’d struggle.”

“What do you remember?”

“The pressure. Trying to explain what we knew and what we didn’t. The meetings. The account of the problem changing around me. I remember the steering committee making a decision that wasn’t mine to make.”

“Which decision?”

“I’d have to check my notes. I don’t remember the exact sequence well enough to give you a reliable account of it now.”

He paused.

“I can find some of it in what I kept. Dates, emails, things I wrote down. But those notes aren’t a complete record of every conversation. And I can’t fill in all the gaps from memory.”

Daniel nodded.

“That’s the trap, I think,” Graham said. “When something is happening to you, especially when it’s frightening or important, you assume you’ll never forget it. You think the details are burned into your memory. They aren’t.”

He looked at Daniel.

“You remember the experience. That isn’t the same as remembering the evidence.”

“And if you hadn’t kept notes?”

“Then I’d have very little to go back to.”

Graham took a drink.

“That’s not a reason to assume notes will give you everything, either. I could recover some particulars. I couldn’t reconstruct the whole situation. And I still had to be careful not to turn what I remembered into a chronology I couldn’t actually support.”

“I was responsible for some things,” Graham continued. “I could have been clearer in how I reported what was known and what hadn’t been established. But I wasn’t the steering committee. I didn’t make its decisions.”

“Did the distinction matter?”

“It mattered to me. Whether it mattered to everyone else is another question.”

He looked down at the table.

“And the more I tried to explain the difference, the more the discussion seemed to become about whether I was the right person to be doing the job.”

Daniel looked at the papers in front of him.

“That’s what worries me. They have a timeline. They have a summary. They have documents. And I have to work out what I remember from years ago, against a version of events they’ve already put together.”

“Yes,” Graham said. “And the version they’ve put together may be right about some things. That doesn’t make every conclusion in it right.”

What Daniel can still establish

The asymmetry is real. It does not mean Daniel has no agency, or that the company’s account is beyond challenge.

There are things he can establish, although they do not amount to recovering the past in full.

He can establish his procedural position: why the regulator wants to speak to him, what the enquiries concern, what obligations apply to him, what deadlines exist and what opportunities he has to respond.

He can establish what the regulator is actually asking, rather than assuming that the company’s findings summary is a complete description of the regulator’s concerns.

He can examine the evidence that has been put to him. He can distinguish what a document records from what the company says it proves. He can identify where a conclusion depends on an inference, and whether the available evidence supports that inference.

He can also identify the limits of his own knowledge. He may be able to say what he remembers, what he cannot now recall, what he understood at the time and what he only learned later.

Where relevant records or witnesses can be identified, their significance can be considered with his lawyer. Any personal notes or other records he has legitimately retained may also matter.

None of this restores the company’s systems or gives him access to every conversation that took place. Nor does it guarantee that the regulator will accept his account.

For Daniel, three questions now matter:

  • What has the company actually told the regulator?
  • What documents or other evidence support each finding about him?
  • What do those original documents say, compared with the conclusions drawn in the company’s summary?

These are questions to establish with independent legal advice, in the context of the regulator’s process. They are not necessarily questions Daniel can answer simply by asking his former employer, and he should not assume that he has an automatic right to every document he would like to see.

The company may have an interest in demonstrating that it identified the problem, investigated it, took corrective action and dealt appropriately with those responsible. Daniel’s interests may not align with that account.

This does not mean the company is acting improperly. It means the two parties are no longer necessarily trying to establish the same thing.

The company may be explaining its institutional response. Daniel may need to establish his own knowledge, decisions, authority and conduct within the events under examination.

Those are related questions, but they are not interchangeable.

Back at the pub

Daniel looked at Graham.

“So I don’t yet know what the regulator thinks.”

“No.”

“And I don’t know exactly what the company has told them.”

“No.”

“But I do know what the company says happened.”

“You know what its summary says happened,” Graham replied.

Daniel smiled faintly.

“That’s a start. Not much of one, though.”

“Well, it’s what you’ve got. How well can you make use of it? That’s for you and your lawyer to determine.”

They sat for a moment.

The company had a version of the past. The regulator was examining it. Daniel would have to establish what the regulator was actually asking, and what evidence lay behind it.

He could not recover every conversation, every decision or every detail of a working environment he had left years earlier.

But he did not have to treat the company’s account as though it were the past itself.


Suggested related reading

If you’re trying to understand how an organizational account can become difficult to challenge:

– What Happens to the Information You Raise
A concern can be reported, acknowledged and formally handled without its original meaning or significance surviving the journey through the organization.

– When an Investigation Starts With Its Answer
How an assumption embedded in an investigation’s referral or terms of reference can shape the questions asked and the conclusions drawn from the evidence.

– When the Evidence Starts Agreeing
How one person’s account can pass through several people and records, acquiring the appearance of independent corroboration along the way.

– When the Investigator Is Already Inside the Story
How an investigator can work conscientiously and still be constrained by the organization’s framing, background assumptions and limits on the scope of the enquiry.

– When You Wonder If You’re Becoming the Scapegoat
How an individual can have made genuine mistakes and still become the carrier of responsibility for a much wider organizational failure.

A note on legal advice

If you are contacted by a regulator about events involving a former employer, obtain independent legal advice. Your former employer’s lawyers represent the organization, not necessarily you.

How Centreline Clarity can help

Centreline Clarity helps individuals make sense of difficult organizational situations by examining the conditions shaping them: who holds authority, how information moves, where pressure and constraints arise, what remains uncertain, and which options may still be available.

The aim is to develop a clearer picture of the situation before deciding what to do next.

Structural Snapshot

Disclaimer: This article is for general informational purposes and does not constitute legal advice. Regulatory processes, rights and obligations differ by jurisdiction and circumstance.

Explore Framework

Return to Articles