Straight into the service manual page
WrenchQuarry
More

3 ticket fields to fill before an HCFC-22 unit visit

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

When a customer reports that an air conditioning unit is not cooling, what you write on the ticket before the technician leaves the yard decides whether that visit works. For equipment that may hold HCFC-22, or a blend containing it, three fields on the work order carry most of the weight. Fill them well and your tech shows up with the right answers, the right framing for a safe visit, and the right context on how the unit is placed at the site.

Those three fields are: the exact location of the unit, the refrigerant the unit uses, and any known hazard on the site that the crew needs to be briefed on. Each one closes a specific gap that otherwise shows up as wasted drive time, a truck turned around, or a crew working without the instruction they should have.

Field one: exact location of the unit

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.

Field two: refrigerant in the unit

The second field is refrigerant. Name it on the ticket before the visit, and if you do not know it yet, record that the answer is open and who you asked. This is the field that shapes what the tech can and cannot do on site.

The EPA describes HCFC-22 as a refrigerant in several applications: unitary air conditioners, cold storage, retail food refrigeration equipment, chillers, and industrial process refrigeration. It also notes that some HCFCs, like HCFC-22, are a component in refrigerant blends. That second point catches people out. A unit does not always carry a sticker that says HCFC-22 in plain letters. Sometimes the charge is a blend, and the blend name is what is printed.

Blends that contain HCFC-22, listed by the EPA, include R-401A, R-402A, R-408A, R-409A, R-414B, and R-502A. If the customer or a previous visit recorded one of those names, put the blend name on the ticket exactly as written. Do not swap it for HCFC-22 and do not swap it for a modern replacement. The name on the field is the name the tech matches against what the machine actually holds.

What the refrigerant field should carry before the truck leaves the yard:

  • The refrigerant name as printed on the unit or the service record
  • If it is a blend, the blend name, written in full
  • Source of the answer: nameplate, past invoice, customer report, or unknown
  • If unknown, who has been asked and when they were asked

That range covers a wide spread of substances, and HCFC-22 sits inside the Class II group the agency phases out. The practical effect on your ticket is simple. The refrigerant name is not decoration on the form. It tells the tech what the charge is, and what the charge is decides what the visit can include.

Write the answer or write "unknown" and the name of the person you called. Leaving the field blank gives the tech nothing, and a blank looks the same on a ticket as a field nobody thought to ask about.

Refrigerant names the ticket may carry

These are the substances and blends named in the sources used here, so a dispatcher reading the ticket can tell at a glance which of them the unit may hold.

Name on the ticketWhat it is
HCFC-22Refrigerant used in unitary air conditioners, cold storage, retail food refrigeration equipment, chillers, and industrial process refrigeration
R-401ABlend containing HCFC-22
R-402ABlend containing HCFC-22
R-408ABlend containing HCFC-22
R-409ABlend containing HCFC-22
R-414BBlend containing HCFC-22
R-502ABlend containing HCFC-22

Field three: known site hazards and the brief the crew gets

The third field is the hazard line. Capture any known hazard at the site on the ticket, and record that the crew has been instructed on it before they walk in. California's safety regulation for employees is that state's rule, and a useful model for the hazard field. Where employees face known job site hazards, such as flammable liquids and gases, poisons, caustics, harmful plants and animals, toxic materials, or confined spaces, they shall be instructed in recognizing the hazard, in the procedures for protecting themselves, and in the first aid procedure in the event of injury.

That regulation applies under California's rule. The habit it describes is worth running on every ticket, whatever state you dispatch in. A brief on a known hazard belongs on the work order, dated, with a name against it, so there is a record that the instruction happened.

What the hazard field should carry on the work order before roll:

  • The hazard itself, named plainly: confined space, flammable gas, toxic material, caustic, animal or plant risk
  • Where at the site the hazard sits relative to the unit
  • Confirmation that the crew was instructed on recognition, protection, and first aid for it
  • Who gave the instruction and when

An HVAC visit can touch several of these at once. A chiller room can be a confined space. A retail refrigeration rack can sit next to cylinders. A cold storage call can put a tech alone in a low-traffic area. The hazard field is where you write that down before the truck moves, rather than hoping the tech works it out on arrival.

The instruction itself needs to cover three things, matching the regulation: how to recognize the hazard, how to protect against it, and what first aid applies if something goes wrong. Note on the ticket that all three were covered. An entry that only says "safety talked through" leaves out all three things the rule asks for.

How the three fields work together on one ticket

Taken on their own, each field looks like routine intake detail. Together they set up the visit. The location field gets the right tech to the right machine. The refrigerant field tells that tech what the machine holds before the hood opens. The hazard field makes sure the crew arrives briefed for what they will meet there.

A ticket with all three filled behaves differently from a ticket with one or two. The tech does not call in from the site for the address. They do not stand at the unit guessing whether the charge is HCFC-22 or a blend. They do not walk into a confined space or a cylinder area without a recorded brief. Each gap the fields close is a gap that would otherwise cost a return trip, a delay, or an unsafe moment.

The fields also hand off cleanly between shifts. A dispatcher who took the call at 7 a.m. and a tech starting at 2 p.m. share the same ticket. When the three fields carry real content, the second person does not have to reconstruct the job from memory or from a voicemail.

What to do when the refrigerant is unknown

You will hit tickets where the refrigerant field has no answer. The unit is old, the sticker has worn off, the customer does not know, and no past invoice is on file. Handle that case by writing the state of the answer, not by leaving a blank. Put "unknown" in the field, name who you asked, and note when you asked them.

Then treat the unknown as work for the visit. The tech can read the nameplate on site, check the service history, or inspect the charge and report back. What matters for intake is that the ticket shows the field was considered and is open, and shows who owns getting it closed.

Ask the customer for anything they have. A past invoice, a maintenance contract, a nameplate photo, or the name of the company that last serviced the unit. Any of those can carry the refrigerant name. The EPA lists several blends that contain HCFC-22, so a blend name from an old invoice is a real answer for this field even if it is not the phrase the customer expected to hear.

Building the fields into your intake form

The three fields only help if they are on the form every ticket goes through. If your dispatcher has to remember to type the location, the refrigerant, and the hazard into a comment box, some tickets will arrive without them. Put them in structured fields that show on the technician's view of the work order.

Store location as a field in the record, not as a trailing note. Mirror that on your own form. Give refrigerant and hazard the same treatment: their own fields, visible on the ticket the tech opens, not buried in an attachment.

Set the rule at intake. No ticket goes to dispatch with those three fields blank. "Unknown" is a value and fills the field. A blank is not. The difference shows up when a tech scans a day of tickets and needs to know, at a glance, which jobs still have an open question on them.

Running the hazard brief as a record

The hazard field and the brief it triggers are one workflow, not two. You capture the hazard on the ticket, you brief the crew, and you record that the brief happened with a name and a time against it. The California regulation asks for instruction in three areas: recognition of the hazard, procedures for protection, and first aid for injury. Your record should show all three were covered.

Keep the brief tied to the specific hazard on that ticket. A generic annual safety acknowledgment does not answer what this regulation describes for a known job site hazard at a specific site. The crew on a cold storage call needs the brief for what they will meet at that call.

Date and name the entry. When someone reviews the ticket later, the record should show who gave the instruction and when it was given, alongside what was covered.

The visit day check

By the time the tech pulls up, the three fields should tell them almost everything they need before the tools come out. Read the location field for where to park and how to reach the unit. Read the refrigerant field for what the machine holds. Read the hazard field for what the site holds and what brief they received.

If any of the three reads thin, raise it before work starts. A location that names the building but not the roof access is worth one call. A refrigerant field that says unknown when the customer has an invoice in a drawer is worth one more question. A hazard field with no brief recorded is worth stopping for.

That habit keeps the fields honest. A ticket system fills with whatever the intake process rewards. If dispatch rewards complete fields, the tickets that reach your techs carry real content in those three places, and the visits run on information rather than on guesswork.

What the phaseout background adds to your ticket

One piece of context helps dispatchers read a refrigerant field correctly. The EPA describes HCFC-22 as one of the most historically widely used HCFCs, along with HCFC-141b as a solvent and foam-blowing agent and HCFC-142b as a foam-blowing agent and component in refrigerant blends. The agency also notes that in 1993 it established the phaseout framework and a "worst-first" approach, which focused first on HCFC-22, HCFC-141b, and HCFC-142b because they have the highest ozone depletion potentials of all HCFCs.

That background explains why the field exists in the form it does. Older equipment at your customers' sites still holds these charges, and the field tells you which machines on your route carry one. It does not change what goes in the field. You still write the name as the unit or the record shows it.

Closing the loop after the visit

When the tech leaves, ask them to confirm or correct the three fields. If the nameplate said something different from what intake recorded, the ticket should carry the corrected value. If a hazard turned up on site that nobody had noted, add it before the ticket closes.

Those corrections feed the next visit at that site. The next dispatcher who takes a call on the same account reads a location line written by someone who stood at the unit. They read a refrigerant field confirmed against a nameplate. They read a hazard entry added by the crew who met it. Each pass through the loop makes the three fields worth more than they were on the first call.

That is the whole point of filling them before the visit rather than during it. The work order carries the job. The three fields carry what makes the job doable.

Sources

More field guides