Review session results before people leave the room

This guide helps you validate outcomes at the end of a RoomRadar session while participants are still present. Use it when you cannot afford post-session guesswork. In a hurry: reserve 10 minutes, validate each table with three questions, fix wording live, and leave with a clear list of decisions, open issues, and owners.

Fast path (2-6 steps)

1. Protect 10-15 minutes for end-of-session review in the agenda.
2. Show each table's captured outputs.
3. Ask: "accurate?", "missing?", "what to correct?"
4. Edit key wording live, especially decisions and owners.
5. Confirm unresolved items and assign follow-up owners.
6. Restate when final report will be shared.

When this guide is needed

Use this workflow when:

• multiple tables worked in parallel
• decisions were captured during discussion
• stakeholders will act on the output quickly

If you still have vague commitments, run a brief pass from [Capture decisions during discussion, not after](/guides/workflows/capturing-decisions-during-discussion) before final review.

End-of-session validation loop

1. Lock the time first

Do not let review time become optional. If time pressure appears, shorten report-outs before you shorten validation.

Tell participants early:

"We will close with a quick accuracy review so nothing important is lost."

2. Use one fixed three-question loop

At each table, ask exactly:

1. Is this accurate?
2. What is missing?
3. What should be clarified, merged, or removed?

Using the same loop table to table keeps pace stable and makes outputs comparable.

3. Correct wording where it matters most

Prioritize edits for:

• decisions (what exactly was decided)
• ownership (named person or role)
• timeline (date or milestone)
• unresolved items (not hidden inside decisions)

If transcript phrasing is ambiguous, ask the table to restate in one sentence and update immediately.

4. Prevent review from becoming a new ideation round

A frequent failure mode: validation turns into another 20-minute debate.

Use this boundary sentence:

"Right now we verify what was said. New ideas go to the follow-up list."

If fatigue is high, run compressed mode: top two outputs per table, decisions first.

5. Close with one shared snapshot

Before participants leave, state:

• validated decisions
• unresolved issues + owners
• report delivery timing

This is the handoff point to [Building a workshop report](/guides/analysis/building-a-workshop-report) or [Turning summaries into reports stakeholders can use](/guides/workflows/turning-summaries-into-reports).

What to do when something looks wrong

Summary feels too vague

Ask for one concrete example from the table and rewrite on the spot.

A table claims "we never said that"

Compare against transcript context, then let the table provide corrected wording. Mark confidence lower if disagreement remains.

Missing output from one table

If a device dropped late in session, do a short verbal reconstruction with that table before they leave. For repeated drops, see [Reconnecting a device without losing the discussion](/guides/setup/reconnecting-a-disconnected-device).

Too little time left

Skip low-impact items. Validate decisions, owners, and deadlines first.

This guide is for...

Use this guide when your risk is post-session misinterpretation.

If your risk is poor synthesis logic across many tables, start with [Combine results from many tables without flattening nuance](/guides/workflows/combining-results-from-many-tables).

Related guides

• [Capture decisions during discussion, not after](/guides/workflows/capturing-decisions-during-discussion)
• [Combine results from many tables without flattening nuance](/guides/workflows/combining-results-from-many-tables)
• [Turning summaries into reports stakeholders can use](/guides/workflows/turning-summaries-into-reports)
• [Building a workshop report](/guides/analysis/building-a-workshop-report)
• [What to do when summaries feel wrong](/guides/analysis/what-to-do-when-summaries-feel-wrong)