5 Spring Startup Scenarios That Are Tripping Up Contractors Right Now (And How to Handle Each One)

Four weeks ago, we covered the seasonal variance exemption in detail: the four conditions, the documentation requirements, the chronic leaker connection, and what to do when the numbers don't match.

That was theory. This is what's actually happening in the field.

Across the country this week, commercial cooling systems are coming back online. Techs are connecting gauges, checking charge levels, and making the first spring additions of refrigerant under Subpart C. And the same five scenarios keep showing up — each one requiring a different decision, different documentation, and different compliance outcome.

This post walks through all five. Read it in the truck before your next spring startup call.

Scenario 1: The Clean Seasonal Variance

The situation: Marco's shop pumped down a 22-lb R-410A rooftop unit at a dental office on November 8, 2025. His tech recovered 14.2 lbs into a clean tank, weighed it, and documented the removal as seasonal — including the exact weight, the date, the reason (seasonal shutdown due to ambient temperature), and the equipment ID.

Now it's March 18. Marco's tech is back at the same unit for spring startup. He charges the system with 14.2 lbs — exactly what was removed. The system reaches full charge. Everything checks out.

The call: This is a textbook seasonal variance exemption. All four conditions are met: refrigerant was removed first, the removal was seasonal, the addition equals the removal amount, and both events fall within a 12-month window.

What to document:

• Equipment ID: RTU-3, dental office, 440 Commerce Dr
• Date of spring addition: March 18, 2026
• Amount added: 14.2 lbs
• Cross-reference to fall removal: 14.2 lbs removed November 8, 2025
• Confirmation: 14.2 ≤ 14.2 — seasonal variance applies
• Notation: "Seasonal variance — spring recharge, exempt from leak rate calculation per § 84.106(b)"

What Marco does NOT do: Calculate a leak rate. He doesn't need to. The exemption is valid.

What Marco DOES still do: Add the 14.2 lbs to the system's calendar-year cumulative total for 2026. Seasonal variance exempts the leak rate calculation — it does not exempt the addition from chronic leaker tracking. On a 22-lb system, 14.2 lbs is already 64.5% of full charge. If this system needs any significant service additions later this year, it could approach 125%.

Scenario 2: The Mismatch — System Needs More Than What Was Removed

The situation: Dana recovered 12.4 lbs from an 18-lb R-410A unit on October 30, 2025. Fall documentation is complete — exact weight, seasonal reason, all four boxes checked. In March, her tech reconnects the system and starts charging. The unit takes 14.0 lbs to reach full charge.

That's 1.6 lbs more than what was removed.

The call: Seasonal variance does not apply. The exemption requires the spring addition to be less than or equal to the fall removal. 14.0 exceeds 12.4. The moment the total addition passes the removal amount, the entire addition becomes a standard service event that requires a leak rate calculation.

This is the scenario we flagged in the seasonal variance post: you cannot split the addition and claim the exemption on the first 12.4 lbs while calculating a leak rate on the remaining 1.6 lbs. It's all or nothing.

What to document:

• Equipment ID, location, date, refrigerant type, amount added (14.0 lbs)
• Note that seasonal variance was evaluated but does not apply (addition > removal)
• Full leak rate calculation on the 14.0 lbs added
• Calculation method, result, applicable threshold (10% for comfort cooling)
• Whether threshold was exceeded

What Dana should investigate: Where did the 1.6 lbs go? It was either lost during recovery (equipment issue), leaked from the tank over winter (storage issue), or leaked from the system while it was down (the system has a leak). If the system lost refrigerant while idle, that's exactly the kind of problem Subpart C is designed to catch.

Scenario 3: No Fall Documentation — Can't Prove the Removal

The situation: Jeff's shop has been pumping down rooftop units every winter for years. It's just what they do. But last fall was the first winter under Subpart C, and nobody thought to change the documentation process. The tech recovered refrigerant from three commercial units in November — but the service tickets just say "pumped down for winter." No exact weights. No notation that the removal was seasonal. No cross-reference to equipment IDs.

Now it's spring. Jeff's techs are at those same sites adding refrigerant back. Can they claim seasonal variance?

The call: No. The exemption requires documentation of both the removal and the addition, including exact amounts for both. Without the fall removal weight on record, there's no way to confirm that the spring addition is less than or equal to what was taken out. The exemption fails at Condition 3.

What to do:

Treat every spring addition on these systems as a standard service event. Calculate the leak rate on the full amount added. Document everything per the standard requirements — equipment ID, full charge, amount added, date, calculation method, result.

The silver lining: This is a one-time problem. Jeff now knows what to document next fall. Every pumpdown from October 2026 forward should include exact pounds recovered, the seasonal reason, the date, the equipment ID, and the tech's name and cert number. One bad season of documentation doesn't compound — it just means this year's spring additions get calculated instead of exempted.

The seasonal variance exemption is only as good as the fall documentation that supports it. If you didn't write it down in November, you can't claim it in March. Full stop.

Scenario 4: "It's Spring, So It's Seasonal Variance" — The False Assumption

The situation: A tech on Rosa's crew is at a strip mall servicing a 20-lb R-410A rooftop unit. The system is low — needs 5 lbs to reach full charge. The tech knows it's spring. He's heard about the seasonal variance exemption. He writes on the service ticket: "Seasonal variance — spring recharge, no leak rate calc needed."

Nobody removed refrigerant from this system last fall. It ran all winter. It's just low.

The call: This is the single most common misapplication of the seasonal variance exemption we're seeing in the field. Seasonal variance requires a prior documented removal of refrigerant due to a change in season. If no one deliberately pulled charge from this system before winter, there is no seasonal variance event. The system is low because it leaked — and that leak needs to be measured, not exempted.

What this actually is: A standard refrigerant addition that triggers a leak rate calculation. Five pounds on a 20-lb system is 25% — well above the 10% comfort cooling threshold. This system needs a repair within 30 days (or 14 if you're in Washington).

What Rosa should do: Correct the service ticket. Remove the seasonal variance notation. Calculate the leak rate. Document the threshold exceedance. Start the repair clock.

The training issue: This scenario is a crew communication problem. The tech knew the phrase "seasonal variance" but didn't understand the conditions. A five-minute morning huddle covering the four requirements — with emphasis on "removal came first" — prevents this mistake on every spring call for the rest of the season.

Scenario 5: Clean Seasonal Variance — But the System Is Already Trending Toward Chronic Leaker

The situation: Amir's shop did everything right. They recovered 16.0 lbs from a 20-lb R-410A condenser at a restaurant on November 15, 2025. Documentation is perfect. In March, the tech adds 16.0 lbs back. Seasonal variance applies. No leak rate calculation needed.

But when Amir looks at the calendar-year cumulative for this system, the picture isn't great. Before the seasonal pumpdown last fall, the system had already received two service additions earlier in 2025. And since the chronic leaker threshold tracks the calendar year — January 1 through December 31, 2026 — the 16.0 lbs added in March goes on the 2026 ledger.

That's 80% of full charge from one event — a valid seasonal variance event — and it's only March. If this system needs even 9 more pounds of refrigerant between April and December, it crosses 125% and becomes a chronic leaker.

The call: The seasonal variance exemption was applied correctly. There's no compliance error here. But this system is now on a trajectory that demands attention.

What Amir should do:

Flag this system at the 75% alert level (it's already past that). Have the building owner conversation now — not in October when it's too late. Show the numbers: 80% of full charge consumed by a single seasonal event, 125% threshold only 9 lbs away, and if the system needs any service additions this summer, a federal report will be required by March 1, 2027.

This is exactly the scenario where Subpart C compliance becomes a business conversation. The system may be a candidate for replacement, a major leak investigation, or at minimum a proactive maintenance plan that prioritizes keeping this unit off the chronic leaker list.

The Spring Startup Cheat Sheet

Before your tech leaves the shop for any spring startup call, they should know the answers to these questions:

1. Was this system pumped down last fall?

• Yes → Check the fall documentation. Proceed to question 2.
• No → This is a standard service event. Calculate the leak rate on any refrigerant added.

2. Is the fall removal documented with exact pounds and a seasonal reason?

• Yes → Proceed to question 3.
• No → Seasonal variance doesn't apply. Calculate the leak rate.

3. Does the system need more charge than was removed?

• No (addition ≤ removal) → Seasonal variance applies. Document the match. Skip the leak rate calculation. Add the amount to the calendar-year chronic leaker total.
• Yes (addition > removal) → Seasonal variance doesn't apply. Calculate the leak rate on the full amount added. Investigate the discrepancy.

4. After the spring addition, where does this system stand on the calendar-year total?

• Below 75% → No immediate action needed beyond standard tracking.
• 75–100% → Flag for monitoring. Discuss with building owner.
• Above 100% → Active risk. Proactive leak investigation and replacement conversation warranted.

What We're Watching

This is the first spring under Subpart C. Every contractor in America with commercial cooling customers is navigating these scenarios for the first time. The patterns we're seeing now — documentation gaps from last fall, misapplied exemptions, mismatch surprises — will repeat next year in any shop that doesn't build the fall pumpdown process into their standard workflow.

The Q1 audit we published two weeks ago included seasonal variance as Audit Area 5. If you haven't checked your spring startup documentation yet, this week is the week to do it.

And if you're in a state with stricter timelines — Washington's 14-day repair window, for example — the margin for getting these decisions wrong is even thinner. Know your state rules before the first truck rolls.

---

Next week: refrigerant costs are climbing. We'll look at how the AIM Act phasedown is affecting what you pay at the supply counter, what that means for your customer quotes, and why the contractors who track refrigerant usage per-system are going to have a pricing advantage over those who don't. See you March 30th.