Start here
Five rules for a safe first handoff
- Create a controlling change record
- Sort dependencies into keep, move, cancel, and decide
- Test consequences hidden behind a small calendar change
- Run a dated readiness review and close the superseded plan
Task map
Split admin work from owner decisions
| Work lane | Philippines team | Company owner | Useful check |
|---|---|---|---|
| Create a controlling change record | Prepare and route the evidence for checkpoint 1. | Approve the decision described in “Create a controlling change record.” | Retain the source and destination result for checkpoint 1. |
| Sort dependencies into keep, move, cancel, and decide | Prepare and route the evidence for checkpoint 2. | Approve the decision described in “Sort dependencies into keep, move, cancel, and decide.” | Retain the source and destination result for checkpoint 2. |
| Test consequences hidden behind a small calendar change | Prepare and route the evidence for checkpoint 3. | Approve the decision described in “Test consequences hidden behind a small calendar change.” | Retain the source and destination result for checkpoint 3. |
| Run a dated readiness review and close the superseded plan | Prepare and route the evidence for checkpoint 4. | Approve the decision described in “Run a dated readiness review and close the superseded plan.” | Retain the source and destination result for checkpoint 4. |
Example pilot board
Use small numbers for the first review
Create a controlling change record
Begin with the accepted offer, candidate identity, original start date, employing entity, role, location, and work arrangement. Add the proposed date, source of the request, reason category, candidate agreement, employer approval, and time received. Do not replace the original offer artifact or make a calendar edit the only evidence. If the change affects other terms, route it back to the hiring, HR, compensation, or legal owner before sending revised language.
Use one reference for the date change across systems. Recruiter email, HRIS prehire record, payroll setup, background vendor, and manager checklist should link to the same approved event. If sources disagree, stop and show the conflict. A coordinator can prepare the impact list and approved candidate message but cannot decide whether screening, work authorization, benefit eligibility, notice obligations, or compensation terms permit the new date.
Sort dependencies into keep, move, cancel, and decide
Review background and credential checks, Form I-9 workflow, payroll creation, benefits enrollment timing, account provisioning, equipment shipping, workspace, orientation, training, travel, introductions, and first-week meetings. Mark each task keep, move, cancel, or owner decision. Equipment already shipped may remain with an approved custody plan; an account may stay disabled until the revised date; a training seat might need cancellation to release capacity.
Avoid bulk-shifting every deadline by the same number of days. Payroll cycles, plan rules, vendor expirations, holidays, and facility access windows behave differently. Record the new due date and basis for each change. If a vendor cannot move a task, identify whether it can be reused, must be repeated, or requires an exception. The candidate should receive only confirmed changes, not internal speculation about eligibility or operational delays.
Test consequences hidden behind a small calendar change
A one-week move can cross a pay-period boundary, benefits waiting point, month end, holiday shutdown, screening validity window, relocation booking, or manager absence. It can also leave a laptop at an unattended address or send credentials before employment begins. Use the specific scenario—equipment shipped and a payroll record already created—to check physical custody, data access, pay status, and communications separately. Do not activate access merely because the account exists.
Include the candidate in changes that affect their actions: revised arrival instructions, document appointments, shipment handling, orientation, and approved contacts. Keep internal risk decisions with company owners. If the candidate cannot meet the new plan, reopen the hiring decision rather than repeatedly moving administrative dates without a stable agreement. Preserve every issued version and withdraw obsolete invitations so the person does not receive contradictory instructions.
Run a dated readiness review and close the superseded plan
Before the revised start, ask each owner for ready, blocked, changed, or not-applicable status with evidence. Confirm payroll and HRIS dates, account activation, equipment location, workspace, manager coverage, orientation links, and outstanding candidate tasks. A checklist is useful only if it shows unresolved work and who owns it. Do not mark readiness from tickets created in advance when their destinations have not acknowledged the change.
After the start, reconcile attendance, system access, payroll inclusion, benefit handoff, equipment receipt, and completed orientation. Cancel obsolete tasks and retain the reason they were superseded. Review defects such as early activation, duplicate payroll records, expired checks, or conflicting messages. The reader leaves with a dependency-led date-change process that protects candidate clarity and prevents an apparently minor schedule edit from creating pay, access, or onboarding errors.
Copy-ready scripts
Make the stop points easy to say
Dependency owner"The approved start date changed from the recorded original to the revised date. Confirm whether your task will remain, move, cancel, or require an owner decision."
Candidate confirmation"We recorded the revised start date and these confirmed next steps. Contact the named hiring owner if any date or instruction does not match your understanding."
Launch path
A five-step HR outsourcing workflow
- 01
Create a controlling change record
Begin with the accepted offer, candidate identity, original start date, employing entity, role, location, and work arrangement.
- 02
Sort dependencies into keep, move, cancel, and decide
Review background and credential checks, Form I-9 workflow, payroll creation, benefits enrollment timing, account provisioning, equipment shipping, workspace, orientation, training, travel, introductions, and first-week meetings.
- 03
Test consequences hidden behind a small calendar change
A one-week move can cross a pay-period boundary, benefits waiting point, month end, holiday shutdown, screening validity window, relocation booking, or manager absence.
- 04
Run a dated readiness review and close the superseded plan
Before the revised start, ask each owner for ready, blocked, changed, or not-applicable status with evidence.
Buyer FAQ
HR outsourcing questions
Should every onboarding task move by the same number of days?
No. Each dependency has its own cutoff, validity period, and owner. Classify and reschedule tasks individually.
Can accounts remain active while the start is delayed?
Only under an approved security plan. Existing accounts should normally remain disabled until the authorized activation event.
Sources
Source notes
- USCIS Form I-9 CentralOfficial employer resources for Form I-9 timing and responsibilities.
- NIST Privacy FrameworkOfficial framework for accountable, purpose-based handling of personal data.