A contractor laptop policy sets out whether people who are not employees use company hardware or their own, who owns it, and what happens at the end of an engagement. Most companies apply their employee policy by default and discover the gaps when a contractor leaves holding company data.
TL;DR
- Contractor engagements are shorter and turn over faster, so issue-and-recover economics work differently.
- The deciding factor is data sensitivity, not employment status.
- Equipment provision can bear on how an engagement is characterised in some jurisdictions, so take local advice.
- Write the terms into the contractor agreement, not the staff handbook they will never read.
- Set the return point at the end of the engagement, not a last working day, because engagements pause and resume.
- Where contractors use their own machines, your only real control is at the account layer.
Why the employee policy does not transfer
Three things differ, and each breaks an assumption built into most equipment policies.
Duration. A three-month engagement does not justify the cost of procuring, shipping and retrieving a machine, which for an international contractor can approach the value of the work. Turnover. A contractor population cycles several times faster, so each process failure repeats more often. And the end point. Engagements conclude, pause, extend and resume, so a clause written around a final working day does not describe how they actually finish.
Applying the employee policy unchanged produces a document that is either unworkable or silently ignored, and the second is more common.
Decide on data, not on status
The useful question is not whether somebody is an employee. It is what they can reach.
A contractor with access to customer records, financial systems, production infrastructure or source code presents the same exposure an employee would, and the absence of a controllable device is the same gap regardless of the contract type. For that population, issue company hardware whatever the engagement length.
A contractor writing copy or designing assets in tools you control is a different case, and their own machine with account-level controls is a reasonable arrangement. Sort people by what they touch and the policy writes itself.
Where the terms belong
A common and avoidable failure. Equipment terms placed in a staff handbook do not reliably reach contractors, who are frequently never given one and have no particular reason to read it.
Put the equipment clauses in the contractor agreement itself, as a short annex. Half a page covering ownership, return and data is enough, and it is attached to a document the person actually signs.
What to do:
- Add an equipment annex to the contractor agreement template, not to the handbook.
- State ownership plainly, including for anything reimbursed.
- Tie the return obligation to the end of the engagement rather than to a working day.
- Say who arranges and pays for the return, which should be the company.
- Record the serial number against the individual at issue, as you would for an employee.
The characterisation question
Worth raising because it is frequently either ignored or over-interpreted.
In some jurisdictions, the provision of equipment is among the factors considered when assessing whether an engagement is genuinely independent or is closer to employment. That is not a reason to avoid providing hardware, and it is a reason to take local advice before standardising an approach across a contractor population spanning several countries.
What this page can say is practical: keep the equipment annex to ownership, return and data, and avoid clauses governing how somebody works, when they work or what else they may use the machine for. Rules about conduct are where a document starts to read like an employment term. What any of it means where you operate is a question for your own advisers.
When they use their own machine
The common arrangement, and a legitimate one for lower-sensitivity work. The thing to be clear-eyed about is that your control moves entirely to the account layer.
You cannot see the device, configure it, or wipe it. What you can do is decide what it reaches and remove that access cleanly. Conditional access rules can require a managed device for your most sensitive systems while permitting lower-risk work from anywhere, and a managed boundary keeps company material in applications you can clear remotely.
Checklist:
- Put sensitive systems behind a managed-device requirement, and permit the rest from anywhere.
- Keep company material inside a managed boundary that can be cleared remotely.
- Revoke every token and session at the end of the engagement, not just the main login.
- Send a written deletion request naming the categories of data and a date.
- Record on the asset register that no wipe was possible, so the limitation is documented.
If you do issue hardware, plan the return first
Contractor retrieval fails more often than employee retrieval, for a straightforward reason: the relationship was always transactional and nobody feels much obligation once the invoice is settled.
Ask while the engagement is still running. A return arranged in the final fortnight, with prepaid packaging already sent, works far better than a request made after the last payment has cleared. Platforms in our laptop procurement comparison can trigger the return from an end date, and none of them publishes pricing, so expect a quote.
Where an engagement is likely to resume, consider leaving the device in place rather than running two shipments. Recovering a laptop only to send it back six weeks later costs more than holding it.
Final Thoughts
- Sort contractors by what data they touch, not by their contract type.
- Sensitive access means company hardware regardless of how short the engagement is.
- Put equipment terms in the contractor agreement, since the handbook will not reach them.
- Tie return to the end of the engagement, and have the company arrange and pay for it.
- For own-device arrangements, control the accounts and document that no wipe was possible.
- Take local advice before standardising, because equipment can bear on characterisation.
Frequently Asked Questions
Should contractors get company laptops?
It depends on what they can access rather than on their contract type. A contractor who can reach customer records, financial systems, production infrastructure or source code presents the same exposure an employee would, and should be issued company hardware regardless of how short the engagement is. A contractor working in tools you control on low-sensitivity material is a reasonable candidate for using their own machine with account-level controls. Sorting the population by data access rather than by employment status produces a policy that is both defensible and practical.
Does giving a contractor a laptop affect their employment status?
In some jurisdictions the provision of equipment is one of several factors considered when assessing whether an engagement is genuinely independent, so it is worth taking local advice before standardising an approach across several countries. It is not generally a reason to withhold hardware from somebody who needs it for security reasons. The practical guidance is to keep equipment terms narrow, covering ownership, return and data, and to avoid clauses governing how or when somebody works, since conduct rules are what make a document read like an employment term.
Where should contractor equipment terms be written?
In the contractor agreement itself, as a short annex of around half a page, rather than in a staff handbook. Contractors are frequently never issued a handbook and have no particular reason to read one, so a term that lives only there is difficult to rely on later. The annex needs to cover three things: that the equipment remains company property including anything reimbursed, that it is returned at the end of the engagement with the company arranging and paying for the return, and what happens to company data on the device.
How do we recover laptops from contractors?
Start before the engagement ends rather than after. Contractor retrieval fails more often than employee retrieval because the relationship was transactional and obligation drops sharply once the final invoice is settled. Sending prepaid packaging during the last fortnight, with a clear request and a date, produces far better results than contacting somebody weeks after payment. Where an engagement is likely to resume within a couple of months, consider leaving the device in place, since two international shipments usually cost more than holding the machine.
What can we control if a contractor uses their own machine?
Only the accounts and the data, which is why both need to be set up properly from the start. Conditional access rules can require a managed device for your most sensitive systems while permitting lower-risk work from any device, and a managed application boundary keeps company material in a space you can clear remotely without touching anything personal. At the end of the engagement, revoke every token and session rather than only the primary login, send a written deletion request naming the categories of data, and record on your asset register that no device wipe was possible.
Is a stipend a good option for contractors?
Often yes, and it is one of the clearest cases for the arrangement. A stipend removes the logistics entirely, which matters most for engagements too short to justify procuring and retrieving a machine, and it matches the commercial nature of the relationship. State in writing at the point of payment who owns what is bought, because silence resolves in favour of the person holding the hardware. The exception remains data sensitivity: where a contractor will handle material you could not afford to lose control of, provide managed hardware regardless of engagement length.
