Skip to content
Assetze

IT Asset Management

IT Onboarding Checklist: From Laptop Procurement to Day 1

Plan employee IT onboarding from laptop procurement to Day 1, with clear owners, device preparation, account access, delivery checks and a complete checklist.

Author

Ishika

ShareLinkedInX

An employee is joining your company in two weeks. HR has shared the joining date, the manager has requested a laptop, and IT has started preparing the employee's accounts.

A few days later, the manager asks for a different laptop model. The employee will be working remotely, but their delivery address hasn't been confirmed. Procurement is waiting for approval, and nobody has checked whether a suitable device is already available.

Each request is manageable on its own. The delays come from the information arriving at different times and from different people.

This becomes harder when companies hire across multiple locations. A laptop may need to be purchased in one city, configured by an IT partner, delivered to an employee elsewhere and recorded in a central inventory. The same employee may need repairs or a replacement later.

A good IT onboarding process gives everyone involved a clear view of what has been requested, what is ready and what still needs attention.

This guide covers the practical decisions behind that process, along with a checklist that IT, HR and Admin teams can adapt to their own workflows.

What should an IT onboarding checklist cover?

An IT onboarding checklist should cover the employee's device, required applications, company accounts, security settings, access permissions, delivery, asset assignment and first-day verification.

It should also identify who is responsible for each task and how the team will confirm completion.

For smaller companies, one IT or Admin employee may handle most of this work. Larger organisations may involve HR, Procurement, IT, Finance, external vendors and local support teams.

The number of people involved changes, but the information they need remains fairly consistent.

Start with the joining date and work backwards

A joining date tells IT when the employee is expected to start. It doesn't tell them how long preparation will take.

A standard laptop already available in the office may only need inspection, configuration and handover. A specialised machine could require additional procurement time. International delivery introduces another set of considerations.

Before committing to a device, IT should have the following details:

  • Employee name, department and reporting manager
  • Joining date and work location
  • Laptop specifications and operating-system requirements
  • Accessories needed for the role
  • Required software and licences
  • Systems the employee needs access to
  • Budget approval, where applicable
  • Delivery address for remote employees
  • Any additional security or device-management requirements

It helps to record when these requirements were approved.

Suppose an employee's joining date moves forward after procurement has begun. The original plan may no longer work. Having the request history available allows IT to identify what changed and decide whether another device can be assigned.

How much notice should IT receive?

There is no single lead time that works for every company.

An IT team should establish its own planning periods based on device availability, approval time, configuration and delivery.

One practical approach is to separate onboarding requests into categories.

Type of requestWhat needs to be checked
Standard laptop available internallyCondition, configuration and handover
New laptop purchaseAvailability, price approval and delivery
Specialised laptopHardware specifications and supplier availability
Remote employeeShipping address, delivery time and receipt
International employeeLocal sourcing, logistics and support arrangements
Urgent joiningSuitable available devices and approval for changes

Reviewing previous onboarding requests can help establish realistic lead times for each category.

Check inventory before placing a new order

IT employee scanning the asset label on a laptop resting on a desk
IT employee scanning the asset label on a laptop resting on a desk

An employee leaving the company may return a laptop that can be used by someone joining the following month.

That sounds straightforward until the device arrives without its charger, requires a battery replacement or is still registered under the previous employee's account.

A laptop being physically present in the office tells IT very little about whether it can be issued again.

For onboarding purposes, inventory should show the device's current condition and availability.

Useful statuses include:

StatusMeaning
AssignedCurrently issued to an employee
AvailableChecked and suitable for allocation
ReservedAllocated to an upcoming requirement
Returned, pending inspectionReceived but not cleared for reuse
Under repairAwaiting repair or testing
In transitBeing delivered or collected
RetiredRemoved from active use

A returned device should go through the company's approved data-removal, inspection and configuration process before reassignment.

Its specifications also need to suit the next employee.

For example, a laptop previously used by someone in sales may be suitable for another sales hire but insufficient for a developer working with demanding local applications.

Having accurate inventory information gives IT more options when a request is urgent. It also helps prevent unnecessary purchases.

What changes when employees are spread across countries?

Device preparation becomes more difficult to coordinate when employees are joining from different locations.

A company may have one process for approving laptops, but the actual procurement and delivery work can vary by country.

Local availability, delivery arrangements, repair options and support hours all affect the employee's experience.

Assetze's work with Lyric offers a useful example.

How Lyric manages device operations across four countries

Lyric is an AI-powered supply-chain technology company with IT and device requirements across the USA, UK, Germany and the Netherlands.

Its partnership with Assetze began in January 2026 and covers procurement, device setup and deployment, inventory management, employee IT support, repairs, replacements, deliveries and collections.

Before the partnership, Lyric maintained device and purchasing information in a single sheet and relied on manual follow-ups. As requirements increased across locations, the internal IT team needed additional support coordinating device movements and employee requests.

Assetze became an ongoing partner for these activities.

The process described in the case study starts when Lyric raises a requirement. Assetze reviews the request, checks available options and obtains approval where a purchase or paid service is involved. The device or service is then arranged, tracked and supported through completion.

The current case study records more than 100 devices and accessories procured since the partnership began.

For an IT team handling employee onboarding across countries, this kind of coordination addresses a practical problem: keeping track of the device after the purchase has been approved.

A procurement record can confirm what was bought and at what price. IT still needs to know whether the equipment has been prepared, dispatched, delivered and assigned to the intended employee.

What should be recorded for a remote delivery?

Laptop and accessories packed securely for delivery to a new employee
Laptop and accessories packed securely for delivery to a new employee

For employees working outside the main office, IT should be able to retrieve:

  • Employee name and destination
  • Device model and serial number
  • Procurement or inventory reference
  • Configuration status
  • Expected dispatch and delivery dates
  • Shipment reference
  • Delivery confirmation
  • Employee acknowledgement
  • Owner of any outstanding issue

These details are also useful when a device needs to be collected, repaired or replaced.

Prepare accounts alongside the device

Laptop procurement and account creation often involve different people.

While IT or Procurement arranges the hardware, another team may be responsible for creating accounts, assigning licences and approving access.

Both need to be ready by the joining date.

The required accounts depend on the employee's role. Common examples include company email, communication tools, HR systems, shared drives, project management software and role-specific applications.

Access should be approved by the relevant manager or system owner.

A finance employee may require accounting software and restricted financial folders. A salesperson may need CRM access and sales reporting tools. An engineer may need access to development systems and repositories.

Using a standard role-based access request helps teams collect this information consistently.

However, roles can change over time. IT should review the permissions requested for each employee rather than automatically copying everything assigned to someone in a similar position.

Security setup before the first login

Depending on the company's IT policies, device preparation may include encryption, endpoint protection, operating-system updates, device-management enrolment and screen-lock settings.

Account preparation may include multi-factor authentication, licence assignment and group membership.

Some tasks need to be completed by the employee during their first login, particularly password creation and authentication enrolment.

The IT team can prepare the required settings and instructions beforehand.

Assign responsibility for every handoff

Consider an employee whose joining date changes from Friday to Wednesday.

HR updates its records. The manager expects the laptop to arrive earlier. Procurement has already placed the order, and IT is preparing the device according to the original schedule.

Someone needs to inform the teams involved and confirm whether the revised date is achievable.

A shared onboarding request makes this easier, particularly when each activity has an assigned owner.

ActivityTypical ownerCompletion evidence
New-hire notificationHRIT receives the request
Device requirementsHiring managerSpecifications approved
Device selectionIT / AdminSuitable device identified
Purchase approvalBudget ownerApproval recorded
Procurement and setupIT / ProcurementDevice prepared
Application accessIT / System ownerAccess assigned and approved
DeliveryIT / LogisticsReceipt confirmed
Asset assignmentIT / AdminInventory updated
First-day verificationIT / EmployeeEssential access tested

Companies can change the ownership to match their internal structure.

The completion evidence is particularly useful. It reduces the need for follow-up messages asking whether a task has been finished.

Handling last-minute changes

When an employee's joining date, location or device requirement changes, the original request should be updated.

IT can then review the effect on procurement, configuration, access and delivery.

If the planned device will arrive late, the team may be able to allocate another suitable laptop from inventory.

Any reassignment should be reflected in the asset record, including what happened to the original order.

Documenting these exceptions helps companies handle future changes without reconstructing the entire situation from emails.

Record the device assignment before handover

The employee's laptop will probably remain in use long after the onboarding request is closed.

During that time, it may require a repair, an upgrade or a replacement. The employee may move locations or eventually leave the company.

The assignment record created during onboarding should therefore be accurate enough to support those later activities.

At minimum, record the employee, device model, serial number, asset ID, assignment date, location, condition and accessories issued.

Where relevant, include warranty details and the device's management-system reference.

What Lyric's asset tracking process illustrates

As part of its work with Lyric, Assetze maintains device details, employee assignments and equipment status.

The inventory distinguishes between available, assigned and returned equipment, giving the team a clearer view of devices across the supported locations.

That information is useful during onboarding because it helps identify what can be allocated. It remains useful when a device needs to be repaired, collected or reassigned.

For distributed teams, accurate assignment records can also reduce the effort involved in locating equipment when an employee changes roles or leaves the organisation.

Test the setup before the employee arrives

Remote employee testing a video call on her laptop
Remote employee testing a video call on her laptop

IT can prepare an account and install the required applications without knowing whether the employee will be able to use everything successfully.

Some access problems only become visible during the first login.

Before the joining date, the team should confirm that the device is ready, licences are assigned, relevant permissions are configured and any required security policies are applied.

For a remote employee, delivery should also be confirmed.

On Day 1, the employee can complete authentication enrolment, sign in to their accounts and test the applications needed for their work.

If an essential system is unavailable, the issue should be recorded with an owner.

This provides a clearer way to handle incomplete setup than relying on the employee to contact several different people.

When should an onboarding request be closed?

A laptop delivery confirmation is one milestone. The employee may still be waiting for software access or an accessory.

It is useful to establish a small set of completion checks.

CheckWhat confirms completion
Device receivedEmployee acknowledges delivery or handover
First login completedEmployee successfully accesses their account
Essential applications availableRequired tools have been tested
Equipment recordedAsset assignment and accessories are updated
Outstanding issues reviewedOpen requests have owners and next steps

Some non-essential requests may remain open after the employee starts.

The onboarding owner should know which items are pending and whether they affect the employee's ability to work.

A short check-in during the first week can identify missing access, software issues or equipment requirements that were overlooked.

What can IT teams learn from completed onboardings?

A checklist helps teams complete individual requests. Reviewing those requests over time can show where delays occur.

For example, a company might discover that laptop deliveries are consistently on schedule, while employees frequently wait for access to one particular application.

That points towards an approval or account-provisioning issue.

Another company may find that most urgent laptop purchases happen because hiring requirements reach IT only a few days before the joining date.

The appropriate improvement would involve the notification process between HR, hiring managers and IT.

A few useful measures include:

MeasureWhat it can reveal
Notice received before joiningWhether IT has sufficient preparation time
Device delivery by agreed dateProcurement and logistics performance
Essential setup completed on Day 1Overall onboarding readiness
Missing-access requests during Week 1Gaps in requirements or approvals
Devices assigned with incomplete recordsInventory tracking problems
Existing devices successfully reassignedHow effectively inventory is being reused
Time taken to resolve onboarding issuesSupport and escalation performance

These measures are more useful when reviewed by location, role and type of device request.

A specialised laptop purchased internationally will have different preparation requirements from a standard device already held in inventory.

Comparing similar requests makes it easier to identify patterns and decide where changes are needed.

Managing employee devices after onboarding

The device issued to an employee will eventually require some form of attention.

An application may stop working. The laptop may need a repair. An employee may move to another country or leave the company, requiring equipment collection.

Assetze supports companies with these activities across procurement, deployment, inventory management, employee IT support, repairs, retrieval and device retirement.

The Lyric partnership shows how this works in a distributed environment, where employee support and device movements need to be coordinated across several countries.

For IT teams, the information collected during onboarding provides a useful starting point for managing those later requests.

The employee assignment, device condition, location and support history can all help the team decide what action is required.

Before the next employee joins

Take a recent onboarding request and follow it from the first HR notification to the employee's first week.

Check when IT received the requirements, how the laptop was selected, who approved access, when the device arrived and whether any requests remained unresolved after joining.

That review will often reveal which parts of the process rely on someone remembering to send a message or follow up.

Document those handoffs, give each task an owner and make the device record part of the process from the beginning.

The next onboarding request should then be easier to prepare, track and complete.

Download the IT onboarding checklist

Use the Download the checklist link directly below this section to open the full-resolution checklist. Save the image to your device using Save image as on desktop, or touch and hold it on mobile.

The checklist covers preparation before joining, Day 1 and the first week, with spaces for task owners, due dates and equipment details.