Break/fix work starts with something that has stopped working: a till that will not boot, a printer that jams, a camera that has gone dark. The site wants it back quickly, so the temptation is to send someone at once and explain later. The explanation is what makes the first visit count.
Describe the fault, not just the device
Say what the equipment is doing, when it started and what has already been tried. "The terminal restarts when a card is inserted, since this morning, power cycled twice" tells a technician far more than "terminal broken". Include the make, the model and any asset tag, so the right knowledge and the right parts travel with them.
Settle the parts question before the visit
State whether a replacement part is on site, being shipped, or expected to come with the technician. A technician who arrives to find the part missing can diagnose but cannot finish, and a second trip is the most common reason a simple repair takes days.
Make the site easy to reach
Give the site-access detail the technician will need once assigned: who to ask for, where to sign in and which door to use. Name someone at the site who can confirm the fix, and say what "fixed" means, so the work can be approved when the technician leaves rather than argued about afterwards.
None of this takes long to write. It is the difference between a work order that describes a problem and one that lets a stranger solve it.
