
An internal investigation chronology is not a novel. It is a disciplined timeline of events, sources, gaps, and decisions. For boards and audit committees, it can be the difference between informed oversight and a blurred narrative. The chronology should separate allegation, document, interview statement, management response, and finding. That separation protects both fairness and accountability.
The starting point is a neutral issue statement. For example: "Alleged override of vendor approval controls between April and June." The chronology should then record dates, events, source documents, custodians, reliability level, and open questions. If a fact is inferred rather than documented, say so. If a witness account conflicts with an email, mark the conflict. Precision is kinder than confidence when facts are still moving.

The official Supreme Court judgment titled Union of India and Another v Deloitte Haskins and Sells LLP and Another considered statutory investigation material arising from the IL&FS episode. Applied only by analogy, the decision reinforces the practical importance of maintaining records capable of supporting later action. A board that receives an investigation update should be able to see the trail, not merely the conclusion.
A useful board chronology has four layers. The first is the event timeline. The second is an evidence index listing documents, interviews, logs, and external records. The third is an issue matrix connecting facts to policy, contract, or statutory concerns. The fourth is a remediation tracker that records decisions, owners, and due dates. Without the fourth layer, the chronology may diagnose a problem and then politely leave it in the corridor.
Confidentiality and privilege must be handled carefully. Investigation teams should decide early who will receive drafts, what labels will be used, and how electronic evidence will be preserved. Board papers should avoid unnecessary adjectives and should not declare culpability before the process is complete. Where urgent risk exists, interim controls can be recommended without prejudging the final outcome.
For implementation, management should keep a compact evidence bundle for this topic: the approved policy or contract clause, the responsible owner, the last review date, the decision note, and any unresolved exception.
The bundle should be short enough for a busy director to read and complete enough for a later reviewer to understand the decision.
Where the matter is recurring, add a dashboard line showing open items, ageing, monetary exposure where relevant, and the next escalation date.
This keeps the board record factual without turning every issue into a bulky legal file.
It also helps counsel or advisers step in quickly if the matter becomes contentious.
A single owner should confirm closure in writing, because unsigned comfort is rarely comfortable later.
Keep it dated and useful.
If the board or committee chooses not to escalate a known exception, the reason should be recorded in plain terms.
A restrained record of judgment is usually stronger than a silent record of optimism.
The same pack should show what changed since the previous review, so directors are not forced to rediscover the history each quarter.
Where external advisers are involved, the note should also distinguish business instructions from legal advice, and operational updates from privileged review.
That distinction protects candour while keeping routine governance visible.
Short records can still be rigorous.
They should also show the next review owner, because unattended controls tend to become folklore.
AGS Consulting assists boards, committees, and management teams with investigation chronologies, issue matrices, and defensible reporting formats. For support with a specific internal review, reach AGS Consulting through the contact section.
FAQs
What should an investigation chronology contain?
It should contain dated events, source references, custodians, evidence gaps, disputed facts, and links to policy or control issues.
Should allegations be included?
Yes, but allegations should be labelled as allegations until corroborated. The chronology should not convert suspicion into finding.
Can the board receive interim updates?
Yes. Interim updates are useful where risk is urgent, but they should clearly distinguish confirmed facts from pending review.
How does a chronology support remediation?
It connects facts to decisions, owners, and deadlines, allowing the board to monitor corrective action rather than simply note the issue.
