Start here
Five rules for a safe first handoff
- Require an approved source for every date change.
- Show old date, proposed date, and confirmed date separately.
- List each dependent owner before sending updates.
- Keep candidate and manager messages approved.
- Close only after downstream records acknowledge the change.
Task map
Split admin work from owner decisions
| Work lane | Philippines team | Company owner | Useful check |
|---|---|---|---|
| Request capture | Record the request, source, requested date, and affected hire. | Approve or reject the change. | Decision owner is named |
| Dependency scan | List interviews, onboarding, equipment, payroll, and access dependencies. | Choose which dependencies must move. | Each dependency has a responsible owner |
| Communication | Prepare approved notices and track delivery. | Approve wording and recipient list. | Sent version matches approval |
| Reconciliation | Compare calendars and records after the change. | Confirm the new date is authoritative. | Old date is not active in a downstream system |
Example pilot board
Use small numbers for the first review
Keep proposed and confirmed dates apart
A manager message may suggest a change before the employer approves it. Use separate fields for requested date, approved date, and date entered into a system. This prevents a tentative conversation from moving onboarding work prematurely.
The coordinator can surface a mismatch, but should not decide that a reply, calendar event, or system field counts as approval. The named owner makes the date authoritative.
Map the dependency chain
A start date can affect welcome messages, equipment requests, access tickets, orientation sessions, payroll inputs, and the manager’s first-week plan. List those dependencies from the approved onboarding record rather than relying on memory.
Give each dependency an owner and a due point. If one cannot move, record the exception for the manager instead of quietly leaving the old commitment in place.
Send one approved explanation
Candidates and managers should not receive conflicting dates from separate calendars. Prepare the approved message once, record who approved it, and track delivery. The coordinator may answer where to find the updated schedule, but should not explain an employment decision without approved wording.
If the change raises a pay, visa, leave, or contract question, route it to the qualified owner. The date tracker is not an advice channel.
Reconcile after the update
Compare the new date against the applicant record, onboarding checklist, calendar, equipment ticket, and access request. Mark each as confirmed, waiting, or exception. A saved field without an acknowledgement is not proof that the dependency moved.
Keep the previous date in the audit history when the system supports it. That history explains why reminders or notices changed and helps the owner correct duplicate work.
Copy-ready scripts
Make the stop points easy to say
Approval request"The requested start date is [old] to [new]. These dependencies are affected: [list]. Please confirm the authoritative date and approved message."
Reconciliation note"Confirmed date: [date]. Updated: [records]. Waiting: [items]. Exception owner: [name]."
Use a change test before launch
Run an ordinary one-day shift and a change received after the onboarding checklist was issued. Ask who approves, what gets paused, which messages need replacement, and what closes the request.
The test is complete when another coordinator can follow the record without asking which date was merely discussed.
Launch path
A five-step HR outsourcing workflow
- 01
Map start-date change coordination
List the source, required fields, owner, due time, and approved destination for start-date change coordination.
- 02
Test examples
Use redacted routine and exception examples with the responsible owner watching.
- 03
Run the lane
Prepare work, route questions, and record evidence without changing the approved scope.
- 04
Review the sample
Compare output to the brief and correct the operating notes.
- 05
Decide the next scope
Expand, narrow, or hand back the work using the review record.
Buyer FAQ
HR outsourcing questions
Can a coordinator approve a start-date change?
No. The hiring or HR owner approves it and controls the employment message.
What records should be checked?
The approved hiring record, onboarding checklist, calendars, access, equipment, and any payroll input affected by the date.
What if one dependency cannot move?
Record the conflict and route it to its owner. Do not hide it by changing an unrelated date.
When is the change complete?
When the authorized date is recorded, approved communications are delivered, and each dependent owner confirms the update.
Sources
Source notes
- International Labour Organization: Recruitment and placementProvides context for transparent recruitment and clear communication around hiring arrangements.