What Should a Candidate Rescheduling Record Prove?

Research question: whether a recruiting coordinator can manage interview changes consistently without inferring candidate commitment, disclosing private reasons, or changing selection criteria? This protocol tests a narrow administrative evidence model for Philippines staffing operations. It is not legal advice, an employment decision, a security certification, or a promise that the same workflow fits every organization.

Why the question matters: Interview rescheduling is administrative until a delay, interviewer absence, timezone error, or accommodation-related request is treated as evidence about a candidate. A buyer needs proof that comparable options were offered under a declared rule and that private reasons and hiring judgments reached only the right owner.

Evidence frame: the Philippine Data Privacy Act implementing rules describe transparency, legitimate purpose, proportionality, accountability, security, access, retention, and responsibilities around outsourced processing. DOLE advisories provide current Philippine labor context. NIST CSF 2.0 and SP 800-53 supply general governance, identity, access, audit, change, and risk-control language. They are inputs to a buyer’s design, not a substitute for facts, contracts, applicable law, or accountable professional judgment.

Unit of analysis: one request or operational need to change one candidate interview event. Fixing the unit before testing prevents a favorable batch total from hiding one unresolved person, instruction, record, or downstream handoff. Every case receives a stable fictional reference and every conclusion must point to an observable source event.

Test set: create one hundred fictional changes across candidate requests, interviewer conflicts, expired links, timezone shifts, connection failures, public holidays, repeated changes, short-notice cancellations, accessibility requests, recruiter error, no response, alternative formats, panel substitutions, and roles with different service windows. Use invented people, organizations, amounts, accounts, documents, and identifiers only. A study administrator keeps the seeded answer key separate until both reviewers finish their first pass.

Minimum fields: candidate reference, requisition, stage, original event and timezone, change initiator, received time, approved option set, channel, response events, private-reason indicator, accessibility route, interviewer substitution, exception owner, final event, source links, and hiring-owner disposition. Define the purpose and allowed values for every field. Blank, unknown, not applicable, not yet received, restricted, and cannot determine remain distinct states. Reviewers may not turn absence into a convenient answer.

Before review, the accountable business owner freezes the population, source hierarchy, state definitions, permitted actions, access roles, response windows, serious-error classes, and stop conditions. A later policy change creates a new version and a targeted rerun; it never silently rewrites the original observation.

Primary measure: accurate use of the approved scheduling rule, correct timezone representation, preservation of equal option evidence, safe routing of restricted reasons, and separation of scheduling state from candidate evaluation. Secondary measures include unequal options, false no-show, unnecessary disclosure, and unsupported inference. Reviewers must cite the exact evidence used for each state. A confident guess counts as an error even when it happens to match the seeded answer.

Error model: A request to reschedule does not prove disinterest. Silence in one channel does not prove withdrawal when the declared contact process is incomplete. A calendar acceptance does not prove attendance, and a private reason need not be copied into interview notes to explain an administrative state.

Decision boundary: The coordinator may offer approved windows, record responses, update invitations, test links, and route exceptions. The hiring owner defines scheduling policy and decides selection consequences. Authorized HR or accessibility owners handle accommodation decisions; interviewers own their availability and feedback.

Controlled comparison: Compare free-form negotiation with a versioned option-set workflow. Compare reason narratives in the applicant tracker with a restricted indicator and authorized referral. Randomize equivalent cases across reviewers to reveal inconsistent handling. Give both workflows the same underlying cases in randomized order. Compare correctness, unnecessary access, unresolved work, serious errors, and review time rather than relying on completion speed alone.

Privacy and security treatment: Use fictional candidates and neutral reason codes. Do not collect medical, family, religious, or other sensitive narratives merely to justify a schedule change. Review calendar guests, meeting titles, notification previews, recordings, and exports for unintended disclosure. Record who can view, change, export, and delete each artifact. Test linked systems and notification paths because a restricted main record can still leak through email, calendars, downloads, integrations, or backups.

Include positive controls that should proceed, negative controls that should stop, and ambiguous controls that should reach an authorized owner. A workflow that never stops is not controlled; one that stops every case is not operationally useful. Keep the expected route and reason in the hidden answer key.

Analysis plan: Report correct option use, timezone accuracy, time to resolution, exception routing, false no-show classification, and disclosure events by initiator and stage. Audit for systematic differences in options while avoiding demographic inference from the synthetic data. Two reviewers independently classify an overlapping sample. Preserve disagreements and resolve them through the named owner. Do not average classifications or let the first entry become authoritative merely because it appeared first.

Set acceptance thresholds before opening the answer key. Define the minimum routing accuracy, maximum unresolved age, maximum tolerated disclosure, and failures that stop the pilot. Report counts with denominators and list exclusions with reasons. Faster handling cannot compensate for an unauthorized decision, sensitive-data exposure, or false closure.

Run a repeatability check with a second reviewer who receives the written rules and clean cases but no coaching. Low agreement indicates unclear rules, missing evidence, or inconsistent source access. Version the clarification and rerun affected cases; do not label every disagreement as an individual training problem.

Add a temporal test after the static review. Replay selected cases when a cutoff passes, an approver changes, a source is corrected, or a downstream acknowledgment arrives late. The expected state should change only when the declared transition evidence exists. Record who observed the event, which rule version applied, and whether notifications or dependent systems updated. This catches designs that look accurate in a snapshot but cannot preserve history or distinguish an overdue item from a superseded one.

Assess operational recovery as well as normal processing. Remove one required source, delay one owner, introduce one duplicate, and make one integration temporarily unavailable. The coordinator should preserve the last known state, state what cannot be determined, avoid reconstructing missing facts from memory, and route the case through the approved contingency path. Measure whether work resumes from preserved evidence without double action, unauthorized disclosure, or silent closure when the source returns.

Ask a prospective provider for artifacts that match the operating claim: a sanitized workflow demonstration, blank register, role-permission view, change history, exception map, and sample audit export. Each artifact has its own date and scope. Marketing statements, policy documents, and successful demonstrations are point-in-time evidence, not proof of continuous operation.

Separate observed fact, rule-based classification, accountable-owner decision, and researcher inference in the final table. Preserve missing events, integration delays, inaccessible sources, ambiguous definitions, and unavailable owners as explicit uncertainty. “Cannot determine” is a useful result when the source does not support a stronger statement.

Limitations: The study cannot determine discrimination, lawful accommodation, candidate merit, or the correct consequence of repeated changes. It omits many accessibility, connectivity, emergency, cultural, and cross-border scheduling circumstances. Begin any live pilot with a small approved queue, named reviewers, least-privilege access, monitored exceptions, and a stop rule for unexpected sensitive data or work outside the written lane.

Decision-grade output: a rescheduling event record showing the original event, approved options, timezone, communications, restricted-data boundary, operational outcome, and any hiring-owner decision without converting inconvenience into a candidate judgment. A buyer can use the artifact to compare operating discipline, but it does not guarantee outcomes or transfer accountability from the responsible organization.

Sources checked September 24, 2026: National Privacy Commission, Implementing Rules and Regulations of the Data Privacy Act of 2012 (https://privacy.gov.ph/implementing-rules-regulations-data-privacy-act-2012/); National Privacy Commission, The Data Privacy Act and Its IRR (https://privacy.gov.ph/the-data-privacy-act-and-its-irr/); Department of Labor and Employment Bureau of Working Conditions, Labor Advisories (https://bwc.dole.gov.ph/issuances/labor-advisories/); National Institute of Standards and Technology, Cybersecurity Framework 2.0 (https://www.nist.gov/cyberframework); National Institute of Standards and Technology, Security and Privacy Controls for Information Systems and Organizations, SP 800-53 Revision 5 (https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final). These primary government sources frame privacy, labor context, governance, access, audit, and risk questions. They do not decide a specific employment matter, certify a provider, or replace advice from authorized legal, HR, payroll, security, benefits, or finance owners.