Put the full location of the unit on the ticket before anyone rolls. Microsoft describes a work order location with this example: "Room 1 is on Floor 2 of Building A at Campus Z." That is the shape of the field. Floor, building, room or yard position, and any landmark the tech will look for on arrival.
Location matters more than it sounds. A chilled warehouse with retail refrigeration, a rooftop unit over a grocery floor, and a chiller in a mechanical room are different jobs. The EPA lists where HCFC-22 shows up in the field: unitary air conditioners, cold storage, retail food refrigeration equipment, chillers, and industrial process refrigeration. That spread is why the location line has to say where the unit actually sits, not just which account is calling.
Write it the way a person who has never been to the site will read it. The Microsoft example carries the whole idea: floor, building, campus or site, and room. If the unit is on a roof, say the roof and the access point. If it sits behind a locked gate, note the gate and who holds the key. If there is more than one unit at the site, number them or name them the way the customer names them.
A vague location line turns into a phone call on arrival. The tech stands in the parking lot and rings dispatch, and the clock starts over. Filling the field properly on intake costs a minute and removes a whole category of delay.
What the location field should carry, from intake through to arrival on site:
- Floor, building, and room, or yard and pad position for outdoor equipment
- Site name as the customer knows it, plus any campus or complex identifier
- Access details: gate, roof hatch, locked room, contact on site
- Unit identifier if the site has more than one machine
- Anything a driver needs to park or stage near the unit
Keep it in one place. Location notes buried in a free-text comment at the bottom of the ticket get missed. Structured location fields on your own work order form are worth using the way they were designed.