Group chats · Review checklist

A group chat needs a participant map before it needs a polished PDF.

List the relevant people, name or number changes, date range, and system events before sharing a group conversation. Display names help navigation, but they are not independent proof of identity.

Updated 2026-09-077 minTextTrace

Participant map

Visible labelThe display name or number shown in the source.
Change noteGroup rename, contact rename, number change, or participant join/leave event.
Relevant roleWhy the person matters to this review, stated neutrally.
UncertaintyAny label that cannot be independently connected to a person.

Keep conversational context

Replies, reactions, quoted messages, deletion markers, group notices, and attachments can change what a line means. Include enough before and after each key exchange to make the sequence understandable. Avoid extracting only one participant’s rows if doing so removes the questions or events they were answering.

Final review

  • Correct group and relevant participant scope.
  • First and last requested dates visible.
  • Display-name changes and system events retained.
  • Replies and attachments connected to their surrounding messages.
  • Uncertain identity or timing labeled rather than guessed.
  • Original source stored separately from the readable working output.

Questions, answered precisely

Frequently asked questions

Does a display name prove who sent a group message?

No. It is a label present in the source. Identity may require account, device, testimony, or other context outside the export.

Should I remove unrelated group messages?

Only after the reviewer defines scope, and only while retaining enough surrounding context. Keep the original source unchanged.