TL;DR
Equipment for apprentices and graduate intakes is not a scaled up version of equipping one joiner. Twenty people start on the same morning, most leave or convert on the same date, and the process built around individual hires handles neither. Treat the cohort as one project with one deadline.
- One start date means one deadline, not twenty independent ones.
- Specification can usually be lower and more uniform than for senior roles.
- The end date is known at the start, which almost never happens otherwise.
- Returns arrive in one wave too, and storage is the bottleneck.
- Redeployment to the next cohort is the obvious move and rarely planned.
The moment this becomes real
Say you take on eighteen graduates every September. The hiring is handled months ahead and everybody is pleased with how organised it looks.
In the last week of August, eighteen equipment requests arrive in the IT queue at once, each as an individual ticket, each needing approval under a process designed for one person at a time. Procurement asks why this was not flagged earlier. It was, in the hiring plan, which IT does not see.
Best tools for HR Operations
Fourteen machines arrive in time. Four do not. The real issue is not the four laptops. It is that a predictable annual event with a fixed date was handled as eighteen unrelated surprises, because the only workflow available treats every joiner as an individual.
When this is lighter than you think
Four stages where this needs no special handling.
- Two or three people at a time. Your normal joiner process copes. A cohort becomes a different problem somewhere around five.
- Office based intakes. Machines can be handed over in a room on day one, which removes the hardest part.
- You already hold spares. A spare pool absorbs a small cohort without any forward planning at all.
- Bring your own device programmes. Some apprenticeship and university linked schemes work this way, which changes the question to access rather than hardware.
It gets heavy with intakes above about ten, with remote cohorts spread across locations, and anywhere the same thing happens every year without anybody writing it down.
The five questions teams actually ask
What specification do they need? Usually less than a senior hire, and more uniform. A cohort doing similar work on similar tools is the easiest group in the company to standardise, which makes buying simpler and makes redeployment later much easier.
When does IT find out? This is the actual problem in most companies. Recruitment knows the cohort size and date months ahead and the information does not reach whoever buys hardware until the requests arrive. One calendar entry fixes more here than any process change.
What happens at the end? Unusually, you know. A fixed term apprenticeship or a graduate scheme has an end date from day one, so unlike almost every other population you can plan the return before the start. Very few teams do.
Where do returned machines go? Eighteen laptops coming back in one week need somewhere to sit, be wiped and wait for the next intake. Without a plan they end up in a cupboard or with managers, and by next September nobody can find them.
What if they convert to permanent? Some will, and it is worth deciding in advance whether they keep the same machine. Usually yes, and the record needs updating to reflect that the end date no longer applies.
Three ways teams handle it, and where each breaks
Treat each joiner individually. The default, because that is what the system does. No change required. It breaks on timing: eighteen simultaneous requests overwhelm an approval process built for a trickle, and the last few always arrive late.
Bulk order against the hiring plan. Buy for the cohort as one order when the intake is confirmed. Much better. It breaks when the cohort shrinks and you are holding machines nobody needs, which is why ordering against accepted offers rather than planned headcount matters.
Maintain a cohort pool. A set of machines that cycles between intakes: issued in September, returned, wiped, reissued the following year. Best economics by a distance. It breaks on storage and on discipline, since the pool evaporates if machines leak out to other uses.
Five questions before the next intake
Planning equipment for apprentices properly takes five answers and one calendar entry.
When does IT learn the cohort size? If the answer is when the tickets arrive, that is the whole problem.
What is the agreed specification? Decide once per cohort, not per person.
Where will returns be stored? Answer before September, not in the following July.
Who owns the end date? Somebody should hold the return date for the whole group.
How many converted last year? That tells you how many machines actually come back.
What is actually available
Five honest options, including ours.
Individual requests as normal. Best for very small intakes. No change needed. Struggles above a handful, where the approval queue becomes the constraint.
A single bulk order. Best for most teams. One approval, one delivery, one deadline. Struggles if placed against planned rather than accepted headcount, leaving surplus machines.
A cohort pool you own and cycle. Best economics for annual intakes. Machines earn their value across several cohorts. Struggles on storage between cycles and on the pool being raided for other needs.
Short term rental or leasing. Best where the end date is firm and you would rather not own idle machines. Struggles on cost per device and on return condition terms.
RemoAsset. Best where cohorts are remote and spread out, because the whole group needs delivering to a date and collecting to a date, and storage between assignments plus retrieval cover the part where eighteen machines come back at once with nowhere to go. Where it struggles: for an office based intake where everyone collects a laptop in a room on day one, this is far more machinery than the problem needs. Its published pricing starts with a pay as you go plan and a yearly subscription above it.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Occasional apprentices | 1 to 4 a year | Normal joiner process | Very little | Handle as individual joiners |
| Annual intake, office based | 10 plus | Office handover | Approval queue congestion | One bulk order against accepted offers |
| Annual intake, remote cohort | 10 plus | No office | Delivery to a date | Bulk order plus coordinated delivery |
| Repeating intake every year | Any | Machines returning | Returns scatter | Build a cohort pool with managed storage |
| Fixed term with known end | Any | Any | Nobody owns the return | Diarise the collection on day one |
What the gap actually costs
Late machines are the visible cost, and on a graduate intake they are more damaging than usual. These are often people’s first days in their first job, and the ones without a laptop spend that week watching other people work.
The larger and quieter cost is the return. A cohort that arrives as a planned project and disperses as eighteen individual departures leaves equipment scattered, and because everybody knew the end date, nobody felt responsible for it. Those machines are the easiest in the company to recover and frequently the ones most often lost.
The third is the opportunity. A cohort is the one population where a machine can reliably serve several users, because the specification is uniform and the turnover is scheduled. Buying new every September for a group whose laptops come back in July is paying twice for the same requirement. So the question is not how to equip this intake. It is whether last year’s machines are available for this one.
When the cupboard decides the economics
Everything attractive about a cohort pool depends on one unglamorous thing: somewhere to put eighteen laptops for two months between intakes, wiped and ready. With that, the economics are obvious. Without it, the pool idea dies and you buy new every year.
Office based teams solve this with a cupboard and barely notice it is a decision. Distributed teams have no cupboard, so returned machines go to whichever manager is nearest and are not seen again, which is why remote cohorts almost never get redeployed.
That is the gap a laptop lifecycle management service fills, by making collection, storage and reissue a scheduled sequence rather than a favour. It is worth noting the cheap version first though: if your intake is office based, a locked cupboard and a named owner achieves the same thing for nothing.
See how devices are stored and reissued between cohorts
Read our guide to equipment for fixed term staff and interns
Related reading
- Equipment for fixed term staff and interns
- Equipment for seasonal hiring
- Setting a hardware refresh cycle
- Designing an equipment approval workflow
- Apprenticeship frameworks differ by country. The UK government publishes guidance on employing an apprentice, and the ILO covers apprenticeships.
Frequently Asked Questions
How is equipment for apprentices different from a normal joiner?
Volume and timing. A cohort starts on one date, which turns twenty independent requests into one deadline, and it usually ends on a known date too. Almost no other population gives you the end date on day one, which makes planning the return genuinely possible.
What specification do apprentices and graduates need?
Usually less than senior hires and, more usefully, the same as each other. A cohort doing similar work on similar tools is the easiest group to standardise, which makes bulk buying simpler and makes redeploying machines to the next intake far more practical.
Should we buy new machines for every intake?
Not if the previous cohort’s devices come back in usable condition. A pool that cycles between intakes spreads the cost across several years of use. The constraint is somewhere to store machines between cycles, which is what usually decides whether this works.
When should IT be told about an intake?
As soon as the cohort size and start date are known, which is usually months ahead in recruitment and reaches IT far too late. A single recurring calendar entry shared between recruitment and whoever buys hardware fixes more than any process redesign.
How do we avoid losing devices when a cohort ends?
Diarise the collection on day one, as a group rather than as individuals. The whole cohort leaves within the same short window, which is the easiest recovery scenario you will ever have, and it is frequently missed because everyone assumed somebody else owned it.
What if an apprentice converts to a permanent role?
Usually they keep the machine, which is simplest and avoids an unnecessary swap. Update the record so the cohort end date no longer applies to that device, otherwise your collection list in July will include someone who is still working there.
Is leasing better than buying for fixed term cohorts?
It can be, because the term matches the engagement and you avoid owning idle machines. Weigh it against cost per device and the return condition terms, which is where these arrangements get expensive if a cohort of young users returns equipment with ordinary wear.
