Philippines staffing research
Measuring Whether Appointments Start Inside the Booked Time Window
An audit protocol for measuring appointment start-time adherence from join logs and booking records, including the unit of analysis, grace-window definitions, sampling rules, coding states, and the limits of small queue reviews.

Research question and evidence scope
Do appointments begin inside the time window the customer was promised? The scope is one appointment-setting queue during a defined review window, not an industry benchmark. The audit compares the booked start time, the scheduled duration, the first join event, and the time the responsible host opened the meeting. It asks a practical question: can the team show that the appointment started when the calendar said it would?
The review does not judge whether the meeting was productive, whether the customer was a good fit, or whether the host was persuasive. It does not measure close rates, revenue, or the quality of the sales conversation. Those outcomes depend on the offer, the buyer, and the closing team. Separating start-time adherence from meeting outcome keeps a scheduling problem from being blamed on the person who happened to run the call.
The unit is one booked appointment, not one participant and not one join event. A meeting with a host and three guests has one start time even though it has four join records. Keep the appointment identifier, the booked start and duration, the time zone, the host, the attendee list, the first host join, the first attendee join, and the meeting end together. That chain lets a reviewer tell a late host from an early customer and a rescheduled meeting from a late one.
Operating scenario and evidence
A common failure is a meeting that opens late because the host was finishing another call. The first attendee may join on time and wait in a lobby, which looks like an on-time appointment in a booking report but feels late to the customer. Another failure is a host who starts the conversation before the scheduled time and loses the attendee who arrived at the stated minute. Both cases show that the booked time and the actual experience can diverge.
A third failure is a time-zone error that moves the start by an hour or more. The calendar may show the correct local time while the join link opens at a different hour, or the reminder may use a different zone from the invite. The audit should record the time zone used in the booking and the zone shown in the join record before calculating lateness. Without that step, a correct meeting can be coded as late and a wrong one as punctual.
Method and review criteria
Collect a dated export of appointments in the review window. Include the appointment identifier, booked start, booked duration, time zone, host, attendee list, first host join, first attendee join, meeting end, and appointment status. Pull the join logs from the meeting platform used for each appointment and keep the platform's own time stamps with their offsets. Record the export time so a later edit does not silently change the comparison.
Use a census for a small queue and a documented random sample for a larger one. Oversample appointments at the start and end of a shift, appointments booked by a new setter, appointments with several attendees, and appointments where the booking note mentions a tight handoff. These groups carry the highest risk of a late start. Freeze the selection rule before looking at any join record.
Define the grace window before measuring anything. A team may count an appointment as on time when the host joins within two minutes of the booked start, while another may allow five. The number matters less than applying it consistently and stating it beside the result. Include the booked duration in the rule as well, because a meeting that starts late but still runs its full length is different from one that is cut short.
Authority and practical implications
Define four coding states before reviewing records. On time means the host and the first attendee were present inside the grace window. Late means the start fell outside the window. No show means no participant joined. Unverifiable means the join record is missing, the platform did not capture the event, or the time zone cannot be established. Code the appointment once, using the earliest host join and the earliest attendee join as evidence.
Look at the gap between the first attendee join and the host join as a separate measure. A customer who waits alone for six minutes has a different experience from one who joins after the host has already started. Report the wait time next to the on-time count so the team can see whether lateness is visible to the customer. This distinction also helps the host understand why a short delay still damages trust.
The Federal Trade Commission's Telemarketing Sales Rule sets record-keeping duties and calling conditions for covered telemarketing, including the National Do Not Call Registry. The Federal Communications Commission's guidance on the Telephone Consumer Protection Act addresses consent and revocation for automated calls and texts. The National Institute of Standards and Technology Privacy Framework offers a structure for limiting the personal data used in the review. These sources frame the control environment, not the punctuality of any single queue.
Limitations, conclusion, and sources
Implications should point to a specific repair. If late starts cluster around one host, the issue may be calendar overbooking or a back-to-back schedule with no buffer. If they cluster around one client, the appointment duration may be too short for the promised agenda. If they cluster around one platform, the join link or the time-zone handling may be wrong. Each pattern belongs to a different owner and a different fix.
A late start is not always a host failure. A customer may arrive late, a previous meeting may run over, or a platform may take time to admit guests. Separate host-caused lateness from customer-caused lateness and platform delay before assigning a repair. A team that only counts the appointment as late learns less than one that records who arrived when and what the customer saw.
The audit has limits. A join log may record the browser opening rather than the person being present, and a host may join early to test the link. A meeting may start on time but lose time to technical checks, and a customer may consider the appointment late even when the host joined within the grace window. Report these cases as uncertain rather than forcing them into a passing or failing bucket.
Protect the joined file as personal data. Names, email addresses, join times, and meeting notes can identify a person and reveal their schedule. Restrict access to the fields the review needs, store the working file in an approved location, and remove it when the review closes. Do not paste join logs or attendee lists into a shared report. Aggregate counts and role categories are enough for the owner discussion.
The result should name an owner for each pattern and a due date for the repair. A host schedule belongs to the team lead, a duration problem belongs to the client manager, and a time-zone or join-link problem belongs to the systems owner. Check the repair on the next sample before announcing an improvement. Set the review date for that sample when the repair is assigned.
Run the review after any change to the booking form, the calendar template, the meeting platform, or the host schedule. A monthly cadence suits a stable queue, while a weekly check may fit a campaign with frequent same-day bookings. Archive the export, the coding sheet, the definitions, and the repair log so another reviewer can reproduce the result. Keep the same unit and grace window for the next comparison.
An on-time start is not proof that the appointment was useful. It is evidence that the team began the conversation when the customer was told it would begin. State that limit plainly when presenting the result, and keep the punctuality finding separate from any later sales outcome. Sources: FTC guidance on complying with the Telemarketing Sales Rule, https://www.ftc.gov/business-guidance/resources/complying-telemarketing-sales-rule; FCC guidance on telemarketing and the Telephone Consumer Protection Act, https://www.fcc.gov/general/telemarketing-and-telephone-consumer-protection-act; NIST Privacy Framework, https://www.nist.gov/privacy-framework; U.S. Small Business Administration guidance on managing a business, https://www.sba.gov/business-guide/manage-your-business. All sources were checked on November 16, 2026 for general context, not as a local benchmark. Record the definition and sample size beside the result so the review can be repeated.
