TL;DR
- An employee equipment policy is the document that answers who buys a device, who owns it, who looks after it, and what happens to it when somebody leaves. Most disputes trace back to one of those four questions never being answered.
- If you have fifteen people in one office and everybody uses a machine the company obviously owns, you do not need a policy document. You need a list of what you issued.
- The policy does four jobs: it records ownership, it sets the standard of care, it defines the return obligation, and it says what the company does with personal data on a work machine.
- Three models exist: company-provided, a stipend the employee spends, and bring your own device. They produce completely different offboarding problems, and the choice is made at hire whether or not anybody writes it down.
- Anything touching deductions from final pay depends entirely on your jurisdiction and your own legal advice. This page does not tell you what you may do, and no vendor page should either.
- Done properly, nobody reads it until the week somebody leaves, and then it answers the question without a negotiation.
The Argument Nobody Expected to Have
A designer handed in her notice after three years. On her last Friday she asked whether she could keep the laptop. She had, she pointed out, chosen it herself, the company had reimbursed her for it through an expense claim rather than buying it centrally, and she had paid for the memory upgrade out of her own pocket eighteen months earlier.
The People lead did not know the answer. Neither did the finance manager who approved the original claim. There was no document, and the only evidence of the arrangement was an expense line labelled "laptop". The conversation took three weeks, went up two levels, and ended with the company letting her keep a machine it had paid for, largely because nobody could demonstrate that it had not been part of her package.
That is not a story about a chancer. She had a reasonable case precisely because the company had never decided. An equipment policy is not really a document about equipment. It is a set of ownership decisions, written down before anybody has an incentive to remember them differently. Every argument of this shape traces back to a decision somebody deferred at the point of hire, when it felt administrative and cost nothing to skip.
Best tools for Device Management
This is what an employee equipment policy is supposed to solve.
When You Don't Actually Need One
When the manual way is genuinely fine
Under about fifteen people, one location, everybody on machines the company visibly bought and handed over. Ownership is not ambiguous because everybody watched it happen. What you need at this size is a list of serial numbers and who holds them, not a policy document nobody will read.
When friction starts appearing
The signal is the first question you have to think about before answering. Can somebody expense a monitor. Does a contractor get a company laptop. Can a person use their work machine for a side project. The moment two people in the company would answer one of those differently, you have a policy gap, and it typically appears somewhere around thirty people.
When it becomes a liability
It stops being an internal matter once an outsider asks. A security questionnaire asks whether staff use personal devices for company data. An auditor asks how device return is enforced. A buyer in due diligence asks what hardware the company owns. At that point an undocumented practice is indistinguishable from no practice, whatever people actually do.
The edge case that forces it
Hiring in a second country, or taking on contractors alongside employees. Both break the assumption that one arrangement covers everybody. The terms that are normal for a permanent employee in your home market may be unworkable or inappropriate elsewhere, and a single undifferentiated policy either overreaches or says nothing useful.
Five Questions People Ask Before Writing One
"Who owns the laptop?" Whoever the document says owns it, and the absence of a document is itself an answer that tends to favour whoever is holding it.
"Can we require people to return it?" You can set an obligation, and what you can do about non-compliance is an entirely different question that depends on your jurisdiction. Those two things get conflated constantly.
"What about the personal photographs on it?" This needs a stated position before somebody asks, because the answer affects whether devices come back promptly.
"Does this apply to contractors?" Only if you write a version that does. The arrangement is usually different and pretending otherwise creates a gap exactly where the hardware risk is highest.
"How long does this need to be?" Two pages. The longest equipment policies are the ones written by committee after an incident, and length is not what makes them hold.
The Four Decisions the Document Has to Make
Everything else in an equipment policy is detail hanging off these. Make them explicitly, in writing, before the first device ships.
Who buys, and through what route
Centrally purchased hardware is unambiguous: the company bought it, the company owns it, there is an invoice with the company's name on it. Reimbursed hardware is where ownership gets murky, because an expense claim looks a great deal like a payment to the employee. If you reimburse, say in writing at the point of reimbursement that the device remains company property. That one sentence prevents the dispute in the cold open.
Who owns it, stated plainly
Write the word. "This device remains the property of the company at all times." Teams avoid this because it reads as cold, and then discover that warmth in the drafting is what produced ambiguity at the exit. You can be perfectly pleasant about it in person; the document's job is to be unambiguous.
What standard of care applies
What happens if it is dropped, lost, or stolen. The policy should say what the person is expected to do, which is report it promptly, and should not pretend to settle financial liability, because that is jurisdiction-dependent and belongs with your own advisers. A clear reporting obligation is worth more operationally than a liability clause nobody will enforce.
What happens at the end
The return obligation, the timescale, and who arranges it. The single most useful clause states that the company arranges and pays for the return, because it removes the most common excuse and costs very little. A policy that obliges the employee to organise international shipping at their own expense is a policy that produces unreturned laptops.
| Decision | The clause that works | The gap when it is missing |
|---|---|---|
| Purchase route | Reimbursed devices remain company property | Expense claim reads as part of pay |
| Ownership | Stated in plain words, no hedging | Ambiguity resolves towards the holder |
| Care and loss | Prompt reporting obligation | Incidents surface late or not at all |
| Return | Company arranges and pays | Non-return with a reasonable excuse |
The Clauses That Actually Get Tested
Most of an equipment policy is never read. These parts are, and they are read by somebody who is annoyed.
Personal data on a work machine. Say what happens to it. The useful version tells people not to store personal files on a company device, acknowledges that they will anyway, and tells them to remove anything they want to keep before returning it, with a stated date after which the drive is erased. Vagueness here delays returns, because somebody with family photographs on a laptop will stall rather than ask.
Personal use. Decide whether it is permitted and say so. A blanket prohibition nobody observes is worse than a permissive clause with limits, because a rule that is routinely broken teaches people the whole document is decorative.
Upgrades and accessories bought by the employee. The memory upgrade in the cold open. State whether company property absorbs employee-funded improvements or whether the person may remove them, because somebody will eventually ask and there is no obvious default.
Equipment in the event of a dispute. The uncomfortable case: somebody is leaving badly and the laptop becomes a bargaining chip. A policy that already states the return obligation and the company-paid mechanism removes the negotiation. One written after the dispute starts does not.
And what you will not do. If the policy is silent on deductions from final pay, say that any financial question is handled separately and subject to local requirements. Silence invites a manager to improvise, and improvising on pay is how an equipment issue becomes an employment issue.
Writing It So It Survives Contact With a Leaver
A policy is tested once, at the end, usually by somebody who is no longer invested in your goodwill. Three drafting habits decide whether it holds.
Name the obligation, not the aspiration. "Employees are expected to take reasonable care of company equipment" is unenforceable and unhelpful. "Report loss, theft or damage to IT within two working days" is a thing somebody either did or did not do.
Put the return mechanism in the policy, not in a process document. The leaver will be shown the policy. If the mechanism lives in an internal runbook they have never seen, the clause reads as an obligation with no route to comply.
Have it acknowledged at issue, not at exit. The signature that matters is the one taken on the day the laptop is handed over, when the relationship is good and nobody is arguing. Acknowledgement collected during offboarding is acknowledgement collected from somebody with no reason to cooperate.
Checklist:
- Ownership stated in plain words, including for reimbursed purchases.
- Return obligation with a timescale, and the company arranging and paying.
- Reporting duty for loss, theft and damage, with a number of days.
- Position on personal files, including a date after which the drive is erased.
- Position on personal use, written to be followed rather than to sound strict.
- Separate treatment, or explicit exclusion, for contractors.
- Acknowledged at the point of issue and stored where offboarding can find it.
- A line stating that financial questions follow local requirements and separate advice.
So keep it to two pages. A policy somebody will read in four minutes during their first week is worth more than a comprehensive one filed where nobody looks.
The Policy, Clause by Clause
Advice about what a policy should contain is cheaper than the policy. So here is the shape of each clause that carries weight, with the reasoning, in the order they belong. Adapt the wording and have your own advisers review it for each jurisdiction you employ in.
Scope. Name who it applies to and, just as importantly, who it does not. One line: this policy applies to employees issued with company hardware, and contractor arrangements are set out separately. Policies that silently assume everybody is an employee create their largest gap exactly where turnover is fastest.
Ownership. The load-bearing clause, and the one most often softened into uselessness. State that equipment issued to or purchased for an employee remains company property at all times, regardless of whether it was bought centrally or reimbursed through expenses. That final clause is the one that would have resolved the dispute in the opening of this piece, and it costs 14 words.
Issue and acknowledgement. Say that equipment is recorded against the individual at the point of issue, with make, model and serial number, and that the employee confirms receipt. The confirmation is the part people skip. It takes 30 seconds on day one and is the only evidence you will have later about what was handed over.
Care, loss and damage. Set a reporting duty with a number in it: report loss, theft or damage to IT within 2 working days. Keep it to the obligation. Resist the temptation to write a liability clause here, because what you may recover and how is jurisdiction-dependent, and an unenforceable clause weakens the parts of the document that are enforceable.
Personal use and personal data. State whether personal use is permitted, in terms you will actually apply. Then say that employees should not store personal files on company equipment, that anything personal must be copied off before return, and that the drive is erased on receipt. Give the erasure a timescale, 30 days after return is a common and workable figure, so that somebody worried about their photographs knows where they stand.
Return. The clause that decides your recovery rate. Say that on the final working day, or on request, equipment is returned using packaging and shipping arranged and paid for by the company, and that the employee is asked to return it within 10 working days of receiving that packaging. Putting the company's obligation first is deliberate: it removes the most common and most reasonable excuse.
Financial matters. One line pointing elsewhere: any financial consequence of unreturned equipment is handled separately and in accordance with local requirements. Do not try to settle it in the equipment policy.
Review. Name the owner and a review cadence. A policy with no named owner is the one still describing a stipend model 2 years after the company moved to company-provided hardware.
| Clause | Must contain a | Common failure |
|---|---|---|
| Ownership | Plain statement covering reimbursed purchases | Softened into ambiguity |
| Issue | Serial number and an acknowledgement | Nothing recorded at handover |
| Loss and damage | Reporting window in days | Liability wording that cannot be applied |
| Personal data | Erasure timescale | Silence, which delays returns |
| Return | Company-arranged and company-paid | Obligation with no mechanism |
| Financial | A pointer to separate advice | Improvised deductions |
The Handover Is the Policy's Only Real Enforcement Point
Everything above is decided in drafting and enforced in a single moment: the day somebody is handed a laptop. Get that moment right and the rest of the document rarely needs to be argued. Get it wrong and you are relying on goodwill 3 years later.
Three things have to happen at issue, and they take about 5 minutes between them.
Record the serial against the person. Not the model, the serial. A register that says "MacBook Air" against 40 names is not a register, because you cannot match a returned device to the record and you cannot tell an auditor which machine went where.
Take the acknowledgement. A line in the onboarding flow confirming the person has received the equipment listed and has read the policy. Most HR platforms will do this as a task, and BambooHR and similar systems can hold the signed acknowledgement against the employee record so that offboarding can find it later.
Say the two sentences out loud. That the machine belongs to the company, and that the company will arrange and pay for its return when the time comes. People remember the second sentence, and it is the one that makes the first sentence feel reasonable rather than cold.
But the reason to care about the handover is not legal. It is that recovery rates are set by whether somebody, 2 years later, knows what they are holding and expects to give it back. A policy acknowledged on day one produces that expectation. A policy produced for the first time during an exit interview produces a negotiation.
The Three Models, and the Problem Each Creates
Company-provided
What it is. The company buys, owns and issues the hardware, and takes it back.
When it's right. Almost always for employees, and particularly where data sensitivity, a security questionnaire or any kind of audit is in play. Ownership is unambiguous and the standard is consistent.
When it fails. It creates a logistics obligation in every country you hire in. The policy is simple and the operation is not, which is the trade most companies accept.
A stipend the employee spends
What it is. A fixed sum, and the person buys their own machine.
When it's right. Contractors, or markets where shipping a company device is genuinely impractical. It removes the logistics problem entirely.
When it fails. It removes the logistics problem by giving away the asset. The device is the employee's, so there is nothing to recover, no consistent specification, and limited control over how company data is handled on it. That is an acceptable trade only if you have decided it deliberately, and most companies arrive at it by accident because it was easier at the time.
Bring your own device
What it is. People use machines they already own, and the company secures what it can.
When it's right. Short engagements, very small teams, or populations where the company has no realistic route to providing hardware.
When it fails. It fails hardest at the exit, because there is no device to retrieve and the company data on it leaves with the person. It also tends to fail the first time somebody fills in a security questionnaire honestly. If you choose this, choose it knowing that the control you have is over accounts rather than over hardware.
What the Contractor Version Has to Say Differently
This page has told you four times to treat contractors separately without saying what changes, so here it is. The differences are narrow but they matter, and a contractor annex of half a page covers them.
Say who owns the machine, and mean it either way. If the contractor uses their own hardware, say so and stop pretending otherwise in your security answers. If you issue company hardware, the ownership clause is identical to the employee one and so is the return obligation.
Set the return point to the end of the engagement, not a last working day. Contracts end, pause and resume. A clause written around a final working day does not describe how contractor engagements actually conclude, and the ambiguity is where devices stay out.
Keep the control at the account layer regardless. Whoever owns the laptop, the company controls the accounts. For a contractor on their own machine that is the only control you have, so the access review at the end of an engagement matters more than it does for an employee whose device is coming back anyway.
Avoid clauses that read as employment terms. Detailed rules about how somebody uses their own equipment during their own working hours can look like control over the manner of work, and in some jurisdictions that feeds into how an engagement is characterised. Keep the contractor annex to ownership, return and data, and take local advice before adding anything that governs conduct.
So write the annex once and attach it to the contractor agreement rather than the handbook. Contractors rarely read a staff handbook, and a term nobody was shown is a term you will struggle to rely on.
How to Choose: Five Questions Before You Talk to Any Vendor
Which model are you actually running today? Not the one in the handbook. Look at the last ten hires and see what each person is working on and who paid for it. Companies are frequently running two models without having chosen either.
Where would a device have to come back from? List the countries. A policy with a return obligation you have no mechanism to fulfil is a policy that generates write-offs, and the mechanism is the expensive part.
Who enforces the clauses? Name the role. Equipment policies fail in the same way as every other policy: the document is fine and nobody owns the step. The person who notices that a leaver's laptop has not been returned is the policy's actual implementation.
What does your security questionnaire say today? Pull the last one a customer sent you and read your own answers about device management. If those answers assume company-provided hardware and your practice is a stipend, you have a gap that will surface in front of a customer.
Does any of this apply to contractors? Decide explicitly. The honest answer is often that contractors use their own machines and the control is at the account level, which is fine if written down and a problem if merely assumed.
Six Options Worth Knowing
The policy is the document. These are the platforms that execute it, and the reason they belong in a policy discussion is that a return obligation you cannot operate is not really a policy. Every vendor here was checked against its own pricing page on 6 and 7 October 2026 and not one publishes a figure, so treat budget as a sales conversation.
RemoAsset
Disclosure: RemoAsset is owned by the same people who publish HROpsLab. It appears here because it belongs in this category and is described with the same detail and the same limitations as everything else on this page.
Best for: companies that want the policy's lifecycle, issue through to return, to run on one platform.
Why companies choose it: the device is recorded against a named person and address from the moment it is purchased, which is what makes the return clause operable later. Offboarding in the HRIS triggers the return without anybody remembering, and recovered machines can be stored and reissued.
Where it struggles: quote-based with a demo required, so it cannot be compared on paper. It is considerably weaker if you did not procure through it, because then it works from whatever register you already have. And it is neither an MDM nor a certified disposition vendor, so policies that depend on enforced device configuration or on certified end-of-life processing need something else alongside it.
Workwize
Best for: multi-region fleets where storage near the employee is the constraint.
Why companies choose it: regional warehousing makes the reissue half of a policy practical rather than theoretical, with strong European coverage.
Where it struggles: no published price. The multi-region capability is overhead for a company operating in two or three countries.
Deel IT
Best for: teams already employing or contracting through Deel.
Why companies choose it: the employment record and the equipment record sit in one place, so the offboarding trigger already exists.
Where it struggles: quote-based. Compelling as an extension of an existing relationship, much less so bought alone.
Firstbase
Best for: companies whose policy covers the whole home setup rather than a laptop.
Why companies choose it: desks, chairs and peripherals are in scope, which matches policies written during the shift to remote work.
Where it struggles: no published price, and the breadth is only an advantage if your policy really does cover furniture.
GroWrk
Best for: enforcing a return obligation in Latin America and parts of Asia.
Why companies choose it: in-country presence where other providers subcontract, which is the difference between a policy that works there and one that does not.
Where it struggles: publishes nothing. Its page names a per-order model and a subscription tier without attaching figures to either.
allwhere
Best for: United States-led companies with international staff and configuration requirements.
Why companies choose it: depth in the deployment side, not only the shipping.
Where it struggles: consultation-only pricing, so no paper comparison is possible.
What Each One Published
| Option | Published price | Unit | What it executes |
|---|---|---|---|
| RemoAsset | Not published, demo required | n/a | Issue, return, storage, wipe |
| Workwize | Not published | n/a | Issue and return with regional storage |
| Deel IT | Not published | n/a | Equipment inside an employment platform |
| Firstbase | Not published | n/a | Full home setup |
| GroWrk | Not published, models named only | n/a | Issue and return in emerging markets |
| allwhere | Not published, consultation | n/a | Deployment and return |
Checked on each vendor's own page, 6 and 7 October 2026.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| One office, company buys everything | Under 15 | Single site | Nothing is ambiguous | A serial number list, no policy document |
| Two people would answer the same question differently | 20 to 60 | Any | Undocumented practice | A two-page policy, no tooling yet |
| Reimbursing laptops through expenses | Any | Any | Ownership is genuinely unclear | A written ownership line at reimbursement |
| Hiring in a second country | 40 plus | Multi-country | One policy no longer fits | Separate terms per population |
| Return clause with no mechanism | 50 to 500 | Remote | Write-offs with good excuses | A platform that arranges returns |
| Contractors on their own machines | Any | Any | Control sits at the account, not the device | Explicit contractor terms, account-level controls |
| Customer security questionnaire pending | Any | Any | Your answers do not match practice | Fix the practice before the answers |
| Latin America or Asia in scope | Any | Remote | Coverage, not drafting | GroWrk or a regional specialist |
Most companies sit in two rows at once, and the common pair is a drafting row with a mechanism row. Draft first. A mechanism bought before the ownership decision is made will enforce an arrangement nobody agreed.
What Getting This Wrong Costs
The cost people expect is the hardware, and it is the least of it. A handful of laptops written off each year is an irritation on a finance report, not a reason to change anything.
The real cost is that an undocumented equipment arrangement turns every exit into a one-off negotiation, and the outcomes diverge. One person keeps their laptop because they asked at the right moment, another is chased for three weeks over an identical machine, and both of them talk to colleagues. The inconsistency does more damage than either outcome, because it signals that the rule is whatever the company can be bothered to enforce. That reputation is expensive to repair and it arrives long before anybody notices the cause.
The third cost is the one that surfaces in front of a customer. Security questionnaires ask about device management, and the honest answer for a company running an undeclared stipend model is that staff use personal hardware and the company does not control it. Finding that out while completing an enterprise questionnaire is a poor time to find it out, and the fix is months of work rather than an edit to a document.
So ask the diagnostic question directly. Is this a drafting problem, an operations problem, or a decision nobody has made? A drafting problem is two pages of work. An operations problem needs a mechanism and a budget. An undecided question needs somebody with authority to choose between company-provided, stipend and bring your own device, and until that happens the document will keep describing a practice the company does not actually follow.
When You're Ready to Move Beyond a Handbook Paragraph
The signals are concrete. Somebody has asked a question the handbook does not answer. You are hiring in a country you cannot easily ship to. A customer has sent a security questionnaire with a device section. Or an exit has turned into a negotiation about a laptop. Any one of those is the point at which the paragraph becomes a policy.
Write the document first and buy the mechanism second, because the mechanism enforces whatever you decided and cannot decide for you. Two pages, acknowledged at issue, with the return clause stating that the company arranges and pays.
If the gap is the mechanism rather than the drafting, RemoAsset is built around the lifecycle a policy describes, from the purchase record through to the triggered return, which is why it fits companies that run the whole thing in one place and fits poorly as a retrieval service bolted onto hardware bought elsewhere. It is worth a look alongside the alternatives here, and expect a demo rather than a price from any of them.
And on anything involving money taken from a final payment, take your own legal advice for each jurisdiction you employ in. The answer differs considerably between countries and it is not a question a software vendor, or this page, should be answering for you.
Frequently Asked Questions
What is an employee equipment policy?
An employee equipment policy is the written document setting out who buys company hardware, who owns it, what standard of care applies while somebody holds it, and what happens to it when they leave. It usually also states a position on personal use and on personal files stored on a work machine. The useful version runs to about two pages and is acknowledged by the employee at the point the device is issued rather than during offboarding. Its real function is to record ownership decisions in advance, because every dispute about equipment is in practice a dispute about a decision nobody made at the time.
What should an equipment policy actually contain?
Four things carry nearly all the weight: a plain statement that the device remains company property including where the purchase was reimbursed, a return obligation with a timescale and a mechanism the company pays for, a duty to report loss or theft within a stated number of days, and a position on personal files including a date after which the drive is erased. Beyond those, a stated position on personal use and separate treatment for contractors cover most of what gets tested. Anything concerning money recovered from a departing employee should point to separate advice rather than attempting to settle it, because the answer varies by jurisdiction.
Can we deduct the cost of an unreturned laptop from final pay?
That depends on your jurisdiction, the terms the person agreed to, and the circumstances, and it is a question for your own legal advice rather than for an article or a vendor. What this page can say is operational: the companies that rarely face the question are the ones that removed the friction instead, by arranging and paying for the return themselves and asking promptly while the relationship is still intact. Treating deduction as the primary lever tends to produce a worse recovery rate than treating convenience as the primary lever, quite apart from whether it is permissible where you are.
Should contractors get company laptops?
Sometimes, and the decision should be explicit rather than inherited. Issuing company hardware to contractors gives you the same control you have over employee devices and the same retrieval obligation, which is a real cost in a population that turns over faster. Letting contractors use their own machines removes the logistics entirely and moves your control to the account layer, which is a legitimate choice if the data they touch is suitable for it. The arrangement can also carry implications for how the engagement is characterised in some jurisdictions, so check that locally before standardising on either answer.
What is the difference between a stipend and company-provided equipment?
A stipend gives the employee money to buy their own machine, so the asset belongs to them, there is nothing to recover at the end, and the specification varies by person. Company-provided means the business buys, owns and retrieves the device, which gives consistency and control at the cost of running a logistics operation in every country you hire in. The two produce opposite offboarding problems: a stipend has no retrieval work and no retained asset, while company-provided has an asset worth reissuing and the obligation to get it back. Most companies drift into a stipend because it is easier at the point of hire rather than choosing it on the merits.
How do we handle personal files on a returned laptop?
State the position in the policy and repeat it in the return request. The arrangement that works is to tell people not to store personal material on work devices, accept that some will, instruct them to copy anything they want off before returning the machine, and give a date after which the drive is erased. The reason this matters operationally rather than only legally is that uncertainty about personal data is a common cause of delayed returns: somebody with family photographs on a laptop will put off sending it back indefinitely rather than raise the question, and one clear sentence removes that.
Do we need a separate policy for each country?
Usually not a separate policy, but separate terms within one. The structure that holds is a single document stating the ownership and return principles, with a short annex covering the points that genuinely differ by location, which are typically anything financial and anything about the mechanics of return. Writing a complete policy per country produces documents that drift apart and contradict each other within a year. Have your own advisers review the annex for each jurisdiction you employ in rather than assuming a clause that works in one market transfers to another.
Who should own the equipment policy?
People or HR should own the document and IT should own the mechanism, with one named person responsible for noticing when a leaver's device has not come back. The common failure is to treat it as an IT document, which produces something technically precise that never reaches the employee at the point of issue, or as a purely HR document, which produces a return clause with no operational route to comply with it. Whichever way round you do it, the policy only works if acknowledgement is collected when the device is handed over, and that step belongs to whoever runs onboarding.
HROpsLab takes no vendor money and publishes no paid placements, and does not tell you what the law requires in your jurisdiction.