01
Source-native evidence
Slack remains a conversation. ServiceNow remains an incident. Versions, relationships and provenance stay intact.
The platform
From mandate
to finding.
One controlled workspace for authorising the investigation, connecting the evidence, reconstructing the matter and proving the outcome.
The complete investigation workflow.
Telha is organised around the case, not the search box.
01
RequestDescribe the allegation, purpose and proposed scope.
02
ApproveAuthorised reviewers grant a time-limited mandate.
03
CollectAdmit only the evidence permitted by the case.
04
ReconstructConnect events, people, records and decisions.
05
ReportProduce evidence-backed findings and a defensible brief.
Inside the platform.
The surfaces investigators work in, from the first request to the final brief. Illustrative previews: product screenshots to follow.
01 · Memory
Company memory, indexed and governed.
Telha continuously ingests and versions business communication into one searchable index: entities linked, chronology preserved. Access opens only inside an approved case.
- Always-on ingestion and versioning
- Keyword and semantic search
- Search runs inside case scope only
Search · Case 26-014
Scope enforcedSlack
Exchange
ServiceNow
Out of scope
Out of scope
02 · Mandate
Scope the mandate before anyone sees evidence.
The request captures purpose, custodians, systems, date range and expiry. Approvers grant a time-limited mandate that becomes the enforceable boundary of the case.
- Named investigators and approvers
- Explicit custodians, systems and dates
- Automatic expiry with approved renewal
New mandate request
Awaiting approvalPurpose
Custodians
Date range
Systems
ExchangeSlackServiceNowSharePoint
Approve mandate
03 · Evidence
Admit evidence without losing its provenance.
Only evidence permitted by the mandate can enter the case. Each item arrives source-native, with versions, participants, timestamps and hashes preserved.
- Source-native records, not flattened text
- Versions and edits retained
- Hashes and custody events on every item
Case 26-014 · Evidence
126 admittedSlack
Exchange
ServiceNow
SharePoint
Upload
04 · Reconstruction
Rebuild the chronology as it was known.
Connect events across systems and separate when something happened, when it was recorded, and when the organisation learned of it.
- One timeline across every source
- Knowledge-state tracking per event
- Corrections preserved, never overwritten
Reconstruction · Decision history
4 systems09:14
Risk first raised in SlackLinked to the project team and source thread.
11:42
Incident opened in ServiceNowInitial severity recorded as Medium.
14:07
Policy exception approvedApproval document and email chain admitted.
05 · Findings
Findings that carry their receipts.
Each conclusion stays linked to its supporting, contradictory and missing evidence, and exports as a defensible brief.
- Supported, contradicted and gap status
- Source-linked citations throughout
- Brief export for counsel and regulators
Findings · Draft brief
Supported
Finding F-03
4 supporting1 contradictory
Linked evidence
Add finding
Export brief
Built for the work after search.
Keep the archive and eDiscovery tools you already trust. Telha adds the governed investigation layer.
02
Temporal reconstruction
Separate when an event happened, when it was recorded and when the organisation learned about it.
03
Findings with receipts
Each material conclusion remains connected to the exact evidence that supports or challenges it.
Not a database.
A ledger.
The distinction is the whole point. It decides whether a record survives a challenge.
Built to be changed
Records are updated in place. A value is edited, overwritten or deleted, and the previous state is gone. The record is only ever as trustworthy as the last person who touched it, which is exactly what an opponent will point to.
Built to be kept
Telha only ever adds. Nothing already written is edited or removed, so every state the record has held stays provable. You can show not just what it says today, but everything it has said, and the moment each thing changed.
Written once.
Never rewritten.
Why a Telha finding survives challenge comes down to one design choice: the record only ever grows. Nothing already written is edited, and nothing is deleted.
01
Append, never overwrite
When a record changes, Telha doesn't edit the original; it writes a new version and seals the old one in place. Every state a document ever held stays addressable, so history can't be quietly rewritten. Even a deletion is just another entry, marking the moment it was removed.
02
Three clocks on every fact
Telha stamps everything it knows three ways: when it was true, when the source recorded it, and when the organisation learned of it. That's what reconstructs what was known, and when, not today's version pretending it was always understood.
03
Every fact carries its receipt
Each entity and relationship links back to the exact passage of the exact source version it came from, hashes and custody intact. Findings inherit those citations, so every conclusion traces to primary evidence.
Connects to the systems you already run
Microsoft 365ExchangeTeamsSlackSharePointServiceNowJiraApproved uploads
Design partner programme
Prove this workflow on one real matter.
Design partners run a representative investigation end to end (approved mandate, scoped evidence, reconstructed timeline, defensible brief) inside their own environment.