The evidence problem
When the sequence of events is disputed, fragmented or spread across a large case file.
Build a source-linked chronology from statements, correspondence, reports, records, decisions and transactions.
When the sequence of events is disputed, fragmented or spread across a large case file.
Statements, orders, correspondence, reports, logs, decisions and dated records.
A source-linked chronology with conflicts, gaps and supporting document references.
Dates and events are identified across the supplied evidence.
Each event can be tied back to the document from which it was derived.
Where sources describe the same period differently, the conflict can be flagged for review.
Set the relevant timeframe, people and questions before extracting events.
Events are captured from orders, statements, emails, reports, logs and other dated records.
Each chronology entry retains a route back to the document that supports it.
Where sources describe the same event differently, both accounts are preserved and the difference is identified.
The chronology is checked for missing periods, duplicated events, timing conflicts and unsupported later summaries.
A structured record of the material actually reviewed, suitable for audit and later cross-reference.
Material observations presented with enough source information to locate the supporting record.
Where relevant, events, transactions, comparisons or issues arranged into a practical working schedule.
A separate record of missing material, ambiguity, assumptions and points that cannot safely be concluded from the supplied evidence.
Clear distinction between automated extraction, analytical review points and human-reviewed findings.
Professional evidence work should not hide the route from observation back to source. MOLE outputs are designed around traceability, scope control and explicit limitations.
The report states what was asked, what material was supplied and what falls outside the review.
Material observations are linked to identifiable source records rather than presented as unsupported assertions.
Extracted facts, analytical observations, unresolved points and limitations are kept distinguishable.
Automated signals remain review points until checked against the underlying material.
Reports can be versioned so later evidence or corrections do not silently overwrite the earlier analytical record.
Where the evidence cannot safely establish a proposition, the report should say so explicitly.
Open a secure MOLE case and track exactly what has been requested and delivered.