What Counts as Onboarding Readiness Evidence?

Research question: Which checks distinguish a submitted onboarding request from a ready account, device, orientation plan, and first assignment?

Method: Build forty sanitized onboarding packets with seeded conditions such as an open access ticket, failed sign-in, missing equipment confirmation, conflicting start date, absent manager, and complete controls. Review half using request status alone and half using direct verification fields. Preserve all ambiguous cases in the results.

Unit and measures: The unit is one seeded readiness condition. Record detection by condition, false-ready decisions, review time, reviewer agreement, and the point at which the issue was escalated. Report account, equipment, document, schedule, and ownership results separately.

Scope and limitations: Synthetic packets cannot reproduce every HR system, jurisdiction, accommodation, security requirement, or individual onboarding need. Direct verification at one time does not prove future availability, employee eligibility, or the quality of training.

Use: The findings may help an operations owner design a readiness checklist. HR and system owners still decide employment status, document acceptance, access, exceptions, and start approval.

Sources consulted: NIST Cybersecurity Framework 2.0 (https://www.nist.gov/cyberframework); CISA Identity and Access Management guidance (https://www.cisa.gov/topics/cyber-threats-and-advisories/identity-and-access-management); U.S. Government Accountability Office, Standards for Internal Control in the Federal Government (https://www.gao.gov/products/gao-14-704g); Google Search Central, Article structured data (https://developers.google.com/search/docs/appearance/structured-data/article); Sitemaps protocol (https://www.sitemaps.org/protocol.html). These public sources provide general control and publishing concepts. They do not measure Outsourced Employment, establish employment or legal obligations, guarantee indexing, or certify any workflow.