A Meeting Attendance Report Counted Waiting-Room Time as Call Attendance: Correct the Session Boundary

A buyer can arrive on time, wait in a lobby, and never enter the call. If a report turns that waiting period into attendance, it answers the wrong question. It treats an attempted join as an admitted conversation.

Correct the session boundary before changing the disposition. Keep two facts: when the participant entered the lobby, and when the participant entered the call. The first records intent and timeliness. The second supports attended call time.

Microsoft Teams describes the lobby as a place where certain participants wait until an organizer, co-organizer, or presenter admits them. That makes lobby arrival useful operational evidence, but it does not establish that the person was in the meeting. Microsoft Learn

• Attempted attendance: a participant reached the lobby or another pre-admission state.
• Admitted attendance: a participant entered the meeting and has an in-room session.
• Attended duration: the sum of admitted in-room intervals, excluding lobby time.

Which events separate an attempted join from attended call time?

Use distinct event fields. Do not infer one event from another. A lobby-entry timestamp can establish that the buyer tried to join. An admission or in-room join timestamp starts attended call time. An in-room departure timestamp ends that interval.

If the system exports only a broad interval, retain the original export as source evidence and build a corrected interval beside it. Do not overwrite the raw value. The correction needs to be reviewable later.

Google Meet records a participant session for each unique join and leave from a device. Its participant-session resource includes a session ID, start time, and end time. A person who joins again receives another session ID, so a corrected duration should add admitted sessions rather than assume one continuous presence. Google for Developers

How should the corrected ledger handle a held call or no-show?

A held call needs two separate dispositions. The buyer may be recorded as timely for reaching the lobby. The attended-call outcome depends on whether the buyer was admitted and whether an in-room session occurred.

If the buyer waited in the lobby and was never admitted, do not mark the buyer as attended. Record the exact lobby interval, the lack of an admission event, and the meeting owner's disposition. That leaves room to investigate an organizer-side failure without turning waiting time into call time.

If the buyer entered the call after waiting, count only the admitted interval. If the seller never arrived, label that seller-side outcome separately. A single attendance label should not hide which party reached the lobby, who was admitted, or who remained in the call.

• Buyer reached lobby, never admitted: attempted attendance recorded; attended duration is zero.
• Buyer reached lobby, then entered call: preserve lobby arrival; attendance starts at admission.
• Buyer entered and left, then rejoined: sum the admitted sessions and retain the separate session records.
• No lobby or admitted event: do not infer a join from a calendar booking or a CRM status.

Which decisions can inflated waiting-room time corrupt?

Start with every decision that consumed the exported interval. An inflated duration can make a no-show look like partial attendance. It can make a very short admitted conversation look longer than it was. It can also attach an attribution or consent outcome to a session that never happened.

Treat the correction as a review trigger, not an automatic rewrite of every downstream field. The event record settles duration. A human or documented business rule may still be needed to settle disposition, follow-up eligibility, consent, and attribution.

Microsoft Graph describes an attendance record as containing attendance intervals and a total attendance duration in seconds. That model supports checking interval-level evidence rather than relying only on a total. Microsoft Learn

• No-show classification: distinguish no admission from an admitted but brief session.
• Partial attendance: base it on admitted time and the stated rule, not the lobby interval.
• Consent decisions: do not treat a lobby wait as proof that a live conversation occurred.
• Attribution: do not credit a meeting outcome to a call that never reached an admitted session.
• Follow-up reporting: revise every report or dashboard that used the exported interval.

How do you preserve a timely arrival without overstating attendance?

Use paired fields in the corrected report. One field states whether the buyer reached the lobby by the expected time. A separate field states whether the buyer entered the call, plus the admitted start, admitted end, and admitted duration.

This preserves useful operational evidence. A buyer who arrived at the lobby on time should not be treated the same as a buyer who never attempted to join. But the record should be equally clear that a lobby entry does not prove an in-room conversation.

Google Meet exposes participant-level earliest start and latest end timestamps, while its participant-session resource provides individual session start and end times. Use the session events when available for duration corrections, and retain participant-level values as supporting context. Google for Developers

• Timely lobby arrival: yes, no, or unknown.
• Admitted to call: yes, no, or unknown.
• Corrected admitted duration: calculated from in-room sessions only.
• Disposition owner: the person or system rule that approved the final classification.

What is the correction workflow for an inflated attendance interval?

Freeze the original export first. Capture the meeting ID, participant ID, exported start and end, exported duration, report IDs, and the date the discrepancy was found. Then retrieve the available lobby, admission, in-room join, departure, and rejoin events.

Calculate corrected duration from admitted sessions only. Keep each session in the ledger when a participant rejoined. If admission evidence is missing, mark the admitted duration as unknown rather than filling the gap with the lobby interval.

Review each downstream decision named in the ledger. Update only the reports and records that depended on the inflated interval. Record the reviewer, the correction time, the exact revised report, and the reason for any disposition change.

• Preserve the raw export.
• Capture lobby and admitted event evidence.
• Build admitted intervals from in-room sessions.
• Recalculate duration and review affected decisions.
• Publish a corrected report with the raw and corrected values side by side.