TL;DR
- Three places this can live and only one of them is a good idea. The careers page recruits, the pre-start email informs, and the offer letter commits you.
- Promise a capability and a choice set, never a named model. Models go out of stock and offer letters are documents people keep.
- For technical hires, choice of machine is a genuine recruiting signal. It also costs you fleet standardisation, and that is a real trade rather than a free win.
- The acceptance date is your order trigger in any market with a long lead time, whether or not anybody has designed it that way.
- What candidates actually ask is four questions. Answer all four in one findable place and most of this problem disappears.
- The commonest failure is a recruiter promising something verbally that procurement cannot supply, and a one-page brief prevents it.
The Model That Was Out of Stock
A company put the laptop model in its offer letters. It read well, it was specific, and candidates liked it.
Then the model was superseded. The replacement was better in every respect and had a different name, and for about five months the company was sending offer letters naming a machine it could no longer buy, because the template lived with the recruiting team and the supply change happened in IT.
Three people noticed on their first day. Two did not mind. One had taken the role partly on the strength of that specification, had told friends which machine they were getting, and arrived to something unfamiliar with a different keyboard. Nobody had misled anybody and the company had still broken a written promise, because it had put a fact that changes quarterly into a document designed never to change.
Best tools for HR Operations
The fix was two sentences and a different location. The offer letter now names a tier and a choice, the careers page describes the kit in the kind of detail candidates actually want, and the pre-start email confirms the specific machine once it has been ordered. Nothing was lost in recruiting terms and the promise became one the company could keep.
The Three Places It Can Go
| Location | What it does well | What it costs you |
|---|---|---|
| Careers or benefits page | Recruits. This is where candidates look before applying | Nothing, and it can be updated any day |
| The conversation, via a recruiter brief | Answers questions as they arise, with accuracy | Needs a brief, or it becomes improvisation |
| The offer letter | Signals that you take it seriously | Commits you in writing to something supply controls |
| The pre-start email | Confirms the actual machine, accurately | Too late to be a recruiting signal |
The pattern that works uses three of the four. Recruit with the careers page, answer questions from a brief, and confirm specifics in the pre-start email. Keep the offer letter at the level of the tier and the choice, because that is the part you can guarantee.
Whether and how an offer document creates obligations differs by jurisdiction and by how your documents are drafted, so take local advice on what belongs in yours. The operational point stands regardless: a named model in a document you cannot amend easily is a promise against a supply chain you do not control.
What to Promise, and at What Level
Four levels of specificity, and the right one is the third.
A vague statement. All the equipment you need. Means nothing, answers nothing, and reads as evasive to exactly the candidates who care.
A category. A laptop and a home setup allowance. Better, and still not useful to somebody choosing between offers.
A capability and a choice set. A current-generation laptop with a stated memory and storage configuration, from a choice of two or three machines, plus a named peripheral bundle. This is the level that is both specific enough to be meaningful and stable enough to keep.
A named model. Specific, attractive, and the thing that broke in the opening example.
So write the third level into anything durable. Because a capability statement survives a model change and a model name does not, this single choice removes the entire category of failure described above, and candidates who care about hardware read a memory and storage figure as a more serious answer than a product name anyway.
And state the choice set as a set rather than as a default with alternatives available on request. A choice presented as a request is not a choice, and the people who ask will not be representative of the people who care.
Why Choice Matters More Than Specification
Worth understanding before deciding how much to invest in this, because the recruiting value is not where companies assume it is.
For most roles, equipment is a hygiene factor. Candidates want to know they will not be given something inadequate, and a clear statement satisfies that in one line. It will not win anybody over and its absence will not lose anybody.
For technical roles it is different, and the thing that matters is choice rather than specification. The difference between two capable machines is small; the difference between being asked which you prefer and being handed whatever is standard is a signal about how the company treats the tools people work with. That signal is read accurately, because a company that lets engineers choose their machine usually also lets them choose other things.
This is the point at which you have to be honest about a trade rather than claiming a free win. A choice set of three machines across two operating systems is a genuine recruiting advantage and it costs you fleet standardisation, which means more dock types, more spares lines, more support knowledge and more resale batches. Those are real costs and they are worth paying in a competitive technical market and not worth paying everywhere.
The usual sensible position is a choice of two within one operating system for most roles, and a wider choice for the roles where you are competing hardest. Say which roles get which, because an undocumented variation will be read as favouritism.
When Not to Put It in Writing Anywhere
When you cannot reliably deliver on day one
If equipment arrives late in two of your markets, do not make a day-one promise in those markets. Say what the arrangement is honestly, including the expected timing, because a candidate told to expect a machine in week one who gets it in week three has had a worse experience than one who was told week three from the start.
When the answer varies and you have not decided why
A choice set that depends on who asks, or a specification that depends on the hiring manager, should not be written down until it has been settled. Writing down an inconsistent arrangement makes the inconsistency visible and quotable.
When the role is short or the engagement is unusual
For a twelve-week engagement or a contract through a provider, the equipment arrangement may legitimately be different, and putting the standard promise into those offers creates an expectation you will not meet. Handle them separately and briefly.
The edge case that forces the full treatment
A competitive technical hire who asks the question in a first conversation. That is the signal that this has recruiting value in your market, and it is also the moment a recruiter without a brief will improvise an answer somebody will have to honour.
The Four Questions Candidates Actually Ask
Answer these in one findable place and the rest of this becomes straightforward.
Do I get a choice, and from what? The one that matters most to the people for whom this matters at all. State the set.
What is the specification? Memory and storage figures, which is what somebody technical is really asking. Screen size if it varies.
How soon will I have it? Honestly, by market if it differs. This is the answer most often fudged and the one that most affects somebody's first week.
What about a home setup? Whether there is a bundle, an allowance or both, and what it covers. For a remote or hybrid role this is often a bigger question for the candidate than the laptop and it is more often omitted.
Then a fifth that nobody asks and some candidates care about: whether they can keep or buy the machine at the end. If you run a purchase scheme, saying so is a small and unusual differentiator. If you do not, say nothing.
The Acceptance Date Is Your Order Trigger
This is the operational consequence that catches companies out, and it has nothing to do with wording.
In a market where the lead time is 5 weeks, a machine ordered when onboarding starts will arrive in week three or four of employment. The only date early enough to order against is the acceptance date, which means the recruiting process and the procurement process are coupled whether or not anybody designed them that way.
Three things follow.
Somebody has to be told when an offer is accepted, with the market and the role. Not the whole offer, just the three facts that trigger an order. This is the same shape of integration as the absence trigger: a small, specific payload from a system with sensitive data.
The tier has to be known before the order, which means it has to be on the role definition. If the tier is decided by a conversation after someone accepts, the order waits for that conversation and the lead time starts late.
You will sometimes order for somebody who does not start. Offers fall through, and a company ordering at acceptance will occasionally hold a machine for nobody. That is not waste, it is the first item in your spare pool, and treating it as a loss is what pushes companies back to ordering too late.
So the honest version is that ordering at acceptance costs you a small number of unused machines a year and buys you day-one readiness in your slowest markets. For most companies that trade is obviously worth taking, and it is never made explicitly.
Briefing the Recruiters
The cheapest intervention in this article and the one that prevents the most damage.
A recruiter asked about equipment will answer, because declining to answer looks evasive and they are trying to sell a role. Without a brief they will answer from whatever they remember, which may be a year old, or from what they have heard another company offers.
One page, kept with the other role-specific material.
The capability statement, verbatim. The exact sentence they can use, so the wording is consistent across every conversation and matches whatever is written down.
The choice set, by role family. Which roles get which options, and why, so a recruiter can explain a difference rather than apologise for it.
The honest timing, by market. Including the markets where it is slow. A recruiter who knows it is 4 weeks in a particular market can set the expectation rather than discovering the problem on day one.
The home setup answer. Bundle, allowance or both, and what it covers.
What not to say. Specifically, no model names and no promises about choice beyond the set. This line is the point of the document.
And update it when the equipment standard changes, which is the link that was missing in the opening example. Because the brief lives with recruiting and the standard lives with IT, the update has to be somebody's explicit job rather than an assumed consequence, and that is one line in whatever process reviews the standard.
How to Choose: Five Questions Before You Write Anything
Is equipment a competitive factor in your hiring? Ask your recruiters whether candidates raise it unprompted. If they do, it is worth the careers page investment. If they do not, one clear line satisfies the hygiene requirement and you can stop.
Can you deliver on day one in every market you hire into? If not, you have a timing problem rather than a wording problem, and the honest answer in writing is better than an optimistic one.
Is the tier on the role definition before the offer goes out? If not, your order will always start late in slow markets, regardless of what the offer letter says.
Who tells procurement that an offer was accepted? Name them. If the answer is nobody, that is the gap and it is worth more than any wording change.
Do you actually want to offer a choice? Decide deliberately, because it is a real trade against fleet standardisation. A choice of two within one operating system is a reasonable default; a wider choice is a competitive instrument with a cost attached.
The Comparison
| What you write | Survives a model change | Useful to a candidate | Commits you | Right place |
|---|---|---|---|---|
| All the equipment you need | Yes | No | No | Nowhere, it reads as evasive |
| A laptop and a home allowance | Yes | Barely | Lightly | Offer letter, as a minimum |
| Capability plus a choice set | Yes | Yes | Appropriately | Offer letter and careers page |
| A named model | No | Yes | Too much | The pre-start email only |
| Day-one timing, by market | Yes, if honest | Very | Yes, so be accurate | Careers page and recruiter brief |
The third row is the recommendation and the fifth is the one that is most often missing. Candidates do not expect perfection on timing; they expect to know, and a stated 3 weeks is received far better than an implied day one that does not happen.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Model name in the offer template | Any | Capability plus choice set instead | A written promise supply can break | Change the template this week |
| Technical hiring in a competitive market | Any | Choice set of two or three, on the careers page | Equipment never mentioned to candidates | Publish the detail candidates actually want |
| Equipment arrives late in some markets | Any | Honest timing by market, in writing | An implied day-one promise that fails | State the real figure and order at acceptance |
| Recruiters improvising answers | Any | One-page brief, updated with the standard | Verbal promises nobody can honour | Write the brief, including what not to say |
| Nobody tells procurement about acceptances | Any | Three-field notification on acceptance | Orders starting at onboarding, too late | Name the recipient and the three fields |
| Choice varies by who asks | Any | Set it by role family and publish it | Variation read as favouritism | Decide the rule before writing it down |
| Short engagements getting the standard promise | Any | A separate, briefer arrangement | An expectation you will not meet | Handle them separately and say so |
| Home setup question unanswered | Any | Bundle, allowance or both, documented | The bigger question for remote candidates | Answer it on the careers page |
Finding Out Whether This Matters in Your Market
Before investing an afternoon in careers page copy, it is worth establishing whether equipment is actually a factor in your hiring, because the honest answer varies enormously by role and by market and most companies assume rather than check.
Four cheap sources, and none of them is a survey.
Ask your recruiters whether candidates raise it unprompted. Not whether candidates care, which invites speculation. Whether the question comes up without being invited, and in which role families. A recruiter running 20 or 30 technical conversations a quarter will answer this precisely and immediately.
Read the questions in your own interview feedback. Most applicant tracking systems capture candidate questions somewhere, usually in free text nobody aggregates. Twenty minutes with that field across the last two quarters is more reliable than any amount of discussion.
Ask recent hires what they had expected. Specifically the ones in the roles you compete hardest for, within their first month while the comparison is fresh. The useful question is what they thought they were getting and whether it matched, which also tests your communication rather than only the appetite.
Look at what the candidates you lost went to. You usually know, roughly. You will not get a clean answer about why, and you can see whether the companies winning against you say anything about equipment publicly.
Then weigh it honestly by role family rather than company-wide. The common finding is that it matters a lot for a small population, matters not at all for most people, and that the small population is the one where a lost candidate costs the most. Because the signal is concentrated rather than general, a company-wide conclusion will always say this is not worth doing, which is how the roles where it genuinely matters end up with nothing written down.
And if the answer is that nobody raises it anywhere, stop. One clear line satisfying the hygiene requirement is enough, and the afternoon is better spent on the timing problem, which affects everybody regardless of whether they care about hardware.
Measuring From Acceptance, Not From Start Date
The number that tells you whether the ordering arrangement works is measured from the wrong date at almost every company.
Most equipment reporting, where it exists, measures from the start date: did the machine arrive before day one. That is the outcome and it is too late to act on, because by the time you know the answer the person has already had their first week.
The number to watch is the gap between offer acceptance and order placement. If the lead time in a market is 28 days and your average acceptance-to-order gap is 11 days, you have 17 days of lead time against a start date that is usually 30 days out, and you will be late roughly half the time. Nothing about that is visible in a day-one pass rate until it has already happened.
Three things to pull, and all three are available.
Acceptance date to order date, by market. From the recruiting system and the purchase records. This is your controllable variable and the only one you can fix this week.
Order date to delivery date, by market. The supplier's performance, and the figure that goes into the recruiter brief and the careers page. Observed rather than quoted, because quoted lead times are optimistic in every market.
Start date minus acceptance date, by market. Your available runway. In some markets notice periods are long and you have 60 days of slack; in others somebody starts in 2 weeks and the supply chain cannot be rescued by any process change, which means a regional spare is the only answer.
Put those three side by side and the diagnosis is immediate. Because a long acceptance-to-order gap is a process problem and a long order-to-delivery gap is a supply problem, and they need completely different fixes, a single day-one pass rate cannot tell you which one you have.
When a Candidate Asks for Something Outside the Set
It will happen, usually from exactly the candidate you most want, and improvising is how a choice set stops being a set.
Three categories, and only one of them is a negotiation. A different machine within the same capability, which is usually cheap to accommodate and worth doing. A higher capability than the role's tier, which is the real request and should go through the same exceptions route an employee would use. And an accessibility or ergonomic requirement, which should never be handled as a recruiting negotiation and needs its own path.
Answer the first category on the spot, if you can. A recruiter who is allowed to say yes to a keyboard layout, a screen size or a second monitor is worth more than one who has to check, and the cost is trivial compared with the signal.
Route the second category rather than answering it. The honest line is that the tier is set by the work and there is a process for asking for more, which you can start now. A promise made at offer stage that an employee would have had to apply for creates a precedent somebody will discover in about 6 months.
Never improvise the third. Say it will be handled properly and route it to whoever owns that, because the worst outcome available is a well-meaning recruiter making a commitment about an adjustment they do not understand.
And record every one of these, because 10 or 12 such requests over two quarters is the clearest evidence you will get about whether the choice set is drawn in the right place. If most of them ask for the same thing, add it to the set.
Writing the Careers Page Section
If equipment is a competitive factor in your hiring, this is where the work pays off, and most companies either omit it entirely or write two vague lines. About 250 words does the job properly.
Lead with the choice, not the specification. The first sentence should say that people choose from a set, because that is the signal. The figures come second.
Give the configuration in numbers. Memory and storage as actual figures. Somebody technical reads a specification as evidence that the company thought about it, and reads a product category as evidence that it did not.
Name the peripheral bundle as a list. Monitor, dock, keyboard, mouse, headset, chargers for each location. Six items takes one line and answers a question candidates are embarrassed to ask.
State the home setup arrangement in its own sentence. Bundle, allowance or both, and what it covers. For remote and hybrid roles this is often the bigger question and it is the one most frequently missing from a careers page.
Say when it arrives, honestly. Before the first day in most markets, with the exceptions named if you have them. A page that says before your first day in 9 of our 12 markets, and within two weeks in the others, reads as a company that knows its own operation. One that implies universal day-one delivery and misses by 3 weeks reads as one that does not.
Then say what happens at the end, in one line, if you run a purchase scheme. Being able to buy the machine is unusual enough to be worth mentioning and costs nothing to state.
And put it under a heading with the word equipment or laptop in it, because candidates searching a careers site use the same vocabulary as employees searching a handbook.
One thing to leave out: photographs of the kit. They date quickly, they commit you visually to a model you may change, and they take the place of the figures that actually answer the question. A short list of specifications is both more credible and easier to keep accurate than an image of a desk.
What the Pre-Start Email Should Say
The document nobody designs, and the one that determines how the first morning actually goes.
Four things, sent 3 to 5 days before the start date.
The specific machine, by name, now that it exists. This is where the model name belongs, because by this point it has been ordered and the promise is a statement of fact rather than a commitment.
Where it is and when it arrives. A tracking reference if it is shipping, or confirmation that it will be on a desk. If it will be late, this is the moment to say so, not day one.
What they need to do on arrival. Whether it configures itself, whether a call is booked, and what credentials they will need. A machine that enrols itself is worth saying, because a new starter opening a laptop expects to be stuck.
Who to contact if something is wrong. A person or a queue, named. On a first morning nobody knows the internal vocabulary, so the handbook's ticket queue name is useless and a name is not.
And the keyboard layout, if there was a choice. A small thing that is awkward to change after the fact and cheap to confirm beforehand.
So the email is short, factual and sent late enough to be accurate. Because it is the only equipment communication that happens after the machine physically exists, it is the only one that can be fully specific, which is exactly why the durable documents should not try to be.
What Getting This Wrong Costs
The visible cost is the broken promise, and it is rare and recoverable.
The second cost is the first week, and it is neither. Somebody who arrives without a working machine spends their first days unable to do the thing they were hired for, which is the single worst available first impression and is entirely a scheduling consequence. Because the order was placed at the start of onboarding rather than at acceptance, the lead time ran out into employment, and nothing about the offer wording would have changed it.
The third is a recruiting cost you will never see measured. In a competitive technical market, a careers page that says nothing about the tools people work with is read as an answer, and the answer it suggests is that the company has not thought about it. Candidates who care do not raise this as an objection; they take the other offer. The absence of a complaint here is not evidence of anything.
The reframing question: of the people who started in the last two quarters, how many had a working machine on their first morning, and did any of them receive something different from what they were told?
When You're Ready to Write It
The honest position is that this is two separate pieces of work that get confused with each other. One is a wording decision, which takes an afternoon. The other is a timing decision, which is a process change and is where the actual benefit sits.
The trigger for the wording is a template containing a model name, or a recruiter answering the question from memory. The trigger for the timing is a single starter who waited past their first week.
The sequence costs very little. Take the model names out of anything durable and replace them with a capability statement plus a choice set. Get the observed lead time by market from whoever places orders, and write the honest figure into the careers page and the recruiter brief. Put the tier on the role definition so an order can be placed without a conversation. Then name whoever gets told when an offer is accepted, and the three fields they need.
Do that and the offer letter becomes a document you can keep, the careers page starts doing recruiting work it was not doing, and the first morning stops depending on which market somebody happens to live in.
One thing worth separating out, because it gets lost in a discussion about wording. Of everything in this article, the item with the largest effect on a candidate's actual experience is the pre-start email, and it is the one no company has a template for. The offer letter is read once and filed. The careers page is read before applying and forgotten. The pre-start email is read the evening before somebody starts a new job, when they are nervous and looking for anything concrete, and it is the only document in the sequence that can tell them exactly what is happening because the machine now exists.
So if you do one thing rather than four, write that email template. Five facts, sent four days out: the machine by name, where it is and when it arrives, what they do on arrival, who to contact if something is wrong, and the keyboard layout confirmation. It takes twenty minutes to write once and it is sent to every starter from then on.
And the wider point behind all of this is worth stating plainly. Equipment is one of very few things a company promises a candidate that is delivered physically, on a specific date, to a specific place. Almost everything else in an offer is abstract until much later. That makes it an unusually direct test of whether the company does what it said it would, and it is read that way whether or not anybody intended it to be.
Frequently Asked Questions
Should the laptop model be named in an offer letter?
No. An offer letter is a document people keep and rarely amend, while hardware models are superseded every few quarters, so a named model is a written promise against a supply chain you do not control. Promise a capability and a choice set instead: a stated memory and storage configuration from a choice of two or three machines, plus the peripheral bundle. Confirm the actual model in the pre-start email once it has been ordered, which is accurate and still arrives before day one.
Where should equipment details be published for candidates?
The careers or benefits page, because that is where candidates look before applying and it can be updated any day without touching a template. Include the choice set, the specification figures, honest timing by market, and the home setup arrangement, since those are the four things candidates actually ask. Then give recruiters a one-page brief with the exact wording to use so conversations match what is published, and keep the offer letter at the level of the tier and the choice.
Is offering a choice of laptop worth it for recruiting?
For technical roles, yes, and the signal is the choice rather than the specification, because the difference between two capable machines is small while being asked your preference says something about how the company treats working tools. It is a real trade rather than a free win: a wider choice costs you fleet standardisation, meaning more dock types, more spares lines and more resale batches. A choice of two within one operating system is a sensible default, with a wider set where you compete hardest.
When should a laptop be ordered for a new starter?
At offer acceptance, in any market where the lead time is more than about two weeks, because ordering when onboarding starts means the machine arrives during employment rather than before it. This couples recruiting to procurement whether or not anybody designed it that way, so somebody needs telling on acceptance with three facts: the person, the market and the role. You will occasionally order for somebody who does not start, and that machine becomes the first item in your spare pool rather than a loss.
What do candidates actually want to know about equipment?
Four things, and the fourth is the most often omitted. Whether there is a choice and from what. The specification, which for technical candidates means memory and storage figures. How soon they will have it, honestly and by market if it varies. And what the home setup arrangement is, whether a bundle, an allowance or both, which for a remote or hybrid role is frequently a larger question for them than the laptop itself.
How do you stop recruiters promising the wrong thing?
A one-page brief kept with the other role material, containing the capability statement verbatim so wording is consistent, the choice set by role family so a difference can be explained rather than apologised for, the honest timing by market, the home setup answer, and an explicit list of what not to say. The last item is the point of the document, and it should name no model names and no promises about choice beyond the published set. Update it whenever the equipment standard changes.
How do you measure whether the ordering process works?
Measure the gap between offer acceptance and order placement, by market, rather than the day-one pass rate. The pass rate is the outcome and it arrives too late to act on, since by the time you know the answer the person has had their first week. Pull three figures side by side: acceptance to order, which is the part you control; order to delivery, which is the supplier's performance and belongs in the recruiter brief; and start date minus acceptance date, which is your available runway and varies enormously by market.
What if equipment cannot arrive before someone's first day?
Say so, with the real timing, in the careers page and the recruiter brief. A candidate told to expect a machine in week three has a better experience than one who was implicitly promised day one and waited until week three, because the first can plan and the second spends the time asking. Then address the cause rather than the wording: order at acceptance rather than at onboarding, and hold a small regional spare pool funded from recovered machines in your slowest markets.
HROpsLab takes no vendor money and publishes no paid placements, which is why the trade-offs here are stated as costs rather than as free wins.