Skip to main content

Clear the Part 84 Remediation Queue

The Part 84 remediation queue lists every unit whose Subpart C applicability resolves to unknown. Units in this state still record charge events correctly — they're just flagged part84_106_subpart_c_status = unknown in compliance exports. The queue is your worklist for getting that flag green.

The page splits the work into two buckets. Bucket A is high-leverage: classifying one refrigerant fixes every unit that uses it.

Before you start​

  • You have the compliance.view permission to see the queue.
  • You have compliance.manage_refrigerant_catalog to fix Bucket A entries.
  • You have units.edit to fix Bucket B entries.
  • The Part 84 effective date has passed. Before then, the queue is intentionally empty.

Steps​

  1. Open the queue

    Select Part 84 Remediation in the top navigation bar.

  2. Read the summary tiles

    The four tiles at the top show: total unknown units, refrigerant catalog rows needing classification, units affected by an unclassified refrigerant, and units with no refrigerant assigned.

  3. Work Bucket A first

    In Refrigerant catalog rows in use but unclassified, each row shows the refrigerant, ASHRAE code, GWP if any, and the count of units linked to it. For each row, select the orange Classify action.

    The classify action opens the refrigerant edit page. Set the AIM flag, the ODS-only flag, or the GWP value as appropriate, then save. See Manage the Refrigerant Catalog for the field-by-field detail.

  4. Refresh the queue

    Return to Part 84 Remediation. Bucket A should be smaller. Repeat until it's empty.

  5. Work Bucket B

    In Units with no refrigerant assigned, each row shows the unit, customer, device model, and full charge. For each unit, select the orange Edit unit action.

    On the unit edit page, scroll to the compliance fields and assign a refrigerant. Save. The unit drops out of Bucket B on the next page load.

  6. (Optional) Set device-model defaults to prevent future Bucket B entries

    In Bucket B, the Device model column flags any model that has no catalog default. Set the default refrigerant on the device model under Settings → Device Models. New units created from that model inherit the refrigerant automatically.

What happens next​

  • Each fix removes the affected units from unknown status on the next leak-rate calc that touches them.
  • The part84_106_subpart_c_status column in EPA exports flips from unknown to either applies (in scope) or does_not_apply (carve-out).
  • The classify-once leverage means a single Bucket A fix typically clears dozens of unit-level rows.
  • The summary tiles refresh on every page load — they're computed live, not cached.

Common situations​

SituationWhat to do
Bucket A shows a refrigerant you no longer use in new installsClassify it anyway. Historical units linked to it still need the policy decision so their EPA exports come out green. After classifying, untick Active to hide it from new pickers.
Bucket B shows a unit installed years ago that you've never servicedEither assign the refrigerant from the install paperwork, or delete the unit if it's no longer in your scope. Don't guess — incorrect classification is worse than unknown.
The same model appears across many Bucket B rowsSet the model's default refrigerant under Settings → Device Models. Existing units don't auto-update, but the next time you bulk-edit them you can apply the default.
You see "Showing first 200 affected units" at the bottom of Bucket BThe queue caps the table at 200 rows for page performance. Use the EPA records export to pull the full list as CSV for triage.
The queue is empty and the in-force banner is still upNothing to do. Every in-scope unit has a classified refrigerant. Check back after adding new units, importing customers, or after Part 84 amendments shift the threshold.

Troubleshooting​

The Classify button doesn't appear next to a refrigerant row.

You don't have compliance.manage_refrigerant_catalog. The row shows a "Needs catalog permission" hint instead. Ask an admin to grant the permission, or send the row to whoever does have it.

A unit I just classified still shows in Bucket A's sample column.

The sample column lists representative units, not the live affected list. After classification, the Affected units count drops and the row may disappear entirely on the next refresh. The sample is informational; the count is authoritative.

A unit in Bucket B doesn't have a device model.

The unit was created without a model — a data integrity edge case. Open the unit and assign a model first. The refrigerant assignment then becomes possible.

The page shows "Part 84 Subpart C is not yet in force."

Your tenant's part84_effective_date is in the future. The queue is intentionally empty until the date passes. Confirm the date is correct under Settings → Compliance.