The Service Ticket That Survives an Inspection (and the One That Doesn't): A Field-by-Field Teardown

Week 24, the Saturday edition. Monday's mid-year audit gave you six checks to run on the file cabinet before July 1. Today we zoom all the way in — past the appliance ledgers, past the calendar-year totals — to the smallest unit of compliance there is: one service ticket.

Because here's the thing the six-check framework assumes and never says out loud: every check in that audit is built out of individual tickets. The calendar-year total is a stack of tickets added together. The repair clock is a date on a ticket. The verification test is a line on a ticket. If the tickets are weak, the audit framework has nothing to stand on — you're aggregating air.

So today we take one real summer service call — the kind your techs ran a dozen times during last week's heat surge — and write it up twice. Once the way most of the industry still writes it up. Once the way a ticket has to read to survive an inspector's cross-examination. Then we pull both files the way an inspector would, checkpoint by checkpoint, and watch what happens.

The Call

Tuesday, June 9. The back end of the Northeast heat surge. A restaurant calls at 11:40 AM: dining room won't hold temperature, lunch rush starting, get here now.

Your tech rolls up, gets on the roof, and finds the usual suspect: a packaged R-410A rooftop unit serving the dining room, suction pressure low, superheat high. System's down on charge. He weighs in 4.5 pounds, the space starts pulling down, the owner is happy, and the tech is on to the next emergency by 1:30.

The facts of the system:

This is a commercial comfort cooling appliance with a full charge over 15 pounds — squarely covered under Subpart C, not exempt. No refrigerant has been added since the rule took effect, so this is the first calculation under the new program. Using the Annualizing method with the 365-day first-calculation substitution:

Leak Rate = (4.5 ÷ 25) × (365 ÷ 365) × 100 = 18.0%

The comfort cooling threshold is 10%. This system just exceeded it. A 30-day repair clock started June 9. The repair and initial verification test are due by July 9. The follow-up verification test is due within 10 days of a passing initial test.

That's the event. Now let's look at the two ways it gets written up.

Ticket A: The One Most of the Industry Still Writes

Here's the service ticket as it actually reads in thousands of shops this month:

6/9/26 — Marotta's Trattoria — RTU not cooling Found system low on charge. Leak checked, added freon, topped off. System cooling good on departure. 4.5 lbs R-410. Labor: 2.5 hrs. Refrigerant: 4.5 lbs @ $85.

The work behind this ticket might have been excellent. The tech might have weighed the refrigerant precisely, might have scanned the coil with a detector, might even have done the leak rate math in his head. None of that matters, because this is the entire record — and as we said back in the documentation mistakes post: if you can't prove it, you didn't do it.

Count what's missing:

• Which appliance? "RTU" — the restaurant has two. There's no appliance ID, so this addition can't be assigned to a specific unit's calendar-year ledger or service history.
• Full charge? Not stated, not on file. Without the denominator, no leak rate can be calculated or defended — by anyone, ever.
• Leak rate? Not calculated. Which means nobody knows a threshold was exceeded, which means no repair clock started, which means the clock that legally started on June 9 is running silently toward a blown deadline.
• Calculation method? Unknown.
• "Leak checked" — how? No method, no locations inspected, no findings, no certification that visible and accessible components were examined.
• Who did the work? No technician name, no Section 608 certification number.
• Was the record given to the owner? The owner got an invoice. An invoice is a bill, not a compliance record.

One more detail worth sitting with: "topped off" and "$85" tell you this ticket was written to get paid, not to get compliant. That's not a character flaw — it's what tickets were for, for decades. Subpart C changed what a ticket is for. The ticket is now the compliance record, and most shops haven't updated the template to match the new job description.

The invoice gets you paid for the work. The ticket is what proves the work was legal. They are no longer the same document.

Ticket B: The One That Survives

Same call. Same tech. Same 4.5 pounds. Here's the version that holds up — field by field, with the regulatory citation each field answers to:

Two fields on that table deserve a closer look, because they're the ones most shops have never heard of.

The § 84.106(l)(5) inspection record. When a leak inspection happens, the regulation doesn't just want "leak checked." It wants the date, the method used, the location of every leak identified, and a certification that all visible and accessible components were inspected — provided by the certified technician to the owner. "Found leak at liquid line flare" plus "all visible and accessible components inspected" is the difference between an inspection and a rumor of one.

The § 84.106(l)(4) handoff. Subpart C puts the recordkeeping obligation on the owner or operator — but when someone other than the owner performs the work (that's you, the contractor), the regulation requires that person to provide the service-event record to the owner. This is the contractor's hard legal hook in the whole framework. Ticket B closes that loop explicitly: the record was delivered, and the delivery is noted. Ticket A handed over an invoice and called it a day.

The marginal cost of Ticket B over Ticket A is about four minutes at the truck. Every number on it was already in the tech's hands — the scale reading, the nameplate, the detector result. The only thing Ticket B adds is the discipline of writing them down in a structure that maps to the regulation.

Now the Inspector Pulls the File

Fast-forward to October. A records request arrives — the EPA enforces the AIM Act with Clean Air Act tools, and the routine instrument is a Section 114 information request: a letter identifying specific equipment and demanding the records, typically with a 30-day response window. As we covered in the audit defense walkthrough, by the time the letter arrives the inspector usually has a thesis. Suppose the trigger here is a building-owner dispute: Marotta's is selling the business, the buyer's due-diligence team asked for refrigerant compliance records, and the seller's attorney forwarded the question to the EPA region rather than answer it.

The request names RTU-1 at 318 Harbor Ave and asks for all refrigerant service records from January 1, 2026 forward. Let's pull each file.

Checkpoint 1: Can you establish the appliance and its full charge?

Ticket A: "RTU." Which one? The file can't tie the addition to a specific appliance, and no full charge exists anywhere. The inspection effectively ends here — every downstream requirement depends on this foundation, and the foundation is missing. From the inspector's chair, this isn't a formatting problem. It's the absence of the record § 84.106(l)(1) says must exist.

Ticket B: RTU-1, west roof, 25.0 lbs per nameplate, verification date on file. Thirty seconds. Next checkpoint.

Checkpoint 2: Was a leak rate calculated on the addition?

Ticket A: No calculation appears. The inspector now does the math the ticket didn't: 4.5 pounds on what turns out to be a 25-pound system is 18% under any method. The threshold was exceeded on June 9 and nobody's records know it. Which leads directly to —

Checkpoint 3: Did the 30-day clock run, and was the repair verified?

Ticket A: No exceedance was flagged, so no repair was scheduled, so no initial or follow-up verification test exists. It's October. The clock that started June 9 expired July 9 — three months ago — with no repair, no documented extension, and no retrofit/retirement plan. What began as a sloppy ticket has matured into a missed repair deadline with a complete documentation void behind it. And every pound added to this unit since June has been silently stacking the calendar-year total toward territory nobody is watching.

Ticket B: The exceedance was flagged on June 9, the flare repair is documented June 24, the initial verification test (standing pressure, held 30 minutes, electronic scan clean at repair site) passed the same day, and the follow-up verification under normal operating load passed July 1 — inside the 10-day window. The annual inspection obligation that follows a threshold exceedance is on the calendar. Clean chain, checkpoint passed.

Checkpoint 4: Method consistency across the facility

Ticket A: No method appears on any ticket at this site, so consistency can't be evaluated — which reads as a § 84.106(b) failure in itself.

Ticket B: Annualizing, per the facility record, on every 2026 ticket at the address. Passed.

Checkpoint 5: Was the owner given the records?

Ticket A: The owner has invoices. When the inspector asks Marotta's for their § 84.106(l)(2) records, the owner produces billing paperwork — and then points at the contractor, because the contractor was supposed to provide the compliance record under § 84.106(l)(4) and didn't. This is the moment the owner's compliance failure becomes the contractor's liability conversation.

Ticket B: The written exceedance notice and the full service record went to the owner on June 9, and the delivery is noted on the ticket. The owner's file and the contractor's file match. That's what a defensible relationship looks like on paper.

The Tie-Back to Monday's Six Checks

Here's why this post is the companion to the mid-year audit rather than a standalone exercise. Every one of Monday's six checks is answered — or broken — at the ticket level:

Check 1 (calendar-year cumulative totals) is the sum of the "quantity added" field across tickets. Ticket A's vague appliance ID means its 4.5 pounds lands nowhere, and the cumulative total for RTU-1 is silently wrong.

Check 2 (open 30-day repair clocks) only exists if the ticket calculated the rate and flagged the exceedance. Ticket A never opened the clock it was legally required to open.

Check 3 (verification test documentation) lives or dies on whether verification is a closure field on the repair ticket. Ticket B's chain — repair, initial test, follow-up test, dates, methods, results — is exactly what Check 3 audits for.

Check 4 (method consistency) is enforced by the "method per facility record" field. Pre-populate it and the failure mode disappears.

Check 5 (§ 84.106(j) plans) is downstream of the clock. A ticket that never started the clock can never trigger the plan — which means the plan that should exist, doesn't.

The mid-year audit finds these problems in aggregate, weeks or months later. The ticket prevents them in real time, at the truck, while the facts are still warm. The field reference guide called it the five numbers a tech captures before driving away. This post is what those five numbers look like when they grow up into a complete record.

The audit is where you find out whether your tickets were real. The ticket is where you decide.

What to Do With This Before Monday

Three moves, in order of leverage:

1. Put the two tickets in front of your techs. Print this post's two versions side by side. Don't lecture — just ask which file they'd rather hand an inspector with their name on it. The gap sells itself.

2. Rebuild your ticket template to Ticket B's field list. Every field on that table, in that order, with the method and full charge pre-populated from the appliance record so the tech fills in only what changed today. If a field can't be left blank, it won't be left blank.

3. Run one ticket from last week through the five checkpoints. Pick a real refrigerant addition from the heat surge. Pull the ticket. Walk it through appliance ID, full charge, calculation, clock, and owner handoff. If it survives, your summer discipline is holding. If it doesn't, you just found Monday's first corrective action — in June, while it's still a fix instead of a finding.

The inspection your records will eventually face isn't a test of your craftsmanship. Every contractor reading this does competent work. It's a test of whether the ninety seconds at the end of each call captured that work in a form the regulation recognizes. Ticket B costs four minutes. Ticket A costs whatever the cascade costs — and you don't get to pick when the bill arrives.

---

Monday's anchor post: the biggest refrigerant enforcement story of 2026 just landed — a proposed federal consent decree with a multi-million-dollar penalty, roughly $100 million in mandated equipment upgrades, and recordkeeping failures cited right alongside the leak-repair violations. We'll read the whole thing the way a five-truck shop should: what the government actually cited, why "enforcement is deprioritized" is the most dangerous half-truth in the trade right now, and what it means for the file cabinet you just audited. See you Monday.