Backdated Notification, a Works Council, and a Regulator's Email

Preservation first - it is irreversible if missed. Issue a written legal hold the same day to IT, the site, and identified custodians: suspend auto-delete on the shared drive, preserve notification-system logs and audit trails (including any record of edits to timestamps), email, badge/access logs, and shipping records. Confirm in writing that deletion has stopped; a hold nobody confirms is not a hold.

Leadership and scope. Engage outside counsel to direct the investigation - this strengthens privilege and gives the board a defensible record. Define scope in writing: six shipments, the alleged timestamp alteration, whether other sites or analysts are involved, and whether any customer or patient was exposed.

Sequence the evidence. Review logs and system records before interviews. Interviewing first contaminates accounts and tells the subjects what to align on.

Stop the HR plan. Letting HR interview the analyst first, then hand her the notes, creates a witness whose account cannot be independently tested, hands her a document that will circulate, and forfeits control of the record. Interview instead under company-counsel direction with a clear oral and written warning: counsel represents the company, not the individual; the interview is to obtain legal advice; the individual may face personal exposure and may wish to consult their own lawyer; statements must be truthful. Document the acknowledgment.

Works council. Notify under the agreement before any disciplinary interview; local counsel should confirm whether consultation is required for fact-finding too. Keep the fact-finding interview and the disciplinary process on separate tracks to the extent local law allows.

You cannot promise anonymity or absolute confidentiality. The information will be used to investigate, may be shared with outside counsel, auditors, and insurers, and may have to be produced to the regulator or in litigation. Promising more creates a credibility failure at exactly the wrong moment and may support a separate claim.

Phrase it as a limit, not a reassurance: "We will handle this as sensitively as we can and share it only with those who need it to investigate and respond. We cannot promise complete confidentiality - we may have to disclose information to regulators, courts, or advisers. We will not tolerate retaliation against anyone who raises a concern or participates in an investigation."

Witness interviews:

• Notes and memoranda prepared by counsel for the purpose of legal advice may be privileged, but privilege is fragile: wide distribution, forwarding to the business, or including non-lawyers on distribution can waive it.
• In several jurisdictions the regulator can obtain witness identities and factual summaries even where legal analysis is protected; do not structure the investigation on the assumption that everything stays inside the company.
• An employee's own statements belong to the employee; asking witnesses not to discuss the interview is acceptable, coercing silence is not. Union or works council representatives may have presence rights.

The analyst specifically: she is a witness and possibly a subject. Give her the corporate-representation warning, do not give her other witnesses' notes, and document her request for any copy - do not agree casually.

Factors:

• Legal obligation. Some regimes mandate notification of confirmed non-compliance within a set period, with independent disclosure duties to customers or the public. Check before deliberating.
• Severity and character. Falsified records and shipments made without required clearance are aggravators; the conduct goes to integrity of the regulatory record, not just process slippage.
• What the regulator already has. The Thursday request covers the same quarter, so assume the logs will surface. The difference between self-reporting and being caught is usually the largest single driver of penalty.
• Cooperation credit and prior history. No prior findings weighs in favor; a pending cure notice elsewhere cuts the other way.
• Whether facts are known. A premature report that later needs correcting is worse than a brief, explained delay.

Sequencing. In the first 2–3 weeks: confirm from logs whether timestamps were altered and how many shipments were affected, establish whether site or senior management knew, and determine customer exposure. Then decide. If a statutory clock is running, notify within it and update as facts develop. Keep the information-request response accurate and complete, seek an extension if needed, and never make a representation the investigation cannot yet support.

Remediation regardless of the disclosure decision:

• A hard system block: no shipment release without an accepted notification - preventive, not detective.
• Segregate filing from shipping; the analyst should not be able to both submit and release.
• Immutable audit trail on notification timestamps, with alerts on edits.
• Lookback at other sites and the same analyst's other filings.
• Consistent discipline applying existing policy; document the rationale.
• Validate the fix with a post-implementation test, not a training record.

Document the decision either way: who decided, on what facts, with what advice. The reasoning will be examined later, and "we discussed it" is not a record.