Assigning assets during onboarding

Assigning assets during onboarding is the join-time swimlane: catalogued kit ready, assignment on or before day one, acknowledgement, so the new person works with named property. It is not a second people pipeline. Hire-to-activate stages stay on hire-to-activate onboarding. HR joining chores stay on the employee onboarding checklist (that checklist may mention kit; it does not own catalog mechanics). How you actually assign — catalog, employee, custody, issue date, condition, acknowledgement — stays on how to assign a company asset. Product surfaces: Dayzen onboarding (activate the person) and Dayzen asset management (assign property to that person). This is not IT auto-provisioning, MDM, or SSO. Dayzen does not image laptops, create VPN clients, or discover devices.

This is operational guidance, not legal advice. Custody terms may depend on applicable law, contract, policy, or company practice. Verify with your HR and legal or SME team.

Two systems, one person

Onboarding answers: is this the employee we meant to hire, are documents in, is the record active, can they log in to the people system you actually run. Asset assignment answers: which serials does this same person hold from which date. If you create a second employee to “park a laptop before joining,” you will merge messes on day one. If you activate the person and never assign kit, they sit at a desk waving at a locked cupboard.

Sequence that usually works:

1. Offer accepted and joining date locked (pipeline fact, not this page’s job to redesign).
2. Catalog the intended kit while they are still pre-join: serials in stock, not yet assigned, or assigned only when the employee row exists.
3. Employee record exists (pre-onboarding or hired state per your process).
4. Assignment on or just before day one — same workflow as any other assignment.
5. Activation and first login as onboarding actually does them. Kit does not replace activation. Activation does not replace kit.

If the employee row does not exist yet, keep kit in stock. Do not invent a dummy intern named “New Joiner March.” Dummy rows become abandoned assignments.

The onboarding checklist’s kit line is a reminder to the joining owner: “laptop/badge planned.” Checking that line because a PO was raised is a lie. Check it when assignment is dated or when you have a dated exception (delay with an owner).

Timing: ready without pretending to be IT provisioning

IT provisioning, in the industry sense, is imaging, MDM enrolment, account creation in directories, SSO, laptop encryption policies, and package deployment. Dayzen does not do that. Your IT team may still do it on their tools. This swimlane only requires that when they finish (or in parallel), HR/admin can assign the serial to the joiner in the people-linked register.

Practical timing patterns (pick one and write it):

• Desk issue on day one. Catalog complete before they arrive. Assignment and acknowledgement at the issue desk that morning. Best when people are on site.
• Issue in the last working days before join. Only if the person already has an employee record and you are willing to have kit in their custody before they are active. Some offices avoid this for contractors; it is a policy choice, not a product rule.
• Remote courier to arrive on join date. Catalog and serial before ship. Condition and acknowledgement on unboxing, with photos of the device if that is your practice. Courier tracking is logistics, not assignment.

Do not ship an uncatalogued box “to save time.” The serial on the airway bill is not the register. Do not wait for MDM enrolment to complete before you are allowed to write an assignment — unless IT physically will not release the device, in which case the blocker is IT’s, and the onboarding owner tracks the date, not a fake assignment.

SSO and email accounts are access. A laptop without accounts is still an assigned asset. Accounts without a laptop are an access problem. The exit checklist later must revoke access and recover kit as different buckets; joining should not mix them into one magic “provisioned” checkbox that nobody can unpack.

Who owns which wait

Hiring manager wants a working person on day one. HR owns the record and the checklist. IT or admin owns imaging and often the physical store. The asset owner (often IT or admin wearing the catalog hat) owns the assignment row. Dayzen onboarding will not purchase hardware. Dayzen assets will not create an Azure account.

When kit is late:

• Write the delay on the joining file: what is missing, who is chasing, expected date.
• Do not skip acknowledgement later because “they already used it for a week.” Assign when the serial actually changes hands, with condition as of that day.
• Do not issue a personal laptop as a silent substitute without a dated exception. Personal devices are a policy topic; they are not a hidden company assignment.

When the person is late (joining date slips): keep the catalog row; do not assign to a date that never happened. If you already shipped, you now have custody in the world before employment — treat it as an exception with an owner, not as a second pipeline stage.

What to prepare before day one

1. Intended kit list for the role (from the handover checklist categories you actually issue to joiners — laptop, badge, SIM, and so on — not a reprint of that whole list here).
2. Catalog rows with serials, optional warranty details stored.
3. Confirmation the employee identity exists so assignment has a target.
4. Issue appointment or courier window on the joining calendar the manager also sees.
5. Condition plan: written state, and photos of the device if you use comparison at return later. Privacy: shoot kit, not people.

Welcome SOP assignment on activation, if you use it, is reading procedures. It is not a laptop. Do not put “collect charger” only inside an SOP and skip the register.

Day one at the issue desk

Walk the assignment sequence without shortening it because the induction room is waiting:

• Match serial to catalog.
• Assign to this employee, issue date today (or the ship date you defined).
• Condition, accessories listed.
• Acknowledgement. Show them my-assets so they know what they own in the company’s eyes.

If induction starts in ten minutes, still take acknowledgement. A rushed blank condition field is how exit disputes are born. The onboarding checklist can wait five minutes; the serial will not get easier to photograph later.

Managers should not intercept kit from a cupboard and skip the desk. Informal day-one loans are assignments you will fail to recover.

A join-time board

Swimlane	Owner	Done means
People pipeline	HR / onboarding	Record exists; activation per hire-to-activate — not redesigned here
Checklist kit reminder	Joining owner	Checked only when assignment or dated delay exists
Catalog ready	Asset owner / IT store	Serials in stock before day one when possible
IT fleet steps	IT (their tools)	Imaging/MDM/SSO if you use them — outside Dayzen assets
Assignment	Issuer	Catalog linked to this employee, dated, acknowledged
My-assets	Joiner	They can see the live kit

What this page must not steal

Do not retell hire-to-activate. Do not copy the full onboarding checklist. Do not copy the full assignment essay; link it and add only calendar and ownership. Do not invent MDM, barcodes, GPS, remote wipe, or procurement integrations. Do not link unpublished helpdesk. First-day manager calendar (buddy, first task) stays on the manager-facing onboarding article if you use it; this page is kit, not culture.

Failure modes

Dummy employee rows. Checking the onboarding kit box when only a purchase order exists. Shipping without catalog. Assigning to the hiring manager “until they join.” Mixing SSO done with laptop assigned. Waiting for Dayzen to provision Windows. Photographing the joiner with the laptop as a welcome ritual and calling it condition evidence. Letting the buddy hand over a spare with no serial. Activating on Friday, kit arriving next Wednesday, nobody writing the delay. Creating a parallel Excel “new joiner hardware” tracker that diverges from the catalog by week two.

Another failure: treating intern kit as optional so nothing is assigned, then charging a lost badge as folklore. Short tenure still uses the same assignment object.

When the swimlane is done

Done when day-one (or your published issue date) has dated assignments for every serial they actually hold, acknowledgements exist, my-assets matches the bag, and open delays are named. Done is not “onboarding status = activated.” Done is not “IT said enrolled.” Enrolled in MDM and assigned in Dayzen can both be true or each can fail alone — record both worlds honestly.

Ready the catalog, assign to the real employee on the joining calendar, acknowledge, keep IT provisioning in IT’s tools. Dayzen onboarding activates people. Dayzen assets assign property. Hire-to-activate owns the pipeline. The onboarding checklist reminds; it does not replace the register.

Use the same swimlane for internships and contractor starts if they hold company property. Stop when kit and the person share a dated link — not with a second hire-to-activate guide or an MDM brochure.