TL;DR
A contractor to employee conversion usually updates payroll, benefits and notice terms, and leaves the device arrangement exactly as it was. If the person worked on their own machine, somebody now has to decide whether the company issues one. If the company already owned the laptop, the paperwork tying them to it is stale.
- Three device situations exist at conversion. Each needs a different action.
- Own machine to company machine is a procurement job with a start date.
- Company machine already issued means the agreement needs re signing, not reissuing.
- The asset register almost always still shows the old contract type.
- Access and data usually move first. The hardware is the part that lags.
The moment this becomes real
Say a developer has worked with you for fourteen months on a contract. They are good. You convert them to a permanent role starting in six weeks. Legal redrafts the agreement. Payroll sets up the record. Somebody books a laptop.
Then it turns out they already have one of yours, shipped eleven months ago when a project needed a locked down machine. It is in the register under a name nobody recognises, with no equipment agreement attached, because contractors were never in that workflow.
Best tools for HR Operations
So you are about to ship a second laptop to somebody who already has one. The real issue is not the ordering mistake. It is that the device record and the employment record have never been connected, and a conversion is the one moment when both change at once.
When this is lighter than you think
Four stages where the work is genuinely small.
- The contractor used their own machine and will keep doing so. Nothing physical changes. Update the record to say so, and check your acceptable use terms cover an employee rather than a supplier.
- One conversion a year. Handle it by hand with a checklist. Building a process for an annual event is wasted effort.
- Same country, same office. If they can walk in and swap machines, this is an afternoon rather than a project.
- No regulated data involved. The decision is still worth making, but the consequences of getting it wrong are smaller and slower.
It gets heavier when conversions come in batches, when the person sits in a country where you have no entity, or when their own machine holds company data that now needs to move.
The five questions teams actually ask
Do we have to issue a laptop on conversion? Not automatically. Many companies do, because controlling the endpoint gets easier. Some keep a bring your own device arrangement. The decision belongs to your security posture, not to the contract type, and it is worth writing down once rather than per person.
What happens to the work on their personal machine? This is the step most teams skip. If company data sits on a device you do not own, a conversion is the natural moment to move it and confirm the original copies are gone. Agree what that confirmation looks like before the start date.
Does the equipment agreement need re signing? Usually yes. An agreement signed by a supplier is a different document from one signed by an employee, and deductions, liability and return terms often differ. Check what your template says about who it binds.
Who pays for the new machine? Whoever owns the headcount budget from the start date, which is rarely the team that engaged the contractor. Resolve this before procurement, or the order stalls in approvals for a fortnight.
Does anything change about worker status? That question is jurisdictional and it is not a device question. The tests differ by country and by circumstance. Take local advice rather than reasoning from a device policy.
Three ways teams handle it, and where each breaks
Treat it as a new joiner. Run the person through onboarding from scratch, issue fresh equipment, create a new record. Clean and simple. It breaks when they already hold company hardware, because you end up with two machines and one of them is invisible.
Treat it as a record update. Change the contract type, keep everything else. Fast and tempting. It breaks because the equipment agreement, the access review and the device standard all quietly stay on contractor terms, and nobody notices until an auditor reads the file.
Treat it as a conversion with its own checklist. A short list covering device decision, data move, agreement re signing and register update. This works. It costs you the effort of writing it and the discipline of using it, which is more than it sounds when conversions are rare.
Five questions to find your own gaps
A contractor to employee conversion exposes whatever your two records disagree on. These five surface it quickly.
Can you list every contractor currently holding company hardware? If the register has no contract type field, the answer is no and that is the gap.
Who signs the equipment agreement for a contractor today? If the answer is nobody, conversions are not your only problem.
What is your standard machine for this role? Deciding at conversion is slower than deciding once per role band.
How long does procurement take to that country? Work backwards from the start date. Six weeks of notice can still be too little for some markets.
Who closes the loop on the personal device? Name a person. If it is everybody, it is nobody.
What is actually available
Five honest options for handling the device side, including ours.
Do nothing structural. Best when conversions are genuinely rare. Chosen because it costs nothing today. Struggles the moment you convert three people in a quarter and each one is handled differently.
A conversion checklist in your HR system. Best for most teams. Cheap, visible and it forces the device question to be asked. Struggles on execution: it records that a laptop was requested, not that one arrived.
An IT asset tool with a contract type field. Best when you already run one. Makes the population queryable. Struggles because it still relies on somebody updating the field, and conversions are exactly the event people forget.
Your EOR or payroll provider’s device add on. Best if they already employ the person in that country. Convenient. Struggles on the handover itself, and usually treats a conversion as a new start rather than a continuation.
RemoAsset. Best when the person sits in a country you do not operate in and a machine has to reach them before a start date. Chosen because procurement, delivery and the register entry happen together, so the device the person receives is the device the record shows. Where it struggles: it will not tell you whether to issue a laptop at all, which is a policy decision you still own, and it does not touch contracts or worker status. It also publishes an entry subscription price but no per device rates, so budgeting needs a conversation first.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Rare conversions, one country | 1 to 2 a year | No IT function | Nobody owns the device step | A one page checklist in the offer workflow |
| Regular conversions, same market | 5 to 15 a year | One IT generalist | Duplicate machines get ordered | Add a contract type field to the register |
| Converting contractors abroad | Any volume | No local entity | Machine cannot reach them in time | A lifecycle service such as RemoAsset for delivery |
| Bring your own device today | Any volume | Security review pending | Company data on personal machines | Decide the policy before the next conversion |
| Batch conversion after an acquisition | 20 plus at once | Mixed estates | Two registers that do not agree | Reconcile both lists before issuing anything |
What the gap actually costs
The visible cost is a duplicate laptop. Annoying, recoverable, and small. It is also the least interesting thing that goes wrong here.
The second cost is the equipment agreement that never got re signed. When that person eventually leaves, the terms you try to rely on for return or deduction were written for a supplier relationship that ended months earlier. Whether those terms still bite depends on your jurisdiction and your drafting, which is exactly the conversation you do not want to be having at offboarding.
The third is the quiet one. Company data stays on a personal machine because nobody closed that loop, and it stays there for years. You cannot attest to a device you do not control. So the question is not whether the conversion went smoothly. It is whether you could say, today, where that work actually lives.
When a checklist stops being enough
The checklist holds until geography breaks it. One conversion in your own city is a conversation and a courier. Four conversions across three countries, with start dates fixed by contract, is a logistics problem wearing an HR hat.
What changes at that point is who carries the physical step. Instead of asking a manager to arrange a machine in a market they have never shipped to, procurement and delivery become somebody else’s job with a tracked outcome. A laptop lifecycle management service for distributed teams covers the part a checklist can only ask about.
That is not an argument for buying one during your second conversion. It is an argument for noticing which step keeps slipping. If it is the decision, write the policy. If it is the paperwork, fix the template. If it is consistently the box arriving somewhere you have no presence, that is the step worth handing over. Keeping the asset record updated as devices move is the part that makes the next conversion easier than this one.
See how device retrieval works when a conversion falls through
Read our guide to the employee equipment agreement
Related reading
- What belongs in an employee equipment agreement
- Putting the device policy in the handbook
- Writing an equipment exception policy
- Equipment deductions from final pay
- Worker status tests differ by country. The US IRS publishes its classification guidance and the UK government publishes employment status guidance. Take local advice rather than reasoning from either.
Frequently Asked Questions
Does a contractor to employee conversion require issuing a new laptop?
No rule forces it. Many companies issue one because controlling the endpoint makes security and support simpler, but a bring your own device arrangement can continue if your policy allows it. Decide the rule once at policy level rather than case by case, and record which arrangement applies to each person.
What should happen to company data on the contractor’s own machine?
Move it to company systems and agree what confirmation looks like that the original copies are gone. A conversion is the natural moment, because the person is cooperative and still engaged. Leaving it costs nothing today and becomes very hard to resolve once the relationship ends.
Do we need to re sign the equipment agreement?
Usually. An agreement signed in a supplier relationship is a different document from one signed by an employee, and terms on liability, deduction and return often differ between the two. Check what your template says about who it binds, and take advice if the answer is unclear.
Who pays for equipment issued at conversion?
Whoever holds the headcount budget from the start date, which is frequently not the team that engaged the contractor. Settle this before raising the order. Unresolved ownership is the most common reason a conversion laptop arrives late.
How far ahead should procurement start?
Work backwards from the start date using your real delivery times to that country, not your average. Markets with customs steps can take considerably longer than domestic shipments. If you have never shipped there, treat the estimate as unverified until somebody confirms it.
Should the asset register show contract type?
Yes, and most do not. Without it you cannot answer a basic audit question about who holds company hardware under what arrangement. Adding the field is cheap. Backfilling it honestly is the work, and a conversion is a good moment to start.
Does converting a contractor change their worker status elsewhere?
Status tests vary by jurisdiction and by the facts of each engagement, so no general answer is reliable. The device arrangement is not what determines it. Treat status as a question for local advisers and keep it separate from your equipment policy.
