Central finding: An onboarding completeness audit should test the required document, the signature or verification, the review owner, and the first-day dependency rather than only counting uploaded files [Source: U.S. Department of Labor workplace guidance].
Select the sample and the standard
Include one smooth onboarding, one late packet, and one packet with an exception. Use the same required-document list for each file [Source: U.S. Department of Labor workplace guidance].
Record the start date and the date the packet was checked. A packet checked after the first day does not prove first-day readiness.
Test evidence, not file count
For each required item, record whether the document is present, signed or verified, reviewed, and linked to the access or payroll task [Source: SHRM onboarding guidance].
An uploaded identity document without a reviewer is not complete. A signed policy acknowledgment for an old version is not complete.
Record the dependency and the owner
For each missing or incomplete item, record the dependency, the owner, and the first-day consequence. A missing access approval is different from a missing welcome form [Source: NIST Cybersecurity Framework].
Do not score the packet complete because the manager said it was fine. The evidence should show the item and the review.
Report with limits
Report the number of packets reviewed, the missing items by type, and the number that affected first-day access. State the sample and the roles [Source: SHRM onboarding guidance].
A small sample can be dominated by one unusual role. The result is local evidence, not an industry completion rate.
Method note
We reviewed the public sources listed below and translated recurring operational ideas into questions for workflow ownership, source evidence, review, and escalation. This is operational guidance, not legal advice.