# Telegram Case Board: Evidence & Annotations

Canonical page: https://phishdestroy.github.io/TgWitness/docs/case-board/

Organize saved Telegram observations, exact highlights and action slices on a Case Board. Link team annotations and presentations to their source records.

[Project context and measured scale](https://phishdestroy.github.io/TgWitness/docs/reference/overview/)

[Documentation index](https://phishdestroy.github.io/TgWitness/llms.txt)

Turn saved messages into a case your team works on together.

Bookmarks, exact quotes, slices and discussion, each linked to its source. Every change is a signed revision.

## From a message to a case card

1. **Investigation → Case Board** (Standard or Expert mode). Make a collection for the case.
2. In **Journal** or a chat hit **To board** (or **B**). The card lands in Inbox, give it a title and move it.
3. Select text in a message, **Highlight → board** keeps the exact quote and version. Note why it matters.
4. Discuss, set a status, jump back to the source whenever needed. **Presentation** walks the team through it.

### Follow one changed payment link

Synthetic example · local illustration

1. **Capture.** Open saved observation #142 and its message version.
2. **Bookmark.** Keep the quote, source reference and your question on a card.
3. **Review.** Add a team comment and move the card to Review.
4. **Present.** Walk through the collection and open the cited source context.

#### Saved observation #142

“Use the new payment link.”

Operations chat · message 38 · observed 09:12 UTC

#### Card: changed destination

> Use the new payment link.

Question: which destination appeared in the earlier version?

#### Team review

Analyst: compare with observation #101.

Status: Review · revision retained

#### Source context

Card → saved version → earlier observation

The annotation and the Telegram observation remain separately identifiable.

## Save a useful range once

Shift-click two messages for **Slice between**, use **Slice by time**, or save the current Journal filters. **Show records added since bookmark** shows what came in later.

Time slices use observation time; message-ID slices follow those messages as they change.

## Give each colleague the right role

**Reviewer** reads, **Analyst** adds cards and comments, **Operator** also manages collections and decisions. Chat permissions apply to cards too.

## Carry the work into a deliverable

Slices export as signed JSON or CSV. Reports can include bookmarks, slices and comments, set that in [Report studio](https://phishdestroy.github.io/TgWitness/docs/reports/). For a limited recipient, use a [handover](https://phishdestroy.github.io/TgWitness/docs/handover/).

Details: [Case Board reference](https://phishdestroy.github.io/TgWitness/docs/reference/case-board/).