I spent three summers working for my dad's HVAC company during college - mostly residential, some light commercial. That experience shaped a lot of how I think about inspection workflows, and ultimately led me to help build FormField.

Here's a memory that stuck with me: August in Phoenix, standing on a flat commercial roof that felt like a griddle. I had 12 rooftop units to inspect. Unit #4 had a sun-faded nameplate, and I spent ten minutes squinting at it, typing the serial number into my phone one character at a time. By unit #8, I was rushing. By unit #11, I'd checked "normal" on the amp draw without actually measuring it.

Three weeks later, that unit's compressor failed. The amp draw had been high - a sign the compressor was struggling. I'd noted something, but in my heat-exhausted state, I'd written it on the wrong line. Nobody caught it until the emergency call came in.

The paperwork didn't cause the failure. But the tedium of the paperwork made me rush through the inspection that could have caught it early.

Below is the checklist we use, along with some notes on what actually matters versus what's just documentation.


The Complete Checklist

Equipment Identification

  • Unit ID / Asset tag
  • Location (building, floor, area served)
  • Manufacturer
  • Model number
  • Serial number
  • Installation date
  • Refrigerant type
  • Tonnage / capacity
  • Voltage rating

This section is necessary for maintenance records, but it's also where most technicians start losing patience. It's 15+ fields of data that's already printed on the nameplate, but you're typing it manually, often with gloves on, often in poor lighting. This is the section we built camera-based capture for - more on that below.


Outdoor Unit / Condenser

  • Condenser coil condition (clean / dirty / damaged)
  • Coil fins (straight / bent / blocked)
  • Fan motor operation (smooth / noise / vibration)
  • Fan blades (intact / damaged / balanced)
  • Compressor operation (normal / short cycling / not running)
  • Compressor amp draw - measure and record actual reading vs. rated
  • Refrigerant lines (insulation intact / damaged / oil stains indicating leaks)
  • Electrical connections (tight / corroded / damaged)
  • Disconnect (functional / damaged)
  • Clearance around unit (adequate / obstructed)
  • Unit level (level / settling)
  • Unusual noises (describe if present)
  • Vibration level (normal / excessive)

A note on amp draw: I've seen technicians write "normal" without actually clamping on. It takes 30 seconds to measure. This is often the first indication of a compressor that's working too hard - catching it early can prevent an emergency failure.


Indoor Unit / Air Handler

  • Evaporator coil condition (clean / dirty / frozen)
  • Drain pan (clean / standing water / biological growth)
  • Condensate drain (flowing freely / slow / clogged)
  • Blower motor operation (smooth / noisy)
  • Blower wheel condition (clean / dirty / balanced)
  • Belt condition, if applicable (good / glazed / cracked / worn)
  • Belt tension (correct / loose / over-tensioned)
  • Filter condition (new / clean / dirty / missing)
  • Filter sizing (correct / undersized / gaps allowing bypass)
  • Cabinet integrity (sealed / air leaks / damage)
  • Ductwork connections (sealed / gaps / damaged insulation)

Always actually look at the blower wheel. I once found a bird that had gotten into a commercial air handler through a gap in a louver. The building couldn't figure out why airflow was restricted. Sometimes the problem isn't mechanical - it's what's gotten into the equipment.


Refrigerant System

  • Suction pressure (psig)
  • Discharge pressure (psig)
  • Superheat (°F)
  • Subcooling (°F)
  • Refrigerant charge assessment (correct / low / high)
  • Leak check performed (yes / no)
  • Leaks found (location if applicable)

If you're documenting superheat and subcooling, measure them properly. "Feels about right" isn't data. If you're going to write it down, it should be an actual reading.


Electrical System

  • Supply voltage (all legs)
  • Contactor condition (good / pitted / needs replacement)
  • Capacitor test results (good / weak / failed)
  • Wiring condition (good / damaged / signs of overheating)
  • Safety controls tested (yes / no)
  • Thermostat operation (calling correctly / issues noted)

System Performance

  • Supply air temperature
  • Return air temperature
  • Temperature differential (typically 15-20°F for cooling)
  • Airflow assessment (adequate / restricted / excessive)
  • Cycling behavior (normal / short-cycling / continuous run)

Findings and Recommendations

  • Issues requiring immediate attention
  • Issues to address at next service
  • Parts to order
  • Follow-up visit needed (yes/no, timeframe)
  • Overall system condition (Good / Fair / Poor / Critical)

Why Inspection Quality Suffers

In my experience, the problem usually isn't the technician's skill or motivation - it's the workflow. When the documentation process is tedious, people naturally start cutting corners to get through it.

That equipment ID section? On a 20-unit inspection, you're looking at 180+ fields of manual data entry before you've actually inspected anything. You're typing serial numbers character by character, dealing with autocorrect changing model numbers, struggling to read faded nameplates. By unit 10, the temptation to rush becomes hard to resist.

The inspection becomes a checkbox exercise rather than an actual assessment of equipment health.


Automating the Tedious Parts

This is where I'll mention FormField, since this is the specific problem we built it to solve.

The concept: instead of manually typing nameplate data, you point your phone camera at the nameplate. The AI reads the manufacturer, model number, serial number, specs - and populates the corresponding form fields automatically. You review, confirm, and move on.

To be clear about the limitations: it's not perfect. Heavily faded nameplates in poor lighting still cause issues. Stamped metal plates are more difficult than printed labels. You'll occasionally need to correct a character. But in our testing, it's significantly faster than manual entry - and more importantly, technicians arrive at the actual inspection portion with more patience and attention.

The goal isn't just efficiency. It's making sure the documentation burden doesn't compromise the inspection itself.


What to Look for in an Inspection Tool

If you're evaluating options (whether FormField or something else), these are the factors that actually matter in the field:

Offline capability: Mechanical rooms, rooftops, basements - signal is often unreliable or nonexistent. Test any tool in airplane mode. Many apps that claim "offline support" actually lose significant functionality without connectivity.

Speed to first entry: Count how many taps it takes to start a new inspection. If it's more than 3-4, there's friction that will add up across a busy day.

Glove compatibility: Touch targets need to be large enough to hit accurately with work gloves. This sounds minor until you're trying to use a tool in the field.

Data integration: If inspection data stays siloed in the app and requires manual export/re-entry into your maintenance system, you've just moved the data entry problem rather than solving it.


Download and Use

The checklist above is comprehensive and field-tested. Use it as-is, or adapt it to your specific requirements.

If you want to try the camera-based nameplate capture, FormField offers a free trial. If you prefer your current tools or paper, that's fine too - the checklist works either way.

The underlying principle is simple: if the inspection process creates frustration, inspection quality will suffer. Address the friction points, and the quality follows.

Try the camera-based capture

Free trial, no credit card required. Test it on your most challenging nameplates.