How live summaries evolve
During a live workshop the transcript appears first and the summary catches up in cycles. Here is why that lag is normal and when a summary is stable enough to rely on.
RoomRadar does two jobs at once during a live workshop: it streams the transcript for every group, and it generates a summary of what each group is discussing. The transcript is near-instant; the summary catches up in cycles, a little behind it. That gap is by design, and this guide explains when the summary is settled enough to rely on.
Why the transcript leads the summary
The transcript is a live feed, words appear as people speak. A summary is a different task: it reads across everything said so far and distils the key points. RoomRadar runs that distillation in repeated cycles rather than after every sentence, so the summary always trails the live transcript by a short margin. If it waited to finish a summary before showing any transcript, the live view would feel far less responsive when every group is talking at once.
How summaries refine over time
Each cycle re-reads the discussion and revises the summary, so early points can be reworded, merged, or reordered as a group's conversation develops. Themes emerge and firm up the same way, the longer a group talks, the more settled its summary becomes. By the time you stop the session, the summary has had the whole discussion to work from and is ready to present.
FAQ
The transcript streams word by word, while the summary is regenerated in cycles that read across the whole discussion, so it always trails the live text by a short margin. That is normal.
Once a group settles, or once you stop the session. The final summary is generated from the full discussion, so it is the most complete version.
No. Each cycle revises the summary as the conversation develops, so points can be reworded or reordered. That refinement is how it stays accurate.