From joining letter to a ready first day
By Mrunal Walke2 min read
Connect a confirmed joining date to HR, IT and manager tasks while keeping document acknowledgement separate from onboarding completion.
On this page
A joining letter can confirm that a new colleague is reporting for work, but it does not provision a laptop, assign a manager or explain the first week. Treat the confirmed joining information as an input to onboarding, with separate owners for the work that follows.
Confirm the starting record
Capture the person's name, employee reference, role, manager, location and agreed joining date. Link the final document rather than circulating multiple editable copies. If a date changes, retain the previous value and identify which dependent tasks need rescheduling.
Keep the document appropriate to the employment arrangement and approved local practice. This workflow guide does not establish employment terms; those belong in the organisation's authorised documents.
Divide the first-day dependencies
HR verifies the personnel record and required documentation. IT prepares the approved equipment and access. The manager sets the first meeting and practical induction tasks. Facilities handles site access where needed. Each task needs an owner and a completion signal.
| Task | Completion should mean |
|---|---|
| Equipment | Assigned device is ready for handover |
| Account | Approved account can be used securely |
| Manager meeting | Time and contact are confirmed |
| Documents | Required items have been reviewed |
| Induction | Employee knows where to begin |
Marking the entire checklist complete because the joining letter arrived removes the visibility this process is supposed to provide.
Handle the date-change example
Imagine a new starter's date moves from Monday to the following Thursday. The workflow should update reminders and appointments without creating a second employee record. IT may hold the prepared device, while the manager reschedules the introduction. If the start is cancelled, route account and equipment tasks through the appropriate cancellation procedure.
Use an onboarding ID to link the tasks. A changed email address or spelling correction should not start a second onboarding plan. Let a coordinator review potential duplicates before merging records.
Check readiness before arrival
The day before joining, review blockers by owner rather than reading a percentage-complete score. A missing welcome presentation is different from a missing laptop or unapproved account access. Record the workaround and the person responsible for it.
After the first day, ask the employee whether they could access the systems and contacts they needed. Keep that feedback separate from document compliance. Zoho People's onboarding documentation describes employee onboarding as a workflow; the practical handoffs above help turn that workflow into an observable first-day result.
Further reading
Primary reference. The workflow examples above are illustrative implementation guidance, not customer results.
Explore the related Dood resource. To discuss your workflow, contact Dood System.
