Meet course 03 — Run close and reconcile the right session

A meeting should leave a clear decision or next action, not only a history row. Ending it also requires care: leaving your own connection, ending the provider conference for everyone and obtaining a complete Workroomly History record are different outcomes. This chapter helps you manage those distinctions and recover when the views disagree.

In this chapter

• Confirm the actual participants and purpose
• Keep observations decisions and actions separate
• Choose Leave or end-for-all from your role
• Match the same session in History
• Diagnose the stage that actually failed
• Close the business result separately
• Practise a complete closeout

Confirm the actual participants and purpose

After an authorised join, compare the connected identities with the intended audience. A second connection bearing the organiser's name might be another tab rather than another person. Verify identity before interpreting the count or using a host action that affects everyone.

Restate the meeting's outcome and scope. For the sample-label review, choose one of two supplied versions and record the reason. Check that participants can access the actual material; an invitation or filename does not establish readability. If a required decision maker is absent, decide whether useful preparation can continue without pretending that a final decision was authorised.

Use only the capabilities needed and agreed for the session. Do not activate camera, microphone, sharing, recording or transcription to explore them during a sensitive discussion. A meeting note can be prepared in an approved separate location; do not assume Meet exposes a particular Minutes, Notes or transcript-export control.

Keep observations decisions and actions separate

An observation describes what someone found. A decision selects an option within the person's authority. An action says who will produce which output by when. Capture all three without turning one into another.

For example, the reviewer finds Label B easier to read; the decision maker selects B subject to a spelling correction; the author accepts returning the corrected text by an agreed time. Selection does not prove the correction is complete, and the note taker is not automatically the correction owner.

Record the exact version and condition. A decision about a practice sample does not approve publication, purchasing or a real customer change. If a later version changes more than the agreed correction, obtain the relevant review rather than treating the earlier decision as blanket approval.

A useful action record includes output, owner, date/time/timezone when relevant, review requirement and destination. If the reviewer's timing is unknown, leave it unresolved. A statement copied into notes is not a saved Board task or a message delivered to the owner; any later handoff uses its own supported route and verification.

Choose Leave or end-for-all from your role

Leave normally ends your own participation. Closing a tab can also remove a connection, but it is not the same evidence as a deliberate supported leave result. Neither proves the conference ended for other participants.

An authorised host can have a separate End session for all control. Do not use it just to close your own window while others are still working. Confirm the current participants, purpose and authority before a global end. For a solo rehearsal, verify that every connection belongs to you; matching display names alone are insufficient when identity remains uncertain.

Use the supported departure or end control and read its confirmation. A provider confirmation that the session ended is stronger evidence of provider termination than merely closing the browser. It still does not prove that every downstream history field has updated.

If service failure prevents a clean departure, retain the exact state and session identity for the responsible owner. Do not create another session to make the history look cleaner.

Match the same session in History

Return to Meet → History. Match the room, session start and internal session reference where shown. If repeated joins produced two records, identify the one you actually ended rather than choosing whichever row says Completed.

Inspect these values separately:

History item	How to interpret it
Status	The retained state reported for that specific session.
Start	A point for matching the correct occurrence, not the appointment's planned start by assumption.
Duration	A recorded measure; missing is unknown, not zero.
Participant join/leave	Connection history, which can be incomplete and needs identity context.
Recording information	Separate evidence about recording; Completed does not imply a recording exists.

A join time without a leave time does not prove the person remains connected. A missing duration should not be filled with a guessed value. If you calculate 15 minutes from observed start and end, label it a calculated interval rather than the native recorded duration.

A provider can report the session ended while Workroomly still shows In progress after reopening. Preserve both observations for the same session. Do not claim the conference is still running solely from the stale label, and do not delete or rewrite history to make the records agree.

Diagnose the stage that actually failed

Separate appointment planning, retained event, room access, prejoin, provider entry, media, departure and History. Failure at one stage does not erase every earlier success. A saved correct appointment can coexist with an audio failure. Provider termination can coexist with incomplete retained History.

For an unavailable service, state whether you reached prejoin or the actual conference. For an audio timeout, state which direction or mode failed and whether any listener confirmed sound. For a cancelled appointment still offering Join, preserve cancellation and stale listing without joining. For mismatched History, preserve the provider result and exact session fields.

Use normal permitted refresh after accounting for unsaved work. Avoid repeated joins, duplicate appointments, blind cancellation retries or security changes. Those actions can add side effects without resolving the original uncertainty.

A useful support handoff contains workroom, room, appointment/session identity, intended action, actual result, timestamps and the specific comparison that differs. Keep credentials and unnecessary participant details out of a broadly shared note.

Close the business result separately

After the meeting, compare the recorded decision with the actual material. If Label B needs one correction, inspect the returned corrected version before marking the action complete. If the note says an owner accepted work, retain the actual agreement rather than inferring it from attendance.

Send or store the outcome only in the authorised destination and audience. A meeting's successful end does not publish a document, place an order or assign tasks automatically. Check the resulting work records independently if follow-through is created.

Practise a complete closeout

Two session records exist in the same room. The earlier one is Completed. The later one reached the provider with camera off and microphone muted, failed listen-only audio, and was ended by the authorised host after verifying all connections were their own. Its History still says In progress with no duration.

The accurate conclusion concerns the later session: provider entry occurred, working audio was not established, the provider confirmed end, and matching History reconciliation remains open. The earlier Completed row does not resolve it. A separately recorded practice decision can still be useful, but correction and review actions remain pending until their outputs exist.

You have completed the course when you can identify the right room and session, explain appointment and access choices, enter with deliberate media settings, depart according to your role and distinguish provider, history and business outcomes. Do not replace an unresolved stage with a more reassuring label from another record.