New starter checklist

Use this checklist to coordinate the people who make a new starter ready for work. It is a suggested internal template, not a statement of mandatory Kuwait documents or legal deadlines. Adjust it to the role, site and approved company procedures.

Create one case with an employee identifier or a temporary reference, an agreed start date, location, manager and coordinator. Do not use a personal identity number as the public case label. Each task should have an owner, a target date, a status and evidence of completion.

Prepare the case and its dependencies

Before assigning tasks, confirm what is already approved and what remains conditional. Route documentary, contractual or work-eligibility questions to the authorized HR/legal process. A checklist records the outcome of those checks; it does not replace them.

Agree the communication language and confirm the correct Arabic/English name fields where used. Define which tasks depend on an earlier decision. An access request should not be treated as approved merely because someone has entered a proposed start date.

Before the first day

• Confirm the approved role, reporting person, work location and start arrangements.
• Assign a manager or delegate for the first-day welcome and questions.
• Send arrival instructions through the agreed channel.
• Request only the equipment and system access justified by the role.
• Prepare the employee master record and identify evidence still requiring checking.
• Arrange the role-specific workplace or safety introduction with its responsible owner.
• Agree an alternative if a required tool or account is not ready.

Keep sensitive attachments in restricted storage. The coordinator can track “checked by HR” without giving every task owner a copy of the evidence.

On the first day

• Confirm arrival and the actual contact person.
• Explain immediate work priorities and where to ask for help.
• Show the employee how attendance, routine requests and incident reporting work in that workplace.
• Test necessary access with a low-risk task, rather than only checking that a login exists.
• Introduce the relevant policies and the route for questions.
• Record missing equipment, access or information as assigned issues.

For example, if a branch employee cannot access the request portal, note the issue, the support owner and the approved fallback. Do not mark the whole onboarding case complete because the welcome meeting took place.

During the first week

Ask the manager to review an actual work sample and check whether the employee can perform the agreed initial tasks. Confirm that the employee record and connected attendance/payroll records use the same approved identifier and start information.

Resolve blockers with the task owner. Record whether the employee needs training, a corrected record or a process decision; these require different responses. Check whether temporary access can now be removed. Avoid granting broad permanent access as a shortcut around a setup problem.

At the first-month review

Review progress against the role outcomes, remaining support and next learning priorities. The first-month timing is an internal planning choice, not a legal probation rule. Keep any employment-status or contractual decision within its separate authorized process.

Use the following case-control fields:

Close with evidence and a handover

The coordinator checks that each completed task has evidence and each “not applicable” entry has a reason. Assign any remaining action to the ongoing manager or service owner, then tell the employee where future questions should go. Restrict the case to people who need it and apply the approved retention treatment.

Use the onboarding guide for the wider plan, employee files for supporting records and attendance exceptions for a clear explanation of one common first-week process.