TL;DR
- A handbook answers what should I expect and what do I do. A policy answers what are the rules and who decides. Most equipment content is written as the second and filed as the first.
- Four things people actively look for and usually cannot find: what you get, what happens if it breaks, what you may do with it, and what happens at the end.
- The what-if-it-breaks clause is the most asked question in this area and the most commonly absent.
- A blanket ban on personal use is ignored rather than followed. Silence is worse, because it creates an assumption you did not choose.
- Family use is the specific case nobody writes down and almost everybody does.
- Anything touching deductions, liability or consequences belongs elsewhere and needs local advice. The handbook's job is to point at it, not to state it.
The Question That Took Four People to Answer
Somebody's laptop stopped charging on a Tuesday. They looked in the handbook, which had a section called Company Equipment running to about 200 words, covering the fact that equipment is provided for work purposes and must be returned on termination.
So they asked their manager, who did not know and asked the operations lead, who said to raise a ticket. The ticket was raised against the wrong queue, picked up two days later, and answered with a question about whether the person had a spare machine. They did not. Four people, three days, and a laptop that was still not charging.
None of the people involved behaved unreasonably, and the handbook had answered a question nobody had asked while omitting the one somebody actually had. The 200 words were a compressed version of a policy, written to establish a position, when what the reader needed was an instruction: tell this queue, here is what happens next, here is what you do in the meantime.
Best tools for HR Operations
That gap is the subject of this article. It is not a legal gap and it is not usually a policy gap. It is that the handbook was written from the company's point of view rather than the reader's.
Handbook, Policy and Contract Do Different Jobs
Worth separating before anything else, because most of the confusion in this area comes from one document trying to do all three.
The handbook tells people what to expect and what to do. It is read by somebody with a question, usually in a hurry, usually once. Its test is whether a reader can act after reading it.
The policy sets out rules, decision rights and process. It is read by whoever administers the thing, and by somebody checking whether a decision was correct. Its test is whether two different administrators would reach the same answer.
The contract and its related documents cover obligation and consequence. What is owed, what may be withheld, what follows from a breach.
Where any particular statement has to live, and what can be said in each, differs by jurisdiction and by the way your documents are structured, so take local advice on that rather than following an article. What is safe to say generally is the direction of the error: companies put policy language in handbooks, which produces a document that establishes a position and answers no questions.
So the four clauses below are written as handbook content. Each one points at the policy or the contract where a decision or an obligation sits, rather than restating it.
Clause One: What You Get
The most basic question and the one most handbooks leave to a conversation.
Somebody joining wants to know what equipment arrives, roughly when, and what to do if something is missing. Somebody already there wants to know whether they are entitled to a second monitor or a different keyboard, and whether asking is reasonable.
State the standard bundle as a list. The laptop, the charger, and whichever peripherals are standard. If you run tiers by workload, say so and say which tier applies to which kind of work, with a link to the detail. A bundle described as appropriate equipment is not a bundle, it is an invitation to ask a manager, and the outcome of that will correlate with how comfortable somebody is asking.
Say what is standard and what is on request, separately. Two short lists. This single distinction prevents most of the small negotiations that otherwise happen per person.
Give the request route and a rough turnaround. Where to ask, who decides, how long it usually takes. A route with no stated turnaround defaults to whenever somebody gets round to it, and people stop using routes that feel slow.
Say what happens if something does not arrive. This is the day-one case and it is common enough to deserve a sentence. Who to tell, and what the interim arrangement is.
And keep the specifications out of the handbook. Exact memory and storage figures belong in the equipment standard, which changes quarterly, while the handbook changes rarely. Link to it rather than copying it, because a handbook containing hardware configurations will be out of date within two quarters and people will notice.
Clause Two: What Happens If It Breaks
The most asked and least written clause in this entire area.
Four facts, and the whole thing fits in about eighty words.
| What the reader needs | Why it has to be here |
|---|---|
| Where to report it | The default is to ask a manager, who does not know either |
| What happens in the meantime | Whether there is a loaner, and if not, what to do that day |
| Who pays for accidental damage | The question everybody worries about and few ask aloud |
| What happens if it is lost or stolen | Including the reporting expectation, which is time-sensitive |
The third row is the one to handle carefully and the one most likely to be either absent or wrong. What may be recovered from somebody, in what circumstances, differs by jurisdiction and by the terms involved, and a handbook paragraph asserting a position may be both unenforceable and alarming. Take local advice, then write the handbook line as a pointer: here is where the position is set out, here is who to talk to.
Write the loaner answer honestly. If there is a spare machine available in a day, say so, because it removes most of the anxiety in this clause. If there is not, say that too and say what the interim arrangement is, since a reader who knows they will be without a machine for four days can plan, and a reader who does not know will spend those four days asking.
Put the theft or loss reporting expectation in hours rather than vaguely. A device holding company data that goes missing is a time-sensitive matter and the handbook is where somebody will look at the moment it happens. A sentence naming the contact and the expectation to report immediately does more good here than anything else in this document.
Clause Three: What You May Do With It
The clause companies either omit or over-write, and both failures produce the same result, which is people doing whatever seems reasonable.
Personal use. A blanket prohibition is ignored. Everybody checks a personal email account, books a holiday and reads the news on a work laptop, and a rule that makes most of the workforce technically non-compliant is a rule nobody can enforce selectively without it looking arbitrary. State a reasonable-use position instead: incidental personal use is fine, here are the specific things that are not. The named exclusions are where the value is, because they are the ones people would not guess.
Family use. The specific case nobody writes down and a great many people do, particularly with a device at home. A handbook that is silent on whether somebody's partner can borrow the laptop for an hour has left a decision to the person holding it. One sentence settles it, and the honest version for most companies is that the device is for the employee's use and others should not use it, with the reason given, because a rule with a reason is followed more often than a rule without one.
Installing software. What people may install themselves, what needs a request, and what is blocked. If the machine is managed and the answer is that installation is controlled, say so plainly, because somebody who does not know will spend twenty minutes trying before asking.
Travel and taking the device abroad. Three practical consequences worth a line each: that warranty and service arrangements are often regional, that some destinations have specific restrictions, and who to tell before travelling if notification is wanted. This is practical information rather than a rule, and it is the kind of thing people are grateful to find.
So the whole clause is five short paragraphs with a few named exclusions, and it works because it tells people where the edges are rather than asserting a position they will quietly ignore.
Clause Four: What Happens At the End
Most handbooks have this one and most have it in the wrong form, as a single sentence saying equipment must be returned.
What the reader needs is the sequence, because the sequence is what they will experience.
When the conversation happens. Early in a notice period rather than at the end, which is also better for the company's recovery rate. Saying so in the handbook means the message that arrives in week one is expected rather than surprising.
How the return happens. Whether a collection is booked for them, whether packaging arrives, and whether they need to do anything beyond handing it over. The answer that works operationally is that the company books it, and a handbook that says so prevents the person assuming they have to arrange something.
What happens to the data. That the device will be cleared, and that personal files should be removed beforehand. This is the clause people most appreciate and almost nobody writes, because somebody with four years of photos on a work laptop needs to know that in week one of a notice period rather than on the last day.
What is not expected back. If a monitor was bought with a stipend and is theirs, say so. Ambiguity here produces a conversation nobody wants about who owns a desk chair.
And one sentence pointing at where the obligations are set out, for anything about non-return or liability. That is deliberately a pointer, because it is the part that varies by jurisdiction and that a handbook paragraph is most likely to get wrong.
When You Should Not Expand the Handbook
When the handbook is already too long to read
If your handbook runs to 60 pages, adding four clauses makes the problem worse. The fix is a short equipment section with links to a single equipment page that holds the detail, and the handbook's job becomes routing rather than answering.
When the answers genuinely do not exist yet
A handbook clause describing a loaner arrangement you do not have is worse than silence, because it creates an expectation and then fails it. Decide the operational answer first. The handbook is downstream of the arrangement, not a substitute for it.
When the policy is in flux
If you are about to change the equipment standard or the tier structure, write the handbook clause to point at the standard rather than to restate it, and then the change does not require a handbook revision. This is good practice regardless and it is essential during a change.
The edge case that forces the writing
The second time the same question reaches somebody senior. One instance is a conversation; two is a missing clause, and the question that arrives twice is almost always one of the four above.
Five Questions People Ask First
"Does this belong in the handbook or the policy?" Apply the reader test. If somebody with a question could act after reading it, it is handbook content. If it establishes a rule, a decision right or a consequence, it is policy or contract. Most equipment content fails this test in one direction: it is written to establish something and read by somebody who needed to do something.
"Can we just say equipment must be used appropriately?" You can and it answers nothing. Appropriately is doing the work of a list that nobody has written, and the effect is that each person decides for themselves and nobody is wrong until somebody decides they are. The named exclusions are the whole value.
"What about deductions for unreturned equipment?" Out of scope for a handbook and out of scope for this article. What may be recovered, in what circumstances and with what consent, differs by jurisdiction and by the terms involved, so take local advice and let the handbook point at wherever that position is properly set out.
"Do people actually read handbooks?" They read the section they need, when they need it, usually through a search. That is an argument for clear headings and short answers rather than for giving up. The four clauses above are each the answer to a question somebody is actively looking for, which is a very different reading pattern from the induction skim.
"How often should this be reviewed?" The clauses rarely, the linked equipment standard quarterly. That split is the reason to link rather than copy, and it is the mechanism that keeps the handbook accurate without a revision cycle nobody has time for.
Where Each Statement Belongs
| Statement | Handbook | Equipment standard | Policy or contract |
|---|---|---|---|
| The standard bundle, as a list | Yes, as a summary | Yes, in detail with figures | No |
| Exact memory and storage figures | No, link to them | Yes | No |
| Where to report a fault | Yes | No | No |
| Whether a loaner is available | Yes | No | No |
| Who bears the cost of damage | Pointer only | No | Yes, with local advice |
| Reasonable personal use position | Yes, with named exclusions | No | Possibly, depending on structure |
| Family use | Yes, one sentence | No | No |
| Software installation rules | Yes, briefly | Possibly | No |
| Travel consequences | Yes, practical notes | No | No |
| Return sequence and data clearing | Yes | No | No |
| Non-return obligations | Pointer only | No | Yes, with local advice |
The pointer rows are the ones to get right. A handbook that asserts a position on liability may be both inaccurate for some readers and intimidating for all of them, while a handbook that says where the position is written and who to ask is useful to everybody and wrong to nobody.
Writing It, With Word Budgets
Four clauses, about 500 words in total, which is shorter than most existing equipment sections and considerably more useful.
What you get: 150 words. Two lists, standard and on request. The request route with a turnaround. One line on what to do if something does not arrive. A link to the equipment standard for the detail.
If it breaks: 120 words. Where to report, what happens meanwhile, a pointer for the cost question, and the loss or theft reporting expectation with a named contact.
What you may do with it: 150 words. Reasonable personal use with three or four named exclusions, one sentence on family use with its reason, the software installation position, and three practical lines on travel.
At the end: 100 words. When the conversation happens, who books the collection, that the device will be cleared and personal files should be removed first, what is not expected back, and a pointer for obligations.
Then one heading above all four so somebody searching for equipment, laptop or computer lands in the right place. Because people arrive at this content through a search rather than by reading in order, the heading does more work than the structure does, and a section called Company Equipment will be found while one called Asset Management will not.
And give it a review date with an owner, in line with however your handbook is maintained. Four clauses that were accurate in March and describe a loaner arrangement that ended in June are worse than no clauses, because somebody will rely on them.
How to Choose: Five Questions Before You Write
Which of the four questions has reached somebody senior twice? Start there. It is the one with demonstrated demand and the easiest to justify spending an afternoon on.
Does the operational answer exist? For each clause, particularly the loaner. If not, decide the arrangement first, because a handbook cannot describe something that is not there.
Where is the liability position actually written, and is it current? You need to point at it, which means finding it. A surprising number of companies discover at this moment that it is written in two places that disagree.
Is there a single equipment page to link to? If not, create it, because it is what allows the handbook clauses to stay short and stable while the detail moves.
Who owns the review? The same person who owns the rest of the handbook, not IT. Equipment content maintained by a different team than the document it sits in is content that goes stale.
The Travel Lines Worth Writing
The travel part of clause three deserves expanding, because it is the one place where a handbook can give genuinely useful information that people cannot work out for themselves and will not think to ask about until it is too late.
Four practical notes, one line each.
Warranty and service are frequently regional. A machine bought in one region may not be serviceable under the same terms in another, which matters for somebody on a long trip or relocating. Saying so in advance costs nothing and prevents somebody discovering it in week three of a secondment.
Some destinations have specific restrictions on equipment or encryption. What applies where differs by country and changes, so the handbook line should point at a route to check rather than attempt a list. A list in a handbook will be out of date and relied upon, which is the worst combination.
Insurance coverage may differ when a device is out of its usual country. Again a pointer rather than an assertion, naming who to ask before a long trip.
Say whether notification is wanted, and if so, to whom. If your security arrangements benefit from knowing a device will be in a different country for a month, that is worth one sentence. If they do not, say nothing rather than adding a step nobody uses.
Then the one piece of practical advice that belongs here and nowhere else: take the charger and a spare adapter, because the single most common equipment failure on a trip is a power problem rather than a device problem. It sounds trivial in a handbook and it is the thing that most often ruins a day away from a desk.
What any of this means legally, and what obligations sit with anybody, varies by jurisdiction and by circumstance, so the handbook should be routing people to advice rather than giving it. The value here is in the four things people would not think to check, not in the answers.
Making the Section Findable
Four well-written clauses in a place nobody finds are four clauses that do not exist, and findability in a handbook is a specific and solvable problem that almost nobody addresses.
People arrive at this content in three ways and only one of them involves reading.
A search, which is the main route. Somebody types laptop, computer, equipment or broken into whatever search your handbook has. So the heading needs to contain the words people use rather than the words the company uses internally. A section called Company Equipment will be found. One called Asset Management or IT Resources will not, because nobody searches for the name of a function.
A link from somewhere else, usually onboarding. Which means the onboarding checklist should link directly to this section rather than to the handbook generally, and the link should survive a handbook reorganisation. Where your tooling supports named anchors, use them.
Being told by a colleague, which is the route you are trying to eliminate. Every instance of somebody being told where to look is an instance of the search having failed, and it is worth asking two or three recent joiners whether they found it.
Three cheap improvements.
Put the four questions in the body as headings, in the words people would use. What equipment will I get. What if something breaks. Can I use it for personal things. What happens when I leave. Those are searchable strings and they are also the questions, which means a search result preview answers the question before somebody has clicked.
Add the obvious synonyms somewhere in the text. Laptop, computer, machine, device, hardware, kit. Not as keyword stuffing but because people search with their own vocabulary and one of those words will be theirs.
Test it. Search your own handbook for broken laptop and see what comes back. Because the test takes ten seconds and almost nobody runs it, this is the cheapest quality check available on the whole document, and a surprising number of handbooks return nothing useful for the most common equipment question there is.
Deciding the Loaner Question First
The handbook cannot describe a loaner arrangement that does not exist, and this is the one clause where the documentation task is downstream of a real decision. So it is worth settling before you write anything.
Four options, and the right one depends almost entirely on whether you have a building.
| Arrangement | Right when | Typical wait | What the handbook can promise |
|---|---|---|---|
| A spare pool at the office | There is an office most people can reach | Same day | A machine today, collected in person |
| A regional spare held by a platform | Distributed fleet, no office | 2 to 4 days | A machine this week, shipped |
| Repair with no loaner | Small team, nothing time-critical | However long the repair takes | Honestly, that there is no loaner |
| Replace rather than repair | Older fleet, repairs cost more than residual value | Same as a new order | A replacement, with the lead time stated |
Fund the pool from recovered machines rather than new purchases. A device coming off the main fleet is ideal for a loaner: it only has to work for a week or two, nobody is choosing it, and it costs nothing because you already own it. Two or three machines covers most companies.
Say the honest answer if there is no loaner. A handbook that admits somebody will be without a machine for four days is far more useful than one that implies a replacement appears. The reader can plan, borrow a meeting room machine, or shift work, and none of that is possible if they are waiting for something that is not coming.
Keep the loaner machines wiped, charged and labelled as ready. A pool that needs a day of preparation is not a same-day pool, and the preparation will not happen on the morning somebody needs it.
And decide who authorises one. If the answer is a ticket queue with a stated turnaround, the handbook can name it. If the answer is somebody's judgement, the handbook can only say to ask, which is where this article started.
The Single Equipment Page the Handbook Points At
Keeping the handbook short depends on there being one place for the detail, and that page is doing more work than the handbook section is.
| On the equipment page | Why not in the handbook |
|---|---|
| Exact specifications by tier | Changes quarterly; a handbook changes rarely |
| Named models and alternates | Changes with supply, sometimes monthly |
| The full on-request catalogue | Long, and grows |
| Lead times by market | A live figure, worth publishing and updating |
| The request form or ticket link | Routes change without the policy changing |
| The current loaner stock position | Operational, and useful to see |
One page, one owner, one review cadence. The handbook links to it by name rather than by URL where your tooling allows, because links rot and a named page is findable even after a reorganisation.
Give the page a change log at the bottom. Three lines: what changed, when, and who approved it. This matters more than it sounds, because the most common objection to moving detail out of a handbook is that the handbook had a version history and the new page does not. A change log answers it in about twenty words per entry.
Make the page readable by everybody, not just by requesters. A specification page that requires a login people do not have is a page the handbook should not link to. If the detail is genuinely internal, that is fine, and the handbook should then summarise enough that somebody without access is not stuck.
So the arrangement is a short, stable handbook section plus one living page, and the handbook survives a hardware change without a revision. Because the alternative is an equipment section that has to be reopened every time a model changes, most companies simply stop updating it, which is how a handbook ends up describing a laptop nobody has had for three years.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Equipment section is 200 words of policy language | Any | Four clauses, roughly 500 words | Establishes a position, answers nothing | Rewrite to the four questions, with budgets |
| Handbook already runs to 60 pages | Any | Short section plus one linked page | Adding content makes it less usable | Make the section route rather than answer |
| No loaner arrangement exists | Under 100 | Two or three recovered machines as a pool | A clause that cannot honestly be written | Decide the arrangement, then write it |
| Distributed fleet, no office | Any | Regional spare via a platform | Same-day loaner is not available | Promise the real timescale, not an aspiration |
| Liability position written in two places | Any | One source, pointed at | Two documents that disagree | Reconcile them before pointing at either |
| Handbook describes a three-year-old laptop | Any | Detail moved to a living page | Nobody reopens the handbook for a model change | Link instead of copy, with a change log |
| Same question reaching somebody senior twice | Any | The specific missing clause | A conversation standing in for a document | Write that one clause this week |
| Setups differ by who asked confidently | Any | Standard bundle published as a list | Unwritten standards tracking confidence | Publish the two lists, standard and on request |
What Getting This Wrong Costs
The visible cost is the four-person, three-day charging cable, and it repeats quietly across every company that has not written these clauses.
The second cost is uneven treatment, and it is the one that matters. When the standard bundle is not written down, what somebody receives depends on what they thought to ask for and how comfortable they were asking. Because every individual decision was reasonable, the pattern is invisible until somebody compares two people's setups, and the pattern will correlate with confidence rather than with need. That is a fairness problem produced by a documentation gap rather than by anybody's intent.
The third is the loss that was not reported promptly. A device holding company data goes missing, the person is not sure who to tell or how urgent it is, and they mention it the following week. The handbook is exactly where somebody looks at that moment, and a single sentence naming a contact and an expectation is the cheapest control in this whole article.
The reframing question: if somebody's laptop failed this afternoon, could they find out what to do without asking a person, and would two different people get the same answer?
When You're Ready to Write It
The honest position is that this is a short piece of writing that keeps not happening because it sits between HR, IT and whoever owns the handbook, and all three can see most of it while nobody owns the whole.
The trigger worth acting on is a question arriving twice. Not a complaint and not an audit. The same practical question reaching somebody senior for the second time tells you a clause is missing and tells you which one.
The sequence costs an afternoon. Write down the four questions and find out whether your company has an operational answer to each, because the loaner question in particular is often a decision rather than a documentation task. Find where the liability position is written and check it is singular and current. Create or identify the single equipment page the handbook will link to. Then write the four clauses to the word budgets above, under a heading somebody searching for laptop will actually find.
Do that and the charging cable becomes a two-minute matter rather than a three-day one. And the standard bundle stops being something people discover by comparing notes with a colleague.
Frequently Asked Questions
What should an employee handbook say about company equipment?
Four things, in about 500 words total. What you get, as a standard list plus a separate on-request list with a route and a turnaround. What happens if it breaks, including where to report it, whether a loaner exists and the loss reporting expectation. What you may do with it, meaning a reasonable personal use position with named exclusions, family use, software installation and travel. And what happens at the end, including who books the collection and that the device will be cleared.
What is the difference between a handbook and an equipment policy?
Their reader and their test. A handbook is read by somebody with a question, usually in a hurry, and its test is whether they can act afterwards. A policy is read by whoever administers the thing or checks a decision, and its test is whether two administrators would reach the same answer. Most equipment content is written as policy and filed as handbook, which produces a section that establishes the company's position and answers none of the questions people actually arrive with.
Should a handbook ban personal use of a work laptop?
A blanket prohibition is ignored, because essentially everybody checks personal email and reads the news on a work machine, and a rule that makes most of the workforce technically non-compliant cannot be enforced selectively without appearing arbitrary. Silence is worse, since it leaves each person to decide. State a reasonable-use position allowing incidental personal use, then name the three or four specific things that are not acceptable, because the named exclusions are the part people could not have guessed.
Does the handbook need to cover family use of a work device?
One sentence, and it is the case nobody writes down while a great many people do it, particularly with a laptop at home. Without it, whether somebody's partner can borrow the machine for an hour is a decision made by the person holding it. The honest version for most companies is that the device is for the employee's use only, given with the reason, because a rule accompanied by a reason is followed considerably more often than a bare prohibition.
Can a handbook state that unreturned equipment will be deducted from pay?
This is exactly the kind of statement to keep out of a handbook and to take local advice on, because what may be recovered, in what circumstances and with what consent differs by jurisdiction and by the terms involved. A handbook paragraph asserting a position may be both unenforceable for some readers and alarming for all of them. Write the handbook line as a pointer naming where the position is properly set out and who to speak to about it.
How do you stop handbook equipment content going out of date?
Link rather than copy. Keep exact specifications, memory and storage figures and model names in a single equipment standard that is reviewed quarterly, and have the handbook summarise the bundle and point at that page. The handbook clauses themselves should then be stable for years. Give the section a review date with an owner, and make that owner whoever owns the rest of the handbook rather than the IT team, since content maintained by a different team than its host document goes stale.
What is the single most valuable equipment clause to add?
What happens if it breaks, which is the most asked question in this area and the most commonly absent. Four facts in roughly eighty words: where to report it, what happens in the meantime including whether a loaner exists, a pointer for the cost question, and the expectation for reporting a lost or stolen device with a named contact. The loss reporting line alone is the cheapest meaningful control available, because the handbook is precisely where somebody looks at the moment it happens.
HROpsLab takes no vendor money and publishes no paid placements, which is why this article says plainly which statements it will not make rather than making them badly.