The HVAC service app fields EPA actually checks.
An HVAC service app has to do two things most general checklists skip: track refrigerant by the pound, and prove who was certified to touch it. Most field service apps were never asked to do either, so for this trade the question is narrower: would the record a technician leaves behind hold up if EPA, an insurer, or a building owner asked for it?
This page is about that record: the fields EPA Section 608 requires once an appliance holds 50 or more pounds of refrigerant, the four technician certification types, and how HVAC scheduling actually behaves once a heat wave doubles your call volume in a day.
See what a service record needs to captureHVAC service, by the numbers
50 lbs
Refrigerant charge that triggers EPA 608 recordkeeping
125%
Annual leak rate that triggers EPA reporting by March 1
4
EPA Section 608 technician certification types
6
Statuses in a typical HVAC job lifecycle
The short version
Refrigerant by the pound, certification by the type.
A good HVAC service app tracks the standard work order fields, plus two things specific to the trade: for any unit holding 50 or more pounds of refrigerant, EPA Section 608 requires the date and type of service and the quantity of refrigerant added on record, and technicians need a certification type (Type I, II, III, or Universal) that actually matches the equipment they're dispatched to. The rest of this page walks through both, plus a real job lifecycle and how scheduling holds up when demand spikes with the weather.
The compliance fields
What an HVAC service record needs to capture.
For any appliance containing 50 or more pounds of ozone-depleting refrigerant, EPA Section 608 requires the owner or operator to keep servicing records documenting the date and type of service, the quantity of refrigerant added, and records of leak inspections and tests performed to verify repairs. See the EPA's recordkeeping requirements . If that same unit leaks 125 percent or more of its full charge in a calendar year, the owner also has to report it to EPA by March 1 of the following year, describing what was done to find and fix the leak. Those obligations aren't optional extras for an HVAC work order app, they're the minimum an owner needs on file if a technician is ever asked to prove the work.
Everything below that is standard field-service hygiene, the same base a work order app needs for any trade: a unique record ID, which unit it applies to, who did the work, and a sign-off.
Try it
Does your current service record capture this?
Check off what your HVAC service records already track today, on a paper ticket, in a spreadsheet, or in whatever app your crew uses now.
0 of 10 · Start here — none of this is captured consistently yet.
Residential vs. commercial
The 50-pound line falls in different places.
A residential split system rarely holds anywhere near 50 pounds of refrigerant, so the EPA 608 recordkeeping requirement often stays theoretical for a pure residential book of business. A commercial rooftop unit or chiller crosses that line routinely, which is exactly why an HVAC service app for commercial and light-commercial work needs the EPA fields built in from day one, not bolted on later.
| Aspect | Residential | Commercial |
|---|---|---|
| Typical equipment | Split systems, window units, small packaged units | Rooftop units, chillers, packaged systems, multi-zone equipment |
| Refrigerant charge | Usually under the 50 lb EPA 608 recordkeeping threshold | Often at or above 50 lbs, especially chillers and rooftop units |
| Who signs off | The homeowner, on the spot | A facilities manager, sometimes after a separate approval step |
| Visit frequency | Seasonal tune-ups plus break-fix calls | Contracted PM schedules, often quarterly or more |
| What a service app needs most | Fast scheduling and a simple invoice | EPA-ready records, contract tracking, and multi-site reporting |
Who can service what
The four certification types.
EPA Section 608 defines four technician certification types, and the test a technician takes is specific to the equipment they intend to work on. A dispatch board that doesn't know the difference can send someone to a job their certification doesn't cover.
| Certification type | What it covers |
|---|---|
| Type I | Small appliances |
| Type II | High- or very high-pressure appliances, except small appliances and motor vehicle A/C |
| Type III | Low-pressure appliances |
| Universal | All types of equipment |
Certification types from the EPA's Section 608 technician certification page.
Try it
Which certification does this job need?
Pick what best describes the equipment on today's job.
Certification needed
Pick an option above to see which certification covers it.
From call to invoice
The HVAC job, status by status.
An HVAC field service app is really a work order app with trade-specific stops built into the lifecycle, most obviously a wait for parts or a refrigerant charge that isn't on the truck. Status should be a fixed set of states, not free text, so a report of "all open jobs" means the same thing every time someone runs it.
| Status | What it means | What moves it forward |
|---|---|---|
| Requested | A customer or a scheduled PM visit creates the call. | Moves to Dispatched once a technician is assigned. |
| Dispatched | A technician is assigned and en route. | Moves to On site once they arrive and start work. |
| On site / diagnosing | The technician is inspecting the equipment and identifying the issue. | Moves to In progress, or Waiting on parts if something is needed. |
| Waiting on parts | Paused because a part or refrigerant charge isn't on the truck. | Returns to In progress once the part arrives. |
| Complete | Work is finished and the service record is filled in. | Moves to Invoiced once billing is generated. |
| Invoiced | Locked. The service record and invoice are both final. | Nothing — this is the end state. |
Terminology
Service call, PM visit, or something else?
The four job types below all move through the same status model above, but each expects a different record by the end.
| Job type | What triggers it | What's typical | What the record needs |
|---|---|---|---|
| Service call | A customer reports something wrong | One unit, same-day or next-day dispatch | Diagnosis, parts used, and a sign-off |
| PM visit | A maintenance calendar or a manufacturer's service interval | Scheduled in advance, often seasonal | A checklist tied to the equipment, not a complaint |
| Install job | New equipment going in, replacement or new construction | Multi-day, often with a crew rather than one technician | Commissioning data, and the refrigerant charge on record from day one |
| Warranty callback | A comeback tied to recent work or a manufacturer defect | Prioritized ahead of routine calls, unbilled to the customer | A link back to the original job or install record |
Scheduling around weather
What happens when a heat wave doubles your call volume?
This is where a generic HVAC field service app shows its limits: a fixed weekly schedule doesn't bend when a cold snap or heat wave triggers a wave of no-cooling and no-heat calls in the same afternoon. A priority field with rules, no cooling in extreme heat outranks a routine filter change, live technician locations, and a way to slot an emergency job into the day without hand-rebuilding everyone else's route matter more here than in most trades. The underlying question, who is closest and free right now, is also the core problem a crew scheduling app is built to answer, just with HVAC-specific rules layered on top.
Scoping it out
How to scope an HVAC service app.
Five steps, in order, before anyone opens a design tool or writes a line of code.
- 1
Nail down your service record fields
Start with the EPA fields for any unit holding 50 or more pounds of refrigerant, then add whatever your insurer, franchisor, or biggest commercial customer requires on top of that.
- 2
Model the job lifecycle
Write out the states a call actually moves through, requested, dispatched, on site, waiting on parts, complete, invoiced, and decide what is allowed to skip ahead and what isn't.
- 3
Map certifications to equipment
Decide which certification type, Type I, II, III, or Universal, a job requires, so dispatch can't send a technician to equipment their certification doesn't cover.
- 4
Plan for offline capture
Basements, mechanical rooms, and rooftop units are exactly where signal drops. Decide upfront whether a technician can open a job, log refrigerant, and get a signature with no connection.
- 5
Pick a backend
Fields and lifecycle are cheap to change on paper. Wiring them to a real database, offline sync, and role-based permissions is a separate decision, worth reading up on before you start on choosing a mobile app backend.
Picking an approach
Off-the-shelf, or built around your crew.
None of the fields above require an expensive tool. Most of the common ones just make at least one of them impossible to get consistently.
| Approach | EPA-ready record | Works offline in the field | Custom fields per job type | Who maintains it |
|---|---|---|---|---|
| Paper service ticket | No | yes, by default | yes, whatever you write | you, by hand |
| Spreadsheet | No | No | yes | you, and it drifts |
| Generic field service app | manual, if you build the fields | depends | limited | you, bolted together |
| Vertical HVAC / field service platform | Yes | Yes | locked to their schema | the vendor |
| Custom-built HVAC service app | Yes | Yes | whatever your process needs | you |
The honest reason to build your own HVAC service app instead of buying a vertical platform usually isn't cost, it's fit. A crew whose service tiers, sign-off chain, or franchise requirements don't match a vendor's schema ends up either bending its process to the software or bending the software until it breaks. That gap, a process no off-the-shelf tool quite fits, is what Newly is for: describe the service record, the job lifecycle, and who can do what, and it builds a real native app around your crew instead of a vendor's template.
Free vs. paid
Is there a free HVAC service app?
For one technician trying it out, sure. Most HVAC field service platforms offer a free or trial tier, but it's usually capped by technicians, jobs, or locations, and the fields that matter most for compliance, refrigerant tracking, custom fields, offline sync, tend to be the first things reserved for a paid plan. Once dispatch, invoicing, and EPA records all need to live in the same place, budget for a real tool rather than stretching a free tier past what it was built for. Even a build-it-yourself platform like Newly starts at $25 a month, and dedicated vertical HVAC platforms typically run well past that per seat.
Sources
Where the specifics came from.
Every regulatory claim on this page comes straight from the EPA, not general industry consensus:
FAQ
HVAC service apps, answered.
An HVAC service app is used to schedule technicians, dispatch them to jobs, and record what happened at each visit: the equipment worked on, the refrigerant added, parts used, and a sign-off. For equipment holding 50 or more pounds of refrigerant, that record is not optional paperwork, EPA Section 608 requires the owner to be able to produce it.
Start with the record, not the app store listing.
HVAC service apps live or die on two things: a record that holds up to EPA, and a crew that can actually use it in a basement with no signal. Get those right, then build the app around them in Newly.