Why transcript ordering matters

This guide helps when the transcript looks "mixed" and you are unsure whether conclusions are still safe to use. You usually need it during fast decision moments, overlapping speech, or right after short reconnect events.

Quick path:

1. Check whether ordering affects a decision, not the whole transcript.
2. Compare the three segments around the suspicious point.
3. Confirm the decision out loud and have the table restate it in one sentence.
4. Mark what is verified before you move on.

When ordering really matters

Not every ordering shift is a problem. If two examples switch position, impact is often low. If a "yes" and "no" switch position, meaning can change.

Start with decision-critical content: decisions, priorities, owners, and deadlines. For everything else, you can usually continue and verify later. If you also see delayed text, begin with [Troubleshooting transcription latency](/guides/advanced/troubleshooting-transcription-latency).

Common causes of ordering drift

The most common cause is overlapping speech: two people start at nearly the same time and segmentation splits the sequence. Another common cause is a short phone reconnection during a dense discussion block.

If the same table keeps dropping, treat it as a stability issue first, not an editing issue. Follow [Device reconnection behavior](/guides/advanced/device-reconnection-behavior) and then validate ordering once the stream is stable.

30-second verification for decision points

When something looks wrong, do not stop the entire table. Run a short verification:

1. Say: "I want to lock this accurately. Can you restate the decision in one sentence?"
2. Have one person state decision + owner + timing.
3. Have a second person confirm or correct it.
4. Record the confirmed sentence and continue.

This usually takes under 30 seconds and is faster than trying to reconstruct old lines live.

When to ignore and when to intervene

You can usually ignore minor ordering drift when:

• discussion is still easy to follow
• no decision or commitment is affected
• the summary remains coherent

You should intervene immediately when:

• ownership is assigned to the wrong person
• priority order appears reversed
• the same symptom appears across multiple tables

If multiple tables are affected, combine this with [Workshop infrastructure reliability checklist](/guides/advanced/workshop-infrastructure-reliability-checklist).

Related guides

• [Troubleshooting transcription latency](/guides/advanced/troubleshooting-transcription-latency)
• [Device reconnection behavior](/guides/advanced/device-reconnection-behavior)
• [Parallel conversations explained](/guides/advanced/parallel-conversations-explained)
• [What to do when summaries feel wrong](/guides/analysis/what-to-do-when-summaries-feel-wrong)
• [Workshop infrastructure reliability checklist](/guides/advanced/workshop-infrastructure-reliability-checklist)