Write specifications around outcomes, not brand names
A specification that names one manufacturer and model invites a single-source price and complicates the evaluation. Describe what the equipment must do — processor class, memory, storage type and capacity, display size and resolution, connectivity, operating system, and the warranty term — then state that documented equivalents are acceptable.
This keeps the field open enough to be competitive while giving the evaluation committee objective criteria. It also produces a specification you can defend later, because every line ties to a requirement rather than a preference.
Standardise the fleet
Where you are equipping a department or a whole site, resist the temptation to buy the cheapest option at each price point. Two or three standard configurations, chosen per role, dramatically simplify deployment, driver management, spare parts, and warranty tracking over the life of the equipment.
Standardisation also makes the next procurement easier: you can describe what is already in service, what it is used for, and what is due for replacement.
Plan power, network, and physical security first
Equipment fails to deliver value when the environment around it is not ready. Before delivery, confirm the number and position of power points, whether surge protection or a UPS is required, the state of structured cabling, switch port count, and where the internet connection actually terminates.
Physical security matters too: lockable cabinets or server enclosures, cable management that survives cleaning staff, and a room that is not a corridor. These are cheap to arrange before installation and expensive to retrofit afterwards.
- Power points, surge protection, and UPS requirements per location.
- Structured cabling and switch ports, tested and labelled.
- Lockable storage or enclosures for high-value items.
- Cooling and dust control for server or network equipment.
Ask for an asset register and warranty schedule
A rollout is not complete when the boxes are opened. Require, as part of the contract, a delivered asset register listing serial numbers, locations, assigned users, and configuration, plus a warranty schedule showing the end date for each unit.
Those two documents turn an inventory problem into a lookup, and they make warranty claims possible years later when the original delivery note is long gone.
Make installation and handover contractual
Specify who installs, who configures, who tests, and who trains users — and what evidence counts as acceptance. A short handover pack (asset register, warranty schedule, admin credentials, and a simple user guide) is a reasonable deliverable to require, and it gives you something concrete to accept against.
Where the rollout spans several sites, agree the sequence and the delivery windows in advance so that each site has someone available to receive, verify, and sign.