From scattered files to a counsel-ready brief.

Matter-2419 is a demonstration matter that contains the kinds of inputs teams bring to Setara every day: forwarded email chains, exported Slack threads, CSV audit logs, scanned documents, OSINT snapshots, and a handful of screenshots with no obvious home. By the end of this walkthrough, every fragment belongs somewhere. The output is a structured brief ready for counsel review.

Drag the source files into the ingest queue, or connect a folder. For matter-2419, the inputs are: fourteen email files (EML format), a Slack export archive, three CSV audit logs from the client's access management system, nine PDF documents, a set of screenshots, and an OSINT context file compiled by the analyst team. Setara accepts these as-is. You do not clean, rename, or reformat them first. Setara Core reads structure where it exists and infers context where it does not. As files enter the queue, a receipt appears for each one confirming format, size, and parse status.

The first resolved output for matter-2419 is the Timeline. Every event extracted from the source files is placed in chronological order. Each event is anchored to its source: click an event and the originating document, message, or log entry opens alongside it. For matter-2419 the Timeline spans forty-three days and contains one hundred and twelve discrete events. Eleven of those events were sourced from the Slack export. Twenty-six came from the audit logs. The remainder came from emails and documents. None of this was manually assembled. The Timeline is filterable by source type, by entity, and by date range. Gaps in the record are marked explicitly, not glossed over. An analyst can add a note to any event, which is attached to the event in the exported brief.

The Relationship Graph maps who knew whom, who communicated with whom, and which entities co-appear across the evidence. For matter-2419, the graph resolves seven named individuals, two organisations, and four systems. It shows which connections are evidenced directly (a sent email, a logged access event) and which are inferred from co-occurrence. Direct connections are drawn as solid lines. Inferred connections are drawn as dashed lines. The distinction matters for counsel. A direct connection is provable from the evidence as it stands. An inferred connection is a lead, not a fact. The analyst can isolate any node to see all evidence items that reference that entity. This is the fastest way to build an entity-specific evidence trail within a larger matter.

The inputs to matter-2419 were twenty-nine separate files across six formats, held across the analyst team's shared drive, email client, and a downloaded Slack export. There was no single view of the matter, no ordered timeline, and no way to know whether the documents corroborated each other or not. After running through Setara, the same material produced one Timeline, one Evidence Map, one Relationship Graph, and one structured brief. The analyst did not write the brief. They reviewed it, added notes where needed, and sent it to counsel. The time from first ingest to brief generation was under two hours. That is what the workflow looks like. No invented numbers, no comparison claims. Just the matter, start to finish.