Which Onboarding Dependencies Should Block a Start-Ready Status?

Research question: whether onboarding coordination can report readiness accurately when prerequisites depend on multiple owners and systems? 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 welcome email, signed form, equipment shipment, account request, and manager confirmation describe different states. Buyers need a model that prevents one visible success from masking a missing prerequisite or expired approval.

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 new hire, one planned start, and one versioned readiness checklist with named dependencies. 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 ninety-six fictional journeys covering changed start dates, conditional approvals, incomplete documents, failed checks, equipment delay, inactive accounts, manager absence, duplicates, vendor receipt without delivery, expired evidence, withdrawal, and scope changes. 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: hire token, planned start and timezone, prerequisite, rule version, dependency, source owner, request time, evidence state, expiry, access class, acknowledgment, exception, waiver authority, readiness decision, actual transition, and closure evidence. 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: correct classification of not requested, requested, received, verified, conditional, expired, waived, failed, blocked, ready, or cannot determine without collapsing dependencies. 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: Requested is not approved; shipped is not delivered; provisioned is not usable; signed is not necessarily complete; and one waived item does not waive its dependents. A percentage-complete dashboard can obscure a mandatory blocker.

Decision boundary: The coordinator may maintain the approved checklist, request evidence, monitor acknowledgments, test observable access, and escalate blockers. HR, hiring, IT, security, legal, payroll, and authorized owners define prerequisites, approve exceptions, and release access.

Controlled comparison: Compare a flat completion percentage with a dependency graph distinguishing required, conditional, waived, expired, failed, and unknown states 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 hires and tokenized identifiers. Keep identity, health, financial, background, and contract documents out of general trackers. Review notification and export exposure. 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 prerequisite accuracy, false-ready rate, blocked-path detection, acknowledgment latency, expired evidence, duplicate requests, disclosure, 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.

Model prerequisites as a directed dependency chain instead of a flat checklist. Seed an account that exists before its access approval, equipment delivered to the wrong recipient, a signed document missing an approved field, and a start-date change that makes earlier evidence stale. For each case, trace which downstream tasks may proceed, which must pause, and who has authority to waive a requirement. Require observable acknowledgment from the receiving system or owner; a submitted request is not a completed dependency. Recalculate readiness after each timed event and preserve the prior state so reviewers can identify false-ready intervals. The output should explain the single blocking path, any conditional branches, expiry or waiver evidence, and the authorized release decision without exposing restricted onboarding documents in the general tracker.

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 protocol does not decide whether employment may begin, whether documents are legally sufficient, or what access a person should receive. 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 readiness dependency record linking each prerequisite to its rule, evidence, owner, expiry, exception path, dependent tasks, and authorized decision. 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.