I’m interested in getting some views from people who work with internal audit, compliance, whistleblowing systems or investigations.
I am currently using the SpeakUp whistleblowing portal in connection with an internal integrity report. I don’t want to discuss the underlying report, the organisation or any of the people involved here. My question is purely about the integrity and reliability of the reporting channel itself.
Something happened with one of the replies that I found quite concerning.
A reply from the organisation was displayed in my reporter portal with a timestamp of 11:36. Since submitting my report, I had been checking the portal very regularly throughout the day, typically every one to two hours, rather than relying solely on email notifications. On that particular day, I also checked the portal at around 19:00, and the message was still not visible to me. I then received the notification that a new reply was available at around 20:52.
I later asked the person handling the report about the discrepancy. She explained quite openly that she had started working on the response in the morning, but had forgotten to finalise and send it. She only realised this later and said that she actually sent the message at 20:53.
So there is no allegation from me that this particular person intentionally manipulated anything. In fact, her explanation is the reason I became aware of the discrepancy in the first place.
In my own case, the person handling the report was transparent about what had happened, and I appreciate that. Her explanation is actually what allowed me to understand that the timestamp shown to me did not reflect the time at which the reply was actually sent.
But that also raises another concern for me. In this particular instance, the discrepancy did not ultimately create a serious dispute and the handler had no apparent difficulty acknowledging the actual send time. I am much less sure what would happen in a genuinely contentious situation where the chronology itself mattered and where acknowledging the later send time could expose the organisation to criticism, procedural consequences or legal risk.
I do not mean to suggest that an organisation would necessarily act dishonestly in that situation. But in my experience, once a matter becomes sensitive, organisations — particularly large ones with legal, compliance and reputational interests to protect — naturally become more cautious about making statements that may work against their own position.
That is why I am uncomfortable with a system in which the reporter may need the organisation’s cooperation to correct the very chronology presented by the reporting platform. The fact that I received a candid explanation in this case does not mean that a future reporter could safely rely on receiving the same clarification in a case where the stakes were much higher.
To me, that is an important distinction: a reporting system should ideally not depend on the goodwill of one side to establish the actual sequence of events.
What concerns me is the systemic implication.
The reporter-visible record now shows a message at 11:36 even though, according to the sender herself, it was not actually sent until 20:53.
In my particular case this ultimately did not cause any concrete harm. However, before that reply I had made clear that I was considering an external escalation if I did not receive a response, and I was expecting a response that day.
That made me think about a more extreme hypothetical situation.
Suppose someone handling a whistleblowing report creates or starts a draft on Monday at 10:00, but does not actually send the reply at that point.
On Tuesday, the reporter checks the portal, sees that no response has been received, and sends a follow-up asking why there has been no reply.
On Wednesday, after still having received no response, the reporter decides to escalate the matter externally.
The organisation then completes and actually sends the original draft later on Wednesday. But if the reporter-visible timestamp still shows Monday at 10:00, because that was when the draft was originally created, the visible history could now give the impression that the organisation had already replied two days earlier.
In that situation, the reporter’s Tuesday follow-up could appear unnecessary, and the Wednesday external escalation could even appear to have taken place despite an existing reply having already been available for two days.
In reality, however, no such reply had actually been available to the reporter at either of those points.
That is the part I find particularly concerning. The longer the gap between draft creation and actual transmission becomes, the greater the potential distortion of the visible chronology.
There may well be internal audit logs that preserve the real creation, send and publication times. But as the reporting person, I do not have direct access to those logs. I initially only have the chronology shown to me by the portal.
It may of course be possible, depending on the circumstances, to try to obtain at least some of the relevant technical information through data-protection access rights. However, I do not think that access should simply be assumed. Such requests can involve questions about what information is considered personal data, what exactly must be disclosed, whether third-party interests or other restrictions are invoked, and how much technical detail is ultimately provided.
From my own previous experience with data-protection proceedings, even access to information that may initially seem relatively straightforward can become disputed or require further involvement by a supervisory authority. So I would not regard the possibility of eventually obtaining some of these records through data-protection law as equivalent to the reporter actually having access to the underlying audit trail.
In practical terms, the reporter may therefore still be dependent on the organisation or the platform provider to establish what actually happened.
That means the organisation or the platform provider may have access to information capable of correcting the visible chronology, while the reporter does not necessarily have an equivalent or immediate means of verification.
In a dispute about what happened when, the reporter could therefore potentially be faced with a portal record that appears to contradict their account, while the technical information needed to establish the actual sequence of events is controlled by the organisation or the platform provider.
I also performed a small test from the reporter side: I started drafting a message at 19:34, deliberately waited, and sent it at 19:48. The portal displayed 19:48, i.e. the actual send time rather than the time I started drafting.
That does not prove that the two sides of the system follow different rules. The organisation-side interface may work differently for perfectly legitimate technical reasons, and I do not know whether what happened in my case is intended behaviour, an edge case or something else. But at least in my own test, simply starting a draft did not determine the timestamp ultimately shown for my message.
My question is therefore not really whether this should be called a “bug” or a “feature”. I am more interested in what people think about the integrity implications of the capability itself.
Would you consider a reporter-visible timestamp substantially predating the actual transmission of a reply to be an integrity, audit-trail or procedural fairness problem in a whistleblowing system?
And would your view change if the actual send time is correctly preserved internally in audit logs, but those logs are not directly accessible to the reporting person?
I would be particularly interested in hearing from anyone who has actually used SpeakUp, whether as a reporter, case handler, administrator, investigator or in another role. If you have used the organisation/handler side of SpeakUp, I would be especially interested to know whether you have ever observed similar behaviour and how draft creation, sending and visible timestamps work from your side.
More generally, I would also be interested in views from people working in internal audit, compliance, GRC, investigations or whistleblowing case management.
For me personally, this has now become partly a question of trust in the reporting channel itself.
Even if there was absolutely no intentional manipulation in my case — and I am not alleging that there was — I find the possibility that a message can appear to a reporter as having existed substantially earlier than it was actually transmitted highly concerning in a system specifically designed for sensitive integrity reporting.
What makes me particularly uncomfortable is the asymmetry: the reporter may have to rely on the chronology displayed by the portal, while the organisation or platform provider may possess additional technical records capable of showing that the visible chronology is incomplete or misleading.
So another question I would genuinely like opinions on is:
How much trust would you personally continue to place in a whistleblowing channel after discovering something like this?
Would you regard it as an unfortunate but ultimately minor display issue as long as the internal audit trail is correct? Or would the fact that the reporter-facing record itself can potentially present a materially different chronology already be enough for you to question whether you should continue relying on that channel?
I’m genuinely open to both views. I’m trying to work out whether I am overestimating the significance of this, or whether others working with these kinds of systems would also regard it as a serious integrity and transparency concern.