Equipment loan and company property agreement template
Short answer: An equipment loan or company property agreement needs an itemized list of what's being issued (with serial numbers or identifiers where it matters), its condition at issue, who's responsible for loss or damage and under what circumstances, what happens at the end of employment or the loan period, and whether anything can be deducted from final pay for unreturned items, which is legally restricted or requires specific consent in many places. The clause most businesses skip, and regret skipping, is the condition-at-issue record, since without it there's no baseline to compare against if a returned item comes back damaged.
You're issuing equipment, a laptop, tools, a vehicle, to an employee or contractor and want a real paper trail, not a verbal handoff.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
This page may contain affiliate links from which Blur Studio earns commissions.
An equipment loan or company property agreement documents what's been issued to an employee or contractor, who's responsible for it while they have it, and what's expected when it's returned, and it's worth having even for gear that feels too ordinary to bother documenting, since it's rarely the expensive, obviously important item that goes missing without a trace, it's the laptop or the set of hand tools nobody thought to track closely. It applies to anything from a laptop and phone to tools, a company vehicle, or specialized gear, and it matters most exactly when someone leaves or an item comes back damaged or missing, which is precisely when a verbal understanding from months or years earlier is least useful.
Clauses
1. Itemized list and condition at issue
List each item specifically, with a serial number, asset tag, or other identifier for anything valuable enough to track individually, and note its condition when issued (new, good, minor existing wear, with specifics). This condition record is the single most important thing most businesses skip, without it, there's no way to fairly determine whether damage on return happened on the employee's watch or already existed. Landlords use the same idea in a move-in and move-out checklist with tenant signature.
2. Permitted use
State whether the item is for work use only or personal use is allowed (common for phones and laptops), and any specific restrictions, no personal modifications to tools, no unauthorized passengers in a company vehicle, whatever's relevant to the specific item.
3. Responsibility for loss or damage
Distinguish between normal wear and tear (not the employee's responsibility) and loss, theft, or damage from negligence or misuse (where the employee may bear some responsibility). Be specific about what counts as negligence for the items you're issuing, leaving a laptop visibly in an unlocked car overnight is a reasonable example of negligence; a laptop failing from normal use after years of service isn't.
4. Deductions from final pay
If you intend to deduct the value of unreturned or damaged equipment from final pay, know that many states restrict or prohibit this without the employee's specific written consent, and some prohibit it from final pay entirely regardless of consent. This is a genuine area to confirm with an employment lawyer in your state before writing deduction language into the agreement and relying on it, rather than assuming a generic clause protects you. Final pay rules also appear in the employment agreement template and e-signing guide.
5. Return requirements
State the return deadline (commonly on the employee's last day, or within a short window after), the condition expected (normal wear accepted, not damage beyond that), and the process for confirming return, a simple return receipt, countersigned by both parties, closes the loop properly. For crew members, equipment handover fits into the contractor and field crew onboarding checklist.
A filled-in example
Items issued: One laptop (serial number noted, condition: good, minor cosmetic wear on the lid noted and photographed), one company phone (new condition). Permitted use: Work use primarily; incidental personal use of the phone permitted. Responsibility: Employee responsible for loss or theft due to negligence (left unattended in a public place, not reported promptly if stolen); not responsible for normal wear or manufacturer defects. Return: Both items due on last day of employment; a return receipt noting condition at return, signed by both employee and a manager, closes out the agreement. Deductions: No deduction from final pay without separate written consent at the time, consistent with the company's state law on wage deductions.
Vehicles and higher-value items need a bit more
For a company vehicle specifically, add a few things beyond the standard template: expectations on personal use (commute only, or broader personal use permitted), who's responsible for routine maintenance and fuel, a requirement to report any accident or damage within a short window, and confirmation of who's covered under the company's insurance policy while driving it. For specialized tools or equipment tied to a specific license or certification requirement, note that certification requirement directly in the agreement, so there's a clear record that the person issued the equipment was actually qualified to use it at the time. Gear lent to a self-employed worker belongs alongside an independent contractor agreement.
Sending and issuing it
Sign this when equipment is actually handed over, not retroactively weeks later once someone's already been using it, since the condition-at-issue record only means something if it reflects the item's real state at the moment of handoff. QuickSigner, a web-based electronic signature tool that lets you send a document for signature from any device without the signer needing to create an account, works well here, particularly for remote employees receiving shipped equipment who can sign the agreement before or as soon as it arrives. Build the agreement with the itemized list and condition notes, and send it through QuickSigner for signature at issue, and again as a return receipt when the equipment comes back. Both carry a timestamped audit trail, useful if a dispute over condition or return timing ever comes up.
Common mistakes worth avoiding
Skipping the condition-at-issue notes is the most common and most costly mistake, since it's the one detail that actually protects an honest employee from being blamed for pre-existing damage, and protects the business from absorbing damage that happened on someone's watch. A second mistake is writing broad deduction language without checking your state's actual wage deduction rules, which can create a clause that's not just unenforceable but potentially creates its own compliance problem if applied. A third is treating this as only relevant for expensive items, a missing $40 tool matters less individually, but a pattern of unreturned small equipment across a whole team adds up, and a consistent process catches both ends of that range the same way. A fourth mistake, specific to businesses with any turnover, is not actually running the return process at offboarding, relying on an exit checklist item nobody double-checks rather than a signed return receipt that closes the agreement out properly. A fifth, worth naming separately: letting the original issue agreement sit in an email attachment somewhere instead of a searchable record tied to the specific employee and item, which is exactly the gap that turns a routine offboarding into a drawn-out argument about who has what.
How I'd approach this
For most small businesses issuing equipment to staff, the itemized agreement above, signed at issue and closed out with a return receipt, is genuinely enough, and I wouldn't suggest anything more elaborate for a handful of items per employee. Where it becomes worth building something more connected is once you're tracking equipment across many employees and locations and want issue dates, condition notes and return status visible in one place automatically, rather than searching through individually signed agreements whenever an item goes missing or a return is disputed. Below that scale, a simple signed form per item, filed consistently, does the job well, and I'd rather tell a small business owner that honestly than build them something bigger than the actual problem.
Questions people ask
Can I deduct the cost of unreturned equipment from a final paycheck?
This depends heavily on your state, many restrict or prohibit wage deductions without specific written consent, and some prohibit deductions from final pay regardless. Confirm your state's specific rule with an employment lawyer before relying on a deduction clause.
What's the most important thing to include in an equipment loan agreement?
An itemized list with the condition noted at the time of issue. Without that baseline, there's no fair way to determine whether damage found at return happened on the employee's watch or already existed.
Should this cover personal use of company equipment?
Yes, state explicitly whether personal use is allowed, common for phones and laptops, and any specific restrictions, rather than leaving it assumed and potentially disputed later.
Do I need a signature every time I issue a small tool?
For genuinely low-value, easily replaced items, a simpler log may be enough. For anything valuable, specialized, or likely to travel off-site with an employee, a signed agreement is worth the small extra step.
How do I handle equipment returns for a remote employee?
An e-signature tool like QuickSigner lets you send both the original agreement and a return receipt for signature remotely, which works well when shipping equipment back isn't paired with an in-person handoff.
What if equipment comes back damaged and the employee disputes it?
This is exactly what the condition-at-issue notes are for, compare the documented condition at issue against the condition at return. Without that original record, you're relying on memory against memory, which rarely resolves cleanly.