Procurement and Receiving

An asset that enters the organisation without being registered is unlikely ever to be registered. The receiving process is where hardware asset management succeeds or fails.

The receiving checklist

Record the asset before it leaves the goods-in area: serial, model, purchase order, cost, supplier, warranty term.

Tag it.

Photograph the serial plate.

Set status to in stock.

Enrol it in management, or record that it is pending enrolment.

Five steps, two minutes, and they are the difference between a register and a guess.

Direct-to-user delivery

Increasingly common with remote workforces and it breaks the receiving process entirely.

The device never passes through a place where anyone could tag it.

Options: ask the supplier to tag and register on your behalf, which many will do for a fee; ship pre-tagged labels to the user with instructions; or accept that tagging happens at first support contact and rely on serial numbers in the meantime.

Zero-touch enrolment solves the management side: the device enrols itself on first boot, which gives you the serial and the assignment automatically. This is the strongest available control for distributed fleets and it requires buying through channels that support it.

Record the shipment, with tracking, as a provisional asset record that is confirmed when the device checks in.

Purchase data that matters later

Warranty term and expiry, which drives repair decisions.

Supplier and order reference, for claims.

Cost, for depreciation and for replacement planning.

Configuration, because "a laptop" is not enough when someone asks what they can be issued.

Buying standard, which is the field that makes fleet management possible.

Standardisation

The procurement decision with the largest downstream effect.

Few models, chosen deliberately. Spares are interchangeable, images are simpler, support knows the hardware, and buying power concentrates.

Refresh becomes predictable when the fleet is three models rather than thirty.

Exceptions handled explicitly, with a reason recorded, rather than by whoever ordered.

An estate of many models accumulated by individual choice is more expensive to support than the saving on any individual purchase.

Stock

Hold some, sized to your joiner rate and lead times.

Count it quarterly, physically.

Rotate it. Devices sitting in stock for two years lose warranty and value while unused.

Record stock as assets, in stock status, not as an unrecorded pile. Uncounted stock is where reconciliation discrepancies originate.

The control that works

Purchase orders for IT hardware routed through one place.

Not to create bureaucracy, but because it is the only point at which an asset can be reliably captured. Where teams buy directly, the register will always lag and the reconciliation will always find surprises.

Where direct purchase is permitted, require registration as a condition of expense approval, which puts the control with finance where it is enforceable.

Choosing a standard configuration

Standardisation delivers more than purchase discounts, and it requires deciding what the standard is.

Two or three laptop configurations, not one. A light configuration, a standard one, and a high-specification option for roles that need it.

Written eligibility, so the high-specification option is assigned by role rather than by who asks.

One docking and display standard, which is where most of the peripheral cost and support load sits.

A refresh interval per configuration.

Reviewed annually, because models change and the previous standard becomes unavailable.

Publish it. A visible standard reduces the negotiation on every individual request and makes the exception process meaningful.

Zero-touch, and what it constrains

Self-enrolling devices are the single most useful capability for a distributed fleet, and they narrow where you can buy.

The device registers to your organisation at the manufacturer or reseller, then enrols itself on first boot.

It gives you serial, model and assigned user automatically, which is the receiving process without a receiving area.

It requires buying through channels that support it, which excludes some retail and marketplace purchases.

It requires the purchase to be linked to your organisation at the point of sale, which is a configuration exercise with each supplier.

Set it up once per supplier and it removes most of the direct-delivery problem permanently. Buying the same machine from a cheaper source without it costs more in unregistered assets than the price difference.