TL;DR
An equipment loan agreement is the short document an employee signs when they receive company hardware. Most companies either skip it or use something a search engine produced. It matters at exactly three moments: when something is damaged, when somebody leaves without returning it, and when a person disputes what they were given. Those are the moments to write for.
- Record what was issued, by serial, with a date. That alone settles most disputes.
- State that the equipment remains company property. Do not leave it implied.
- Be explicit and reasonable about damage. Wear is not negligence.
- Say how return works, including who arranges and pays.
- Avoid deduction clauses you cannot lawfully enforce where you employ people.
- Keep it one page. A long agreement is an unread agreement.
What an equipment loan agreement is actually for
It is not for the day somebody signs it. On that day it is friction.
It is for three later moments. A device comes back with a cracked screen and nobody agrees whose fault that is. Somebody leaves and the laptop does not come back. A person says they were never given the dock that the asset register says they have.
Best tools for Device Management
In all three, the question is the same: what was issued, to whom, when, and on what terms. A one page document answers that in seconds. Without it, the answer is a search through someone’s email.
The part that does most of the work
The inventory. A list of what was issued with serial numbers and a date, acknowledged by the person receiving it.
That single section resolves the majority of disputes, because most disputes are factual rather than contractual. People are not usually arguing about terms. They are arguing about what they were given.
The five sections worth having
Everything beyond these tends to reduce the chance the document is read.
| Section | What it says | Why it is there |
|---|---|---|
| Inventory | Items, serials, condition, date | Settles factual disputes |
| Ownership | Remains company property throughout | Removes the ambiguity at exit |
| Care and use | Reasonable care, report faults promptly | Sets an expectation without being absurd |
| Damage and loss | What to do, and what the company does | The clause people fear most |
| Return | When, how, who arranges and pays | The clause that decides recovery rates |
Two of those need care.
Care and use should be proportionate. A clause demanding equipment be kept in pristine condition is unenforceable in spirit and encourages people to hide faults rather than report them, which costs more.
Damage and loss is where templates go wrong, usually by being harsher than the company would ever actually be. If you would not charge somebody for a dropped laptop, do not write a clause saying you will.
Writing the damage clause honestly
Equipment gets damaged. Screens crack, keys fail, things get dropped. That is the normal cost of putting hardware in the hands of people who are using it.
The useful distinction is not damaged versus undamaged. It is accidental versus negligent versus undisclosed.
- Accidental damage, reported promptly. Company repairs or replaces. No charge.
- Negligent damage. Rare, and worth handling case by case rather than by formula.
- Damage concealed until return. The actual problem, because it delays the replacement and sometimes makes the repair more expensive.
Writing it this way encourages the behaviour you want, which is early reporting. A punitive clause produces the opposite and the company pays twice: once for the worse repair and once for the time somebody worked on a broken machine.
There is a security dimension too. the NCSC device security guidance treats prompt reporting of a lost or compromised device as a basic control, and a clause that makes people afraid to report a problem works directly against it.
On deductions from pay
Many templates include a clause authorising deduction from final pay for unreturned equipment. Whether that is lawful, and under what conditions, depends entirely on where the person is employed, and it is not the same answer everywhere.
Take that one to your own employment advisers rather than a template, and note that a clause you cannot enforce is worse than no clause, because it creates an expectation internally that will not survive contact with payroll.
The return clause decides your recovery rate
The strongest predictor of whether equipment comes back is not the agreement. It is how easy returning it is.
A clause saying equipment must be returned within seven days of the last working day, with no mechanism attached, produces poor compliance from people who are busy, possibly disgruntled, and have no box.
A clause saying the company will arrange and pay for collection within a stated window produces much better compliance, because the only thing asked of the person is to be present.
Say what happens to the data
Worth one line. Equipment is wiped on return, and anything personal on it should be removed by the employee beforehand. NIST Special Publication 800-88 on media sanitization sets out what sanitisation means in practice, and telling people in advance avoids the awkward request for photos back a week later.
For teams without local presence, RemoAsset runs collection from remote employees and can hold returned devices until they are reissued, which is what lets a return clause promise collection rather than request it.
The decision table
How formal this needs to be depends on the exposure.
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Small team, one country | Under 30 staff | Everyone known | Nothing recorded | One page, inventory plus return |
| Remote across countries | 50 to 200 | No office to return to | Recovery is the gap | Company-arranged collection, in writing |
| Contractors and freelancers | Any | Not employees | Different legal footing | Separate agreement, take advice |
| High value specialist kit | Any | Cameras, test devices | Real replacement cost | Per-item sign-out, condition recorded |
| Frequent short loans | Any | Loan pool exists | Nothing comes back | Due date and an automated reminder |
Row three deserves attention. A contractor is not an employee, the relationship is governed by a different contract, and an employee equipment loan agreement may not be the right instrument at all.
Keep it to one page
Length is the enemy here. A four page agreement full of defensive clauses is signed without reading, which defeats the purpose entirely.
One page, in plain language, covering inventory, ownership, care, damage and return. Signed or acknowledged electronically at the point of issue, stored where whoever handles offboarding can find it.
Attach it to a process, not a filing cabinet
The agreement is only useful if it surfaces at the right moment. That means offboarding should pull up what the person was issued automatically rather than relying on somebody remembering to look.
If your asset records and your HR system do not talk to each other, that lookup is manual and will sometimes be skipped. Our note on connecting the asset register to the HRIS covers why that link is worth building.
Re-issue a fresh one when the kit changes
The agreement describes a moment, not a relationship. Somebody issued a laptop in year one and a monitor, a dock and a headset across the following two years is covered by a document that lists one item.
Two workable approaches. Either re-acknowledge the full inventory annually, which is tidy and nobody enjoys, or append each issue as a dated line against the original. The second is less formal and more likely to actually happen.
What does not work is relying on the original signature to cover everything issued since. At exit the document says laptop, the register says four items, and the conversation starts from a contradiction.
One thing worth testing
Pick somebody who left in the last quarter and try to reconstruct what they were issued from the agreement alone. If you cannot, the gap is in the process rather than the wording, and no amount of redrafting will close it.
RemoAsset collects and stores returned equipment, which is what makes a return clause something you can promise. More at HROpsLab.
Frequently asked questions
What should an equipment loan agreement include?
Five sections and no more: an inventory with serial numbers and a date, a statement that the equipment remains company property, a proportionate care and use expectation, a damage and loss position, and a return arrangement that says who arranges and who pays. Keep it to one page in plain language. Longer agreements get signed without being read, which defeats the point of having one.
Can we charge an employee for a damaged laptop?
Whether you can, and under what conditions, depends entirely on where the person is employed, so that is a question for your own employment advisers rather than a template. The more useful question is whether you would. If you would not actually charge somebody for a dropped laptop, do not include a clause saying you will, because an unenforced clause teaches people the document is not serious.
How should the damage clause be worded?
Around behaviour rather than outcome. Distinguish accidental damage reported promptly, which the company simply repairs, from damage concealed until return, which is the actual problem because it delays replacement and often costs more to fix. A punitive clause produces hiding rather than reporting, and the company then pays twice: once for the worse repair and once for the time somebody spent working on a broken machine.
Should the agreement authorise deductions from final pay?
Treat that as a legal question rather than a drafting one, because the answer differs by jurisdiction and is not uniformly permissive. A clause you cannot lawfully enforce is worse than no clause, since it creates an internal expectation that collapses the first time payroll is asked to act on it. Get it checked where you actually employ people before it goes into a standard document.
Does an equipment loan agreement improve return rates?
Less than the return mechanism does. The strongest predictor of whether equipment comes back is how easy returning it is, not what was signed. Requiring return within seven days with no mechanism attached produces poor compliance from people who are busy and have no packaging. Committing to arrange and pay for collection produces much better compliance, because the only thing asked of the person is to be available.
Do contractors need the same agreement as employees?
Usually not the same document. A contractor is not an employee, the relationship sits under a different contract, and an employee equipment loan agreement may be the wrong instrument entirely. The equipment facts still need recording in the same way, with items, serials and dates, but the terms around damage, return and any deduction should be taken from the contractor agreement and checked rather than copied across.
Where should signed agreements be stored?
Somewhere the offboarding process reaches automatically, rather than a folder someone has to remember. The agreement is only useful if it surfaces at the moment a person leaves or a device comes back damaged. If your asset records and HR system do not talk to each other, that lookup is manual and will sometimes be skipped, which is precisely when it was needed.