List the tasks, not just the hours
Describe the routine jobs you expect: rack-and-stack, cabling, reboots, hardware swaps, labelling, inventory checks, media handling. A task list lets both sides price accurately and agree what is outside scope.
Agree response levels in writing
State the response expectation for each priority and how it is measured. Be realistic about access: site permits, escorts and security checks all add time that the agreement should acknowledge.
Require evidence
Ask for a short written report after each visit with before-and-after photos, serial numbers and ticket references. Good evidence makes audits and asset records straightforward.
Tie work to change control
On-site work should follow your change process: an approved ticket, a clear instruction and a rollback step. This protects live services from well-meant but unplanned changes.
Set the escalation path
Name who the technician calls when something unexpected happens, and who can approve extra work. The first incident is a poor time to discover this.
Key points
- Write a task list, not only an hourly rate.
- Put response levels and access assumptions in writing.
- Require photo and serial-number evidence.
- Tie visits to change control and name the escalation contact.
Draft article for technical and editorial review before publication.
