Philippines staffing research · Updated September 28, 2026

Do candidate interview changes preserve a fair and usable scheduling record?

An event-sequence study of interview invitations, availability, accommodations, changes, notices, attendance, and closure.

Decision in scope. This protocol is for a buyer considering recruitment coordination. It tests whether interview rescheduling can be delegated without delegating candidate evaluation, accommodation decisions, hiring priorities, employment terms, or exceptions to recruiting policy. It does not publish an industry benchmark, promise a result, or score individual workers. The output is a documented account of one buyer's queue and the conditions that would make a limited handoff reviewable.

Research question. For interviews changed after the first confirmed invitation, how often can reviewers reconstruct the reason, authorized schedule, required notices, accommodation handling, and final attendance state? Freeze that question before the first record is coded. If the team changes the question after seeing the data, keep the new analysis separate and label it exploratory. That discipline matters because a convenient metric can answer a different question from the one that drove the staffing decision.

Sources and their role. This protocol uses primary guidance checked on September 28, 2026. The 2025 GAO Green Book informs authorization, documentation, control design, monitoring, and response to change. NIST SP 800-53 supplies audit, accountability, access-control, and privacy-control concepts. FTC guidance supports collecting only needed data, limiting retention, and controlling access. The Philippine Data Privacy Act supplies the local privacy context. AAPOR's disclosure elements inform the methods record. These sources shape the protocol. They do not supply observations or outcomes for the buyer.

Population and window. Include every interview first confirmed and then changed during sixteen consecutive recruiting weeks, including candidate requests, interviewer conflicts, no-shows, cancellations, panel changes, and reopened requisitions. Register the start and end dates, working timezone, eligible channels, source systems, cutoff rule, and terminal events before export. Keep a screening log that counts included units, test records, out-of-window events, missing identifiers, duplicates, and records withheld because the reviewer lacked permission.

Unit of analysis. Count one candidate-stage interview under a stable scheduling identifier, with each proposed and confirmed time preserved as an event rather than counted as a separate interview. Messages, reminders, edits, exports, system checks, and status changes are events attached to that unit. They are not extra units. This prevents busy cases from inflating the denominator and keeps the result tied to completed or unresolved work rather than activity volume.

Field dictionary. Collect only what the question requires: schedule ID, candidate and requisition pseudonyms, stage, invited panel, timezone, proposed times, confirmed time, change requester, reason class, accommodation flag, authorized decision route, notices, acknowledgements, attendance, disposition event, deletion rule, and terminal state. Define each field, allowed values, controlling source, timestamp meaning, timezone, change behavior, and missing-value code. Keep direct identifiers in the approved operating system. Use stable pseudonymous identifiers in the analysis file whenever the review does not need a person's identity.

Controlling evidence. Treat the approved interview plan, attributable availability responses, confirmed calendar event, accommodation route, authorized change record, and attendance evidence; a recruiter summary cannot replace the candidate communication. If two permitted sources disagree, preserve both values, effective times, and the conflict. Apply only the source-precedence rule approved by the buyer. An analyst must not choose the more convenient source simply because it makes the record look complete.

Outcome coding. Use these registered classes: changed and acknowledged, candidate confirmation missing, interviewer confirmation missing, timezone conflict, accommodation route active, panel changed, late cancellation, no-show disputed, rescheduled again, requisition paused, closed, and unresolved. The codebook should state which conditions can coexist, which class takes priority, and what evidence moves a unit to a terminal state. Keep an unresolved class. Forced success and failure labels hide uncertainty and make later correction harder.

Measures. Show counts and denominators before percentages. The primary output is the distribution of registered outcome classes. Secondary measures are changed-interview counts, requester distribution, notice coverage, acknowledgement coverage, time to reconfirm, timezone conflicts, repeated changes, attendance states, withdrawals, and unresolved age. For elapsed time, report medians and selected percentiles rather than a mean alone. Put missingness, exclusions, and censored units beside every affected measure.

Event order. Reconstruct creation, first action, each material transition, owner request, response, correction, and terminal event in the site's UTC timezone while retaining original offsets. Write a deterministic rule for events with the same timestamp. Separate active preparation from owner wait, scheduled delay, system delay, and unknown time when the records allow it.

Review quality. A second reviewer reconstructs every accommodation-flagged, disputed no-show, and repeatedly changed interview plus a random sample of acknowledged changes. Both reviewers use the same frozen codebook. Record disagreements before discussion, then publish agreement counts for the reviewed sample and list any rule changed during reconciliation. A material rule change requires recoding the affected population or separating the later analysis.

Worked classification. A candidate accepts a time shown in one timezone, but a later calendar update shifts the displayed hour. Preserve both invitations and route the conflict promptly; the coordinator cannot label the candidate a no-show from the later event alone. The example tests whether the rule is understandable. It is not an observed result and should never appear in the findings table. Actual records may show a different pattern, and the reviewer should preserve that result even when it makes the proposed handoff less attractive.

Operating boundary. A Philippines-based specialist may collect permitted records, link identifiers, apply the codebook, maintain the screening log, flag conflicts, and prepare an exception packet. Candidate assessment, hiring priority, accommodation eligibility, employment-law interpretation, rejection, requisition changes, panel authority, offer timing, and exceptions remain with authorized owners. A deadline, absent owner, or familiar precedent does not transfer that authority to the coordinator.

Privacy and security. Use named accounts, least privilege, approved export methods, encrypted storage and transfer, and a written retention period. Do not copy an unrestricted inbox or an entire personnel, customer, or transaction history when a bounded event table answers the question. Delete working copies under the buyer's approved rule and report access or data-quality incidents through its existing route.

Bias and alternatives. Treat the findings as a description of the registered queue. Differences may come from work mix, source quality, system design, policy changes, shift coverage, owner availability, or missing events. They do not by themselves show that a coordinator, provider, or location caused the outcome. Use only preregistered subgroups, show small groups as counts, and suppress cells when privacy or instability requires it.

Limitations. Calendar systems normalize timezones differently, candidate replies may arrive off-platform, interviewers can change without notice, privacy limits the accommodation record, and attendance does not prove a fair process. One buyer and one operating window do not establish causality or external validity. The records cannot prove what a person knew or why an event occurred. Document any change in system, policy, staffing, volume, or access that overlaps the study so a reader can judge comparability.

Decision rule. Before collection, state the evidence needed to start a narrow pilot, repair records and measure again, keep the queue internal, or request specialist review. Include evidence coverage, unresolved risk, owner capacity, and reversibility. Speed is not enough. A quick queue with missing authority or source records is not ready to hand off.

Pilot. If the evidence supports a test, open one bounded queue with a named internal owner and backup. Record permitted actions, stop conditions, review sample, escalation time, and rollback path. Compare the pilot with the registered baseline using the same units and classes. Version any scope change instead of folding new tasks into the original measure.

Conclusion for this niche. Staff interview rescheduling only when availability, timezone, authorized changes, accommodation routing, notices, acknowledgements, and attendance can be reconstructed without judging the candidate. OutsourcedCompany.com readers are choosing which company function to hand off first. The process must become observable before the staffing decision: sources stay attributable, exceptions stay visible, and consequential decisions stay with the buyer's named owners.

Schedule-specific event model. Store proposed, accepted, changed, cancelled, and attended events with the original timestamp, timezone label, UTC equivalent, sender, recipient set, and calendar identifier. Do not overwrite the first confirmation when a later invitation arrives. Define acknowledgement as an attributable candidate response or approved system event, not email delivery. Record interviewer acknowledgement independently. When a panel member changes, retain the role in the panel and the authority for the substitution without exposing unnecessary personal notes. These rules make it possible to distinguish a valid reschedule from a calendar mutation that only one party saw.

Fairness review. Group operational results by registered change requester, stage, notice band, timezone relationship, and accommodation-route presence, while suppressing small cells. Do not compare selection or hiring outcomes as evidence that scheduling caused them. Instead examine repeated changes, acknowledgement gaps, disputed no-shows, and withdrawals recorded after a change. An accommodation flag should reveal only that the protected route was used and whether required scheduling actions occurred; the analysis file should not contain diagnosis or confidential rationale. Any disparity is a review signal for the authorized recruiting owner, not a judgment about candidates or interviewers.

Service rule. Set a response clock for ordinary changes and a separate urgent path for changes near the interview start. The clock pauses only under named states, such as waiting for candidate availability or an authorized accommodation decision. Test communications across daylight-saving transitions and calendar clients before relying on automatic timezone rendering. A coordinator can offer times within an approved availability envelope, but must return conflicts involving required panel composition, candidate hardship, accommodation, requisition pause, or policy exception. The buyer should staff this queue only if those boundaries and a backup owner make timely, respectful recovery possible.