Procurement is where mobile rollouts actually stall
The technical work on a fleet refresh is rarely what delays it. The delay is in how the devices were bought, and it is almost always avoidable.
A fleet refresh has a technical plan, a communications plan and a schedule. The schedule slips anyway, and when it does the post-implementation review usually blames the migration.
In our experience it is almost never the migration. It is the devices — where they came from, how they arrived, and what state they were in when they got there.
Here is where the time actually goes.
Lead time is a design input, not a detail
Handset availability moves. A model that ships in three days in March can be eight weeks out in September, and colour and storage variants diverge from each other by weeks.
This matters because rollout plans are built backwards from a cutover date, and the device order is usually placed after the platform work is finished — which is exactly the wrong order. The order should be placed when the model is chosen, not when the environment is ready.
Two practical consequences:
- Standardise hard on one or two SKUs. Every extra variant multiplies the chance that one line item holds the whole order.
- Split the order. A staged delivery against a staged rollout means the first ring can start while the rest is still in transit, instead of everything waiting on the slowest line.
Devices arrive unenrolled unless you say otherwise
This is the single most common and most expensive mistake, and it is entirely a purchasing decision.
If the devices are not registered to your Apple Business Manager or Android Enterprise account at the point of supply, zero-touch enrolment does not happen. Somebody has to touch every handset, and a 400-device rollout becomes several weeks of manual work that was not in the plan.
Getting it right requires the reseller to be able to do it, and to be told to. For Apple that means an Apple Authorised Reseller registering the devices against your organisation as they are supplied — and for carrier-supplied handsets, a reseller with Carrier DEP capability, which is a much shorter list. We have written about how Carrier DEP works separately.
Put it in the order, in writing, with your organisation’s ABM or Android Enterprise identifier on the purchase order. Do not assume it.
The asset register is built at delivery or it is never built
Serial numbers, IMEIs, model, storage, colour, assigned user, cost centre, warranty expiry, carrier service number. Every one of those is available for free at the moment the devices are supplied, and expensive to reconstruct six months later from a spreadsheet and a stocktake.
Ask for the asset file as a deliverable of the purchase, in a format your MDM and your finance system can both ingest. It costs the supplier nothing and it is the difference between a fleet you can report on and a fleet you can only estimate.
Procurement pathway shapes the timeline more than price does
For Commonwealth and state buyers, how you buy determines how long approval takes:
- Panels and marketplaces. BuyICT and the equivalent state arrangements exist to compress the approach-to-market step. Buying through an existing arrangement removes a procurement cycle, which is usually worth more than the margin difference you are negotiating over.
- The Indigenous Procurement Policy. For Commonwealth buyers, purchases from Indigenous-owned suppliers can be made under the IPP’s exemption arrangements, which is a legitimate and faster pathway for eligible work. It is a pathway, not a discount — the value proposition still has to stand up.
- Existing contracts. A change order against an in-place managed service is faster than any new procurement, and is frequently the correct answer for a top-up or an in-year refresh.
Carrier plan and device should be separate decisions
Bundling the handset into the carrier plan makes the device look free and locks the fleet to a term that will not match its useful life. It also complicates the end of life: the devices you want to retire are financially entangled with the plans you want to keep.
Buying devices outright and buying carriage separately gives you two negotiations, two renewal dates and a clean disposal path. It usually costs less across three years, and it always costs less in flexibility.
Plan the end at the beginning
Retirement is a procurement decision made two or three years early. Whoever supplies the fleet should also be able to tell you, on day one, what happens to it at the end: data sanitisation to a documented standard, a certificate of destruction or erasure for the asset register, and a trade-in or residual value credit against the refresh.
If nobody owns that, the old devices sit in a cupboard, still enrolled, still counted in your licence numbers, still holding data.
The short version
The purchase order is a technical document. Enrolment registration, SKU standardisation, staged delivery, the asset file and the disposal path are all decided in it, and all of them are cheap to specify and expensive to retrofit.