Interview-accommodation routing in Philippines recruitment coordination

Research question and buyer decision. When a candidate communicates a need that may affect interview scheduling or format, does the recruitment workflow route the minimum necessary information to an authorized owner while preserving a usable interview plan? The study is deliberately about coordination evidence, not about deciding whether a person has a disability, what law requires, or whether a requested adjustment is reasonable. Those judgments belong to the buyer’s people and legal owners. A Philippines coordinator can still add substantial value by recognizing trigger language under a neutral rule, protecting sensitive details, recording deadlines, and keeping logistics moving. The buyer uses the evidence to determine whether the lane is safely defined before coordinators receive broader candidate-system access or authority.

Eligible population and unit. Freeze interview-stage candidate communications during a defined requisition window, including scheduler forms, email, applicant-system notes, recruiter handoffs, and approved phone summaries. One accommodation-related coordination episode is the unit, spanning first observable request through logistics confirmation or documented closure. Retain ambiguous requests, ordinary availability preferences, language or access needs, caregiver timing, religious scheduling, disability-related disclosures, pregnancy-related needs, technology limitations, and requests later withdrawn. Classification should be performed by authorized reviewers, not used to infer protected status. Record requisition, stage, channel, receipt time and timezone, coordinator observation time, routing destination, acknowledgement, interview deadline, and final logistical state. Exclusions require a reason and count.

Data minimization model. The operating record should contain only what the coordinator needs: candidate reference, interview stage, requested logistical change in the candidate’s own bounded terms, preferred contact method, relevant date, whether sensitive detail is stored elsewhere, authorized owner, handoff time, safe holding message, and confirmed arrangement. Medical documents, diagnoses, speculation, and unrelated personal history should not be copied into general scheduling notes. Separate restricted accommodation records from interviewer scorecards and ordinary recruiting views. Use role-based access and retention rules supplied by the buyer. If a candidate volunteers extra detail, the workflow should preserve the request without spreading that detail. Minimization is not deletion of the fact that a handoff occurred; reviewers still need an auditable event and disposition.

Study method. Select episodes before reviewing hiring outcomes. Stratify by stage, channel, request type, urgency, source visibility, requisition group, and whether the request arrived directly or through a recruiter. Trace each episode forward to owner acknowledgement and logistics, then sample scheduled interviews backward to detect relevant requests that never entered the protected route. Two trained reviewers should independently score a de-identified subset against a frozen rubric: trigger recognized, unnecessary detail avoided, correct owner used, deadline visible, candidate response sent, interviewer disclosure bounded, arrangement confirmed, and hiring evaluation kept separate. Preserve original disagreement. Do not ask coordinators or research reviewers to determine eligibility. Measure process handling without linking it to selection outcomes unless a separately authorized fairness study is designed.

Measures. Publish counts and denominators for eligible episodes, timely routed cases under the buyer’s service target, acknowledged handoffs, excess-detail exposure, missing ownership, interview disruption, candidate follow-up, and unresolved logistics. Report medians and ranges for routing and confirmation, distinguishing coordinator work from owner waiting and candidate waiting. Show results by channel because a web form may route differently from free-text email. A fast response is not automatically good if it exposes sensitive information; a longer interval may reflect candidate preference or owner review. Reviewer agreement indicates whether the workflow is operationally clear. It does not show whether an accommodation was legally sufficient or whether a hiring decision was nondiscriminatory.

Responsibility boundary. The coordinator may recognize a request using approved non-diagnostic cues, acknowledge receipt with neutral language, ask only approved logistical questions, route to the designated people owner, reserve time, update permitted scheduling fields, and confirm the authorized arrangement. The coordinator should not seek proof, assess disability, deny a request, negotiate legal obligations, tell interviewers medical details, change evaluation criteria, or record subjective reactions. Hiring managers should receive only the logistics needed to conduct the interview unless the authorized owner determines otherwise. The buyer must name a primary and backup decision owner, define an urgent path, and provide a safe response when the interview date arrives before a decision.

Illustrative workflow. A candidate writes, “I need breaks during a two-hour video panel and may need captions.” The coordinator records the requested logistics, sends the approved acknowledgement, flags the interview date, and routes the restricted request to the people owner. The general calendar can say that the agenda and platform settings are being confirmed; it need not contain a reason. The people owner determines the arrangement and what interviewers need to know. The coordinator confirms timing, caption setup, contact method, and contingency plan, then records completion. If the platform cannot support the arrangement, the issue returns to the owner rather than being reframed as candidate unavailability. This example explains a method and is not legal advice or a claim about company practice.

Common failure modes and repair. Free-text requests can remain in a recruiter’s inbox; applicant-system notes can be visible too broadly; coordinators may confuse availability with accommodation; interviewers may receive unnecessary detail; and urgent requests may wait behind ordinary tickets. Another failure is overcorrection: removing all evidence can make it impossible to prove routing occurred. Repairs include a clearly labeled contact path, restricted case type, minimal structured fields, automatic deadline visibility, backup ownership, approved acknowledgements, access reviews, and a post-confirmation check. Train with varied scenarios but assess the real workflow through de-identified event evidence. When a shared system causes exposure, fix permissions and defaults before treating the event solely as an individual mistake.

Limitations and uncertainty. Employment and privacy duties vary by jurisdiction and circumstance. A coordination audit cannot determine legal coverage, reasonableness, essential job functions, discrimination, or the adequacy of an interactive process. Candidates may make requests verbally or to people outside the observed systems. De-identification may hide context needed to understand a handoff, while reviewing full records creates privacy risk. Small populations and rare request types limit rate comparisons. Interview rescheduling may have unrelated causes. A completed logistical arrangement does not prove the candidate experienced an equitable process. Reports must disclose unavailable channels, missing events, rubric changes, access constraints, and the boundary between observed records and inference.

Decision rule and conclusion. The buyer can delegate coordination when there is one visible request path, minimal-data schema, restricted record, named owner and backup, deadline rule, neutral acknowledgement, confirmed logistics checklist, and clear prohibition on diagnostic or legal decisions. Expansion should depend on consistent performance across free-text and urgent cases, not only structured forms. Any sensitive-data exposure, unowned urgent request, or coordinator-made eligibility decision should trigger a pause and owner review. The result buyers want is not a promise that every case is easy; it is a workflow that protects dignity, keeps uncertainty visible, and connects the candidate with the person authorized to decide. That is a specific, testable recruitment-support lane.

Primary and authoritative sources. “Enforcement Guidance on Reasonable Accommodation and Undue Hardship under the ADA,” U.S. Equal Employment Opportunity Commission, eeoc.gov “Job Applicants and the ADA,” U.S. Equal Employment Opportunity Commission, eeoc.gov NIST Privacy Framework, National Institute of Standards and Technology, nist.gov The EEOC sources provide United States federal guidance; buyers need qualified advice for their facts and jurisdictions. Checked September 28, 2026.