Bayan-Khulasa

An index into the testimony, not a shorter transcript

What a summary is actually for is finding testimony when a witness says something different in court. That means citations, and it means covering every statement.

  1. 01 Input

    Multiple recorded statements, as one document

    Testimony recorded across several sittings — examination-in-chief, cross-examination, statements recorded on different dates — is the case where manual summarising breaks down worst, because a topic index has to span all of them rather than exist once per sitting. A subject raised early and returned to later has to be grouped, and that can only be done by something tracking it across the whole record.

  2. 02 Structure

    Segmented by topic, not by page order

    Testimony is not organised, and a summary that follows the transcript sequentially reproduces its disorder. The output is categorised by subject, so related testimony sits together regardless of where in the record it was given.

  3. 03 Cite

    Every entry carries a page and line reference

    This is the axis on which a summary is useful or useless. A summary describing testimony without pointing to it is orientation — you can read it to remember roughly what was said, but the moment anyone asks where, you are back in the record hunting. A summary with page and line references is an index into the record, checkable by the other side and by the court, which is what makes it safe to rely on.

    • ✓Entries cite page and line, not page alone
    • ✓Citations resolve into the record you supplied
  4. 04 Review

    Read an index instead of building one

    Building a topic index by hand across multiple sittings of recorded testimony is a slow, error-prone task typically left for whenever there is time — which in a busy solo practice is rarely before the next hearing. Processing here runs in the background, and your time goes into reviewing an index rather than constructing one.

What it doesn't do

Stated plainly, so you can decide with the whole picture rather than finding out mid-case.

Review is not optional

Expect to spend real time reading and correcting the output, and budget for it rather than assuming a finished product. The saving is in not building the index, not in skipping the read.

Check citations on a statement you know first

Citation accuracy is the metric that decides whether this is useful, so test it yourself before relying on it. Run it over a statement you have already worked, then check whether the references resolve to the right page and line.

It indexes testimony, it does not assess it

Which testimony is damaging, which is contradictory, and what to do about it are legal judgments. Bayan-Khulasa organises the record so you can reach them faster.

Common questions

What does the output actually look like?
A topic-categorized index of the recorded statement. Each entry states the subject and cites the record by page and line, so you can go straight from the index to the testimony.
Does it handle testimony recorded across several sittings?
Yes, and that is the case it is built for. A topic index across multiple sittings is where manual summarising costs the most, because one index has to span every session.
Can I use the summary to prepare for cross-examination?
That is what the citations are for. An entry you can trace to a page and line is usable to confront a witness with an earlier statement; one you cannot is only orientation. Verify the specific citations you intend to rely on.

See it on your kind of material

Tell us what you're working with and we'll show you it running on something like it. Nothing to upload.

← All features