Overview
In SwiftComply FOG, every pump out you create, edit, or delete recalculates Compliance in two places:
The GCD the pump out is linked to.
Every establishment that GCD belongs to.
This article covers how that cascade works. The full reference of every Compliance status and how each one is calculated lives in Understanding Compliance and Compliance Statuses.
How a pump out updates GCD Compliance
Each GCD's Compliance is calculated from its pumping frequency and its most recent pump out. The four possible statuses are Compliant, Overdue, Non compliant, and Never pumped. For exact definitions and the 14-day grace window, see Understanding Compliance and Compliance Statuses.
What triggers a GCD recalculation
A pump out is created, edited, or deleted on the GCD.
The GCD's pumping frequency or frequency unit changes.
A nightly background job rechecks every GCD, so statuses roll forward as time passes (for example, Compliant → Overdue without anyone touching the record).
How GCD Compliance rolls up to the establishment
An establishment's status matches its least compliant GCD. The five establishment statuses are Compliant, Overdue service, Non compliant, No pump outs, and No devices. (The establishment labels are slightly different from the GCD labels.)
How the priority works: FOG checks every GCD on the establishment and uses the least compliant one to set the establishment's status. From worst to best:
Any GCD is Non compliant → establishment shows Non compliant.
Any GCD is Overdue (and none are Non compliant) → Overdue service.
Any GCD is Never pumped (and none are Non compliant or Overdue) → No pump outs.
Every linked GCD is Compliant → Compliant.
The establishment has no GCDs linked at all → No devices.
What triggers an establishment recalculation
Any GCD linked to the establishment has its Compliance change.
A GCD is linked to or unlinked from the establishment.
The nightly background job updates every establishment after rechecking the GCDs.
Where to see the change
Open any establishment and click the Compliance history tab. Every status change is logged with the new status and the date it was recorded -- you don't need to dig into individual pump out records to see the trend.
Click Establishments in the sidebar.
Open the establishment.
Click the Compliance history tab.
FAQ
Q: If I delete a pump out, does compliance reset?
A: Yes. The GCD's Compliance recalculates against whatever pump out is now the most recent. The establishment's status is then re-derived from its linked GCDs. If the deleted pump out was the only one on file for that GCD, the GCD drops to Never pumped.
Q: One GCD on an establishment is Overdue but the rest are Compliant. What does the establishment show?
A: Overdue service. The establishment always matches its least compliant GCD.
Q: Why did my establishment change status overnight?
A: The nightly job re-evaluated every GCD. If a GCD's next service date passed, it rolled from Compliant to Overdue, which can flip the establishment to Overdue service.
Q: I unlinked a GCD from an establishment. Will compliance update?
A: Yes. Unlinking triggers a recalculation. If the unlinked GCD was the only Non compliant or Overdue device, the establishment's status can improve immediately.
Q: Why are the GCD and establishment status names different?
A: The GCD uses Overdue and Never pumped, while the establishment uses Overdue service and No pump outs. They mean the same thing -- the wording was tuned for each context (a device versus a business).