Can Candidate Consent Evidence Survive a Sourcing Handoff?

Research question: how a sourcing coordinator can preserve consent and notice evidence across a candidate handoff without making legal conclusions or expanding use? 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: A profile can arrive from an application, referral, job board, event, agency, or prior pipeline. The buyer needs evidence of the actual source and declared use rather than a generic consent flag detached from notice, date, channel, and withdrawal state.

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 fictional candidate record acquired through one named source for one declared requisition or talent-pool purpose. 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 records spanning applications, referrals, public profiles, agency transfers, duplicates, stale notices, withdrawals, changed purposes, inaccessible sources, restricted attachments, cross-border tools, and conflicting consent fields. 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 token, source, acquisition time, notice title and version, purpose, contact channel, requisition, evidence link, transfer event, access class, retention state, withdrawal, suppression, exception owner, recruiter decision, and deletion acknowledgment. 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 preservation and routing of source, notice, purpose, contact permission, withdrawal, suppression, retention review, restricted, or cannot determine states. 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 public profile is not blanket permission for every use. A checked box without its notice version is weak evidence. Copying a resume does not carry context automatically, and deleting one duplicate does not prove suppression across every channel.

Decision boundary: The coordinator may preserve source facts, apply approved contact and suppression rules, limit routine fields, route ambiguity, and record acknowledgments. Privacy, legal, recruiting, and business owners decide lawful basis, notice, purpose, retention, disclosure, and selection.

Controlled comparison: Compare one reusable consent flag with a source-linked event record; test whether withdrawal reaches duplicates, outreach lists, agency copies, exports, and scheduled messages 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. Restrict resumes and sensitive data. Inspect exports, messages, notifications, logs, backups, and downstream tools. 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 source completeness, notice-version coverage, transfer lineage, withdrawal propagation, duplicate suppression, restricted-data exposure, and reviewer agreement. 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.

Test permission lineage across every practical copy of a candidate record. Seed one withdrawal after a recruiter export, one referral with no captured notice version, one job-board profile reused for a different requisition, and one duplicate held by an agency and an internal list. Review whether suppression reaches scheduled outreach, shared spreadsheets, email sequences, archived talent pools, and downstream integrations without erasing the historical evidence needed to explain the action. The coordinator should identify the source and affected systems, but privacy and recruiting owners decide the permitted response and retention treatment. Score a case as complete only when the declared purpose, notice context, transfer history, restriction, owner decision, and downstream acknowledgment remain connected. This exposes the difference between changing a central flag and controlling actual operational use.

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 does not determine lawful basis, evaluate discrimination, or decide candidate suitability. Channels, platform terms, jurisdictions, and recruitment relationships vary. 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 candidate source-and-permission record preserving notice context, purpose, transfer history, withdrawal and suppression evidence, boundaries, and accountable owner. 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 25, 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.