Attendance evidence is complete only when the booking, the attendee role, the observed outcome, and any linked reschedule share one case key and one observation time.
Question and scope
This brief asks how many booked meetings in the window have a complete attendance record. Completeness means an outcome observed at the time, not a status inferred later from a recording or a note.
It does not measure whether the meeting was valuable, whether the right decision was reached, or whether the rep performed well.
Unit and fields
The unit is one booked meeting. Required fields are the booking id, the attendee role, the scheduled time with time zone, the observed outcome, the observation time, and any linked reschedule id.
Decide whether a meeting with two internal attendees is one unit or several, and apply the rule consistently. Record the decision in the data dictionary with the date it took effect.
Evidence standard
An outcome recorded the next week is weaker evidence than one recorded after the call. Keep the observation time so the reader can judge the gap between the meeting and the record.
Unclear is a legitimate value. A binary attended or no-show field forces a guess when the calendar, the recording, and the rep note disagree.
Collection and sample
Pull consecutive bookings and include at least one reschedule, one cancellation, and one meeting with an attendee whose role is unknown. These cases test the completeness definition.
Record the calendar export date, the filter, and the row count. If the export omits cancelled events, say so, because the missing rows change the denominator.
Limits and reporting
Calendar data is maintained for scheduling, not for measurement. Fields may be reused, time zones may be stored inconsistently, and reschedules may create new events without linking the old one.
Report completeness by field as well as overall, so a single missing field does not hide behind a high total. The cited sources frame scheduling and recordkeeping context; they do not provide a result for this calendar.
Sources
Apply the operating question
Use the finding to define one source, output, review owner, and exception path inside a real workflow.
Discuss the workflow