The tolerated pain
A technician repeats installation steps, preferences and checks on one computer after another. The method feels flexible, particularly when departments have different needs and new devices arrive individually. The hidden assumption is that remembering and repeating the procedure costs less than maintaining a reusable setup. That assumption should be measured, not taken for granted.
Operational consequence
Manual repetition makes completion depend on both the procedure and the person applying it. Missing steps may appear later as support requests, while undocumented exceptions make comparison difficult. Separate active technician handling from unattended installation time. A device can spend a long time preparing without consuming the same amount of labour, and a quick handover can still leave unfinished work for the user.
Financial consequence
Over a defined rollout, multiply active setup hours by the loaded technical labour rate. Add separately recorded correction and user-interruption hours at their respective rates. Keep purchasing and delivery costs outside this setup estimate unless the intervention changes them. Record different device or role classes separately, since a specialist workstation may legitimately need more preparation than a standard office device.
Compare recurring and reusable work
A reusable configuration also costs money: design, testing, maintenance, exception handling and any required tooling. Compare these costs over the same device volume and planning period with the observed manual workload. Avoid assuming that automation removes acceptance testing or every exception. Released technical hours become cash savings only if they change spending; otherwise they create capacity that must be assigned useful work.
Commercial urgency
A planned refresh or repeated onboarding demand is a good point to inspect the economics because the same steps are about to recur. Prioritise high-volume, stable configurations with measurable correction effort. If device requirements change constantly or volumes are low, a maintained checklist may be more economical than a large deployment project.
Resolution
Document the minimum accepted setup for each common role, separating stable baseline requirements from legitimate exceptions. Trial a repeatable preparation method on a small representative group. Check application access, required controls and the user’s real task before handover. Record exceptions explicitly and maintain a fallback when preparation fails. Assign an owner to update the baseline when business requirements change.
Verify the improvement
Compare active technician minutes, first-use failures and follow-up tickets across comparable devices. Include the time spent maintaining the reusable method so that savings are not displaced into an invisible support task. This article concerns device configuration work; employment-driven account provisioning is a related but separate process. The commercial result is lower repeat handling with an accepted, usable setup.
Sources and method
This is a diagnostic cost model, not a client case study or an industry benchmark. It uses the operating condition described above and requires your own time, transaction and cost records. No numerical loss or saving is asserted. The related Mellorca article supplies context; the model does not rely on current product features or external statistics.