Skip to main content

Michigan State Report Training

How the Michigan State Report Calculates Data

  • XXXX is the Reporting Year. The year runs Jan 1 to Dec 31 in the time zone of the organization running the report.

  • Every line only counts locations that are not deleted and have Zoning set to Industrial, Commercial, Institutional, Residential or Governmental. Zoning and Hazard Level are in the State Report Properties section on each location. Capitalization doesn't matter. A location with any other Zoning value, including blank, is left out of the whole report, including its assemblies in lines I and J.

  • Inactive locations are counted.

  • High hazard means Hazard Level is High. Every other location counts as low hazard, including ones where Hazard Level is blank.

  • Locations created while filling out a survey or test report start with Zoning and Hazard Level blank, so they're left out of the report until Zoning is set.

  • Lines C through H count locations, not surveys. A location with several surveys in XXXX still counts once on each line. Lines I and J count assemblies.

  • Line D uses the location's first survey date. It's saved with the location's survey dates, but it isn't shown anywhere in SwiftComply.

  • Line E uses Last Surveyed On and Next Survey Due, including the history of changes to them. The location's Compliance history tab lists that history (its Compliance Date and Expiration Date columns), except for the previous due date (see How Survey Dates Work below).

  • Surveys that were never accepted don't affect lines D or E. A survey that was accepted and later reset can still count in both. Dates entered by hand on the location count the same way as an accepted survey.

  • Lines F and G look at the survey reports themselves, not the location's survey dates.

  • Survey settings can use Hazard Level to decide how often a location is surveyed. Where they do, changing Hazard Level also changes the Next Survey Due that the next survey sets.

  • When a rule says "currently", it means the value on the record right now, not what it was during the reporting year.

Warnings Shown at the Top of the State Report

"No locations found."

Your organization and its child organizations have no locations, or all of them are deleted. The report stops there, so every line shows 0. The warning shows at the top of the report under "There were some issues that could affect the accuracy of this report".

This is the only warning the Michigan report shows:

  • A location with a blank or unexpected Zoning value is left out of every line without a warning. If no location has Zoning set, every line shows 0.

  • A location with a blank Hazard Level counts as low hazard, without a warning.

  • If the report fails to run, an error message appears, usually with a reference code. Send that code to SwiftComply support.

Line C: Accounts that must be routinely reinspected

C. Total number of industrial, commercial, institutional, residential, and governmental accounts that must be routinely reinspected for cross connections

Counts the locations that meet all of the following:

  1. Currently not deleted

  2. Zoning is currently Industrial, Commercial, Institutional, Residential or Governmental

Inactive locations are counted. This line doesn't look at surveys or assemblies, so a location that has never been surveyed still counts here.

How many are High Hazard accounts: of the locations in line C, the ones where Hazard Level is currently High.

How many are Low Hazard accounts: of the locations in line C, the ones where Hazard Level is currently anything other than High, including blank.

Line D: Initial inspections

D. Number of accounts from line "C" that received an initial inspection in XXXX

Of the locations in line C, counts the ones whose first survey date is in XXXX (Jan 1 through Dec 31).

The first survey date is saved when the location's survey record is first created: by an accepted survey (its Surveyed On date), a date entered by hand on the location, or when your data was first loaded into SwiftComply. For locations loaded at setup, it's the oldest survey date that was loaded, which can be earlier than any Last Surveyed On the location has shown. After that it doesn't change, even when newer surveys are accepted or Last Surveyed On is corrected by hand. It isn't shown anywhere in SwiftComply, so if you think one is wrong, contact SwiftComply support.

  • "Initial" means the first survey date saved on the location in SwiftComply, which isn't always the oldest survey on file. If a location had surveys before it was in SwiftComply and they weren't loaded, its first survey in SwiftComply counts as initial.

  • A survey at a location that already had survey dates before XXXX can't count in D. It can only count as a completed reinspection in E.

  • A survey dated before the location's current Last Surveyed On doesn't change the location's dates when it's accepted, so it doesn't count in D or E.

  • If a location's only accepted survey is reset, all its survey dates are removed, including any entered by hand, and the location drops out of D. The next survey that's accepted sets a new first survey date. If the reset survey was the location's first survey but not its only one, its date stays as the first survey date. Either way, the reset survey's dates stay in the history that line E reads.

Line E: Reinspections required and completed

E. High hazard reinspections required

Of the high hazard locations in line C, the report looks at each location's most recent survey on or before 12/31/XXXX, from the history of its survey dates. If that survey's dates were changed later, it uses the version saved most recently. The location counts if either of these is true:

  1. That survey's Next Survey Due is on or before 12/31/XXXX, meaning it came due in XXXX or was already past due

  2. The previous due date saved with that survey is on or before 12/31/XXXX. This one is skipped when that survey is the location's first survey and it was done in XXXX.

  • #1 has no first-survey exception. A failed first survey sets the Next Survey Due one survey period before the survey date, so a location whose first survey in XXXX failed counts in D and also as required (not completed) here. The same goes for a passing first survey whose new due date is still in XXXX.

  • The skip in #2 compares the survey's date with the first survey date. If the Last Surveyed On from a location's first survey is later changed by hand to a later date, the skip no longer applies, so that survey can count in D and in E. Moving it to an earlier date doesn't do this.

  • The report reads the history of the location's Last Surveyed On and Next Survey Due, not just the current values. A survey date that was later reset or corrected can still be the one it uses. For example, if a 2026 Last Surveyed On was entered by mistake and fixed to 2025, the report still sees 2026.

  • Locations that have never had survey dates aren't counted. A location whose dates were removed by a reset can still count.

  • There's no start date. Locations that were already past due before XXXX count as required every year until a survey moves their due date. On a survey cycle longer than a year, a location can also count as required in a year it wasn't due. For example, a location surveyed in 2024 with its next survey due in 2027 counts as required in 2026. Where low hazard locations are surveyed on a longer cycle, this shows up most in the low hazard line.

E. High hazard reinspections completed

Of the locations counted in High hazard reinspections required, counts the ones where all of the following are true for that most recent survey:

  1. Its date is after Jan 1 and on or before Dec 31 of XXXX. Survey dates are saved as midnight, so a survey dated Jan 1 doesn't count as completed.

  2. It isn't the location's first survey in SwiftComply (that one counts in line D)

  3. The previous due date saved with that survey is on or before 12/31/XXXX

  4. Its Next Survey Due is after 12/31/XXXX

  • #4 doesn't check what set the Next Survey Due. A failed survey, or a passing survey done too early to change the due date, can count as completed if the due date was already past 12/31/XXXX.

  • While the Next Survey Due is still in XXXX, a failed survey doesn't count as completed, since it doesn't move the due date. The location counts once a passing survey moves the due date past 12/31/XXXX.

  • #2 uses the same date check as the skip in required #2. If the first survey's Last Surveyed On was later changed by hand to a later date, or the location's only survey was reset, that survey can count as completed here.

  • A second passing survey in the same year can take the location out of line E completely. The second survey moves the due date again, so the due date it replaced is already in the next year, and the location is neither required nor completed. Pushing the Next Survey Due out by hand during the year, while the Last Survey Result is Pass, does the same thing.

  • With Preserve Date turned on in your survey settings, a passing survey's new due date is the old due date moved forward by whole survey periods until it's on or after the survey date (with default settings). A passing survey done more than the allowed number of days before the due date (90 by default) doesn't change it at all. Either way, if the new due date is still in XXXX, the location counts as required but not completed. For example, a location due in Oct 2025 and surveyed in Feb 2026 gets a new due date of Oct 2026, so it needs another survey before it counts. These settings are in the Compliance Reports Settings and Rules section of your organization settings page.

  • A survey done in the year before a location was due doesn't count as completed in either year. With Preserve Date on, the new due date is a full period after the old one, so the location also counts as required but not completed for the whole year it was due.

E. Low hazard reinspections required: the same as High hazard reinspections required, but for the low hazard locations in line C (Hazard Level is currently anything other than High, including blank).

E. Low hazard reinspections completed: the same as High hazard reinspections completed, but for the low hazard locations in line C.

Line F: Cross connections found

F. Number of accounts where a cross connection(s) was found to exist during inspections or reinspections in XXXX

Of the locations in line C, counts the ones with at least one survey report that meets all of the following:

  1. Not deleted

  2. A Backflow Survey report

  3. Surveyed On date is in XXXX (Jan 1 through Dec 31)

  4. Has a Corrective Action Required field that's checked

  • The survey report's status doesn't matter. In Progress, Submitted, Pending Payment, Rejected and Accepted all count. An in-progress survey counts once its Surveyed On date has been saved.

  • The report looks for the Corrective Action Required field itself, not its label, so a renamed field still counts. A plain checkbox that's only labeled "Corrective Action Required" doesn't. If none of the survey forms used in XXXX have a Corrective Action Required field, this line is 0.

  • Only that checkbox counts. A survey marked as failed some other way, like a pass/fail question answered No, isn't counted here unless the box is also checked.

Line G: Corrective actions completed

G. Number of accounts from "F" where corrective actions have been completed

Of the locations in line F, counts the ones where at least one of the survey reports counted in line F is currently Accepted.

  • Nothing else is checked. The report doesn't look for a follow-up survey or anything else showing the issue was fixed, so accepting the survey that found the problem counts the location as corrected. A follow-up survey with the box unchecked never adds the location to G. Only accepting a survey with the box checked does.

  • A survey that hasn't been accepted stays out of G, and also out of D and E. Until it's accepted, the location keeps its old Last Surveyed On, Next Survey Due and Last Survey Result, so it can keep showing as due or past due.

  • Where survey settings fail a survey when the box is checked, accepting the survey records a failed survey, even though G counts the location as corrected.

  • G uses each survey's current status, so the number can change if the report is run again later.

Line H: Accounts in compliance

H. Total number of accounts from line "C" which are now in compliance with the local cross connection control program; H = C - (F - G)

Line C minus (line F minus line G). In other words, every location in line C except the ones in line F that aren't in line G. Nothing else about the location's compliance is checked.

Line I: Devices requiring testing

I. Total number of backflow prevention devices in system requiring testing

SwiftComply keeps a location record for each location an assembly has been at, with its Installed On, Set Inactive On and Removed On dates. Line I reads those dates, not the assembly's Status. It counts the assemblies that meet all of the following:

  1. Currently not deleted

  2. Isn't a test kit. Every other type counts, including Air Gap, Low Pressure Cut-Off, Single Check, the Backflow Prevention Method types (BB, CV and HC) and Unknown.

  3. Has a location record, current or past, where Installed On is blank or on or before 12/31/XXXX

  4. On that record, Set Inactive On is blank, before 1/1/XXXX or after 12/31/XXXX

  5. On that record, Removed On is blank or before 1/1/XXXX

  6. If more than one location record meets #3 to #5, the report uses the one with the latest Installed On. A blank Installed On counts as the earliest, and if two tie, it uses the one changed most recently.

  7. That location is in line C

  • An assembly set to Inactive before XXXX, or removed from its location before XXXX, still counts. One set to Inactive during XXXX, or removed during XXXX and not moved somewhere else, doesn't.

  • Replacing an assembly sets the old one to Inactive (or removes it from the location), so it drops out of line I in the year it was replaced, then counts again every year after, along with the assembly that replaced it.

  • Assemblies that were never at a location, or whose location record is for a location that isn't in line C, aren't counted. An assembly with no location today can still count through a location it was removed from before XXXX. Assemblies at inactive locations are counted, unless the assemblies were also set to Inactive during XXXX.

Line J: Devices tested

J. Number of backflow prevention devices tested in XXXX: Pass

Of the assemblies in line I, counts the ones tested in XXXX whose result was a pass.

An assembly counts as tested in XXXX when its compliance history has at least one entry with a Last Tested On date in XXXX (Jan 1 through Dec 31). Entries come from an accepted test that updates the assembly (its Tested On date), a Last Tested On entered by hand, or setup data. If an assembly has no test dates, entering only a Next Test Due fills in Last Tested On as one test period before it (or today, if that would be in the future), and picking only a Last Test Result fills in today. Either way it counts as tested.

For the result, the report takes the most recently saved of those entries, even one saved after XXXX ended. If its Last Test Result was Pass, the assembly counts as Pass. Otherwise it counts as Fail. Whether the Next Test Due has passed doesn't matter.

  • Each assembly counts once. An assembly that failed and then passed a retest in XXXX counts as Pass.

  • If Last Test Result is later changed by hand while Last Tested On is still in XXXX, that year's result changes too.

  • Accepting a test only updates the assembly when its Tested On date is on or after the assembly's current Last Tested On. A test that doesn't update the assembly isn't counted, so an assembly tested in XXXX may not count as tested at all if a newer test (say, from the next year) was accepted first.

  • The report reads the history, so a test in XXXX that updated the assembly still counts as tested after it's reset. If the reset brings back an earlier test that's also from XXXX, the result becomes that test's result. Otherwise the result stays the reset test's result. A test entered with the wrong year and then fixed still counts as tested in the wrong year.

  • An assembly tested in XXXX doesn't count in J if it's no longer in line I, for example because it was replaced, removed from its location or set to Inactive later in XXXX.

J. Fail: the same as Pass, except the most recently saved of those entries (the ones with a Last Tested On in XXXX) had a Last Test Result of Fail.

J. Total: Pass + Fail.

How Survey Dates Work

Each location has one survey record behind its Last Surveyed On, Next Survey Due and Last Survey Result. Line D reads its first survey date, and line E reads its history.

  • Accepting a survey: it only updates the record if its Surveyed On date is on or after the location's current Last Surveyed On, including a date entered by hand or loaded when your data was first loaded into SwiftComply. On the same day, a pass replaces a fail, a fail doesn't replace a pass, and otherwise the one submitted later wins. When it updates the record, Last Surveyed On becomes the survey's Surveyed On date.

  • Passing survey: moves the Next Survey Due to the date figured when the survey was submitted. That's normally one survey period after the survey date. With Preserve Date on, it's the old due date moved forward by whole survey periods until it's on or after the survey date (with default settings), and a survey done more than the allowed number of days before the due date (90 by default) leaves the Next Survey Due alone.

  • Failed survey: leaves the Next Survey Due where it was. If the location has no survey dates yet (its first survey, or the first one after a reset removed them), the Next Survey Due is set to one survey period before the survey date (moved to the end of that month if your organization uses end-of-month due dates), so the location shows as past due.

  • First survey date: saved when the record is first created and never changed after that, even by hand edits. It isn't shown anywhere in SwiftComply. If the record is removed, the next one starts a new first survey date. Resetting a location's only accepted survey removes the record, along with every survey date on the location, including ones entered by hand.

  • Previous due date: used by line E, and saved with each change in the history. When the Next Survey Due moves later and the Last Survey Result is Pass after the change (from a survey or a hand edit), the old Next Survey Due is saved as the previous due date. When the record is first created as passing, the previous due date is set to its Last Surveyed On date. Failed surveys don't change it, resets don't roll it back, and a location whose first survey failed starts with no previous due date. It isn't shown anywhere in SwiftComply, including the Compliance history tab.

  • Dates entered by hand: entering survey dates by hand on the location changes the same record and is saved in its history. If a location has no survey dates, entering only a Next Survey Due fills in Last Surveyed On as one survey period before it (or today, if that would be in the future) and sets the result to Pass. Picking only a Last Survey Result fills in today's date and time as Last Surveyed On, with a Next Survey Due one period later for Pass, or today for Fail (the end of the month, if your organization uses end-of-month due dates). Either way, that Last Surveyed On becomes the first survey date and counts in D for the year it falls in. Last Surveyed On can't be entered as a future date.

  • Compliance history tab: shows the same history line E reads, with each change's Compliance Date (Last Surveyed On), Expiration Date (Next Survey Due), whether it was compliant, and who changed it and when. It doesn't show the previous due date.

How Assembly Location Dates Work (Lines I and J)

SwiftComply keeps a location record for each location an assembly has been at, with its Installed On, Set Inactive On and Removed On dates. Line I reads those dates. It doesn't look at the assembly's Status.

  • Set to Inactive: saves that day's date as Set Inactive On on the assembly's current location record. Setting it back to Active clears the date on the current location record only.

  • Edit form: saving the Edit form of an assembly that's already Inactive keeps its Set Inactive On date. When the assembly has a Set Inactive On date, it can also be changed by hand on the Edit form. Quick edits on the Details tab don't reset it.

  • Remove from Location: sets Removed On and keeps the location record.

  • Change Location: sets Removed On on the old location record and makes a new one, copying its Installed On, Set Inactive On and Assembly Location notes. The assembly counts once, at its new location. An Inactive assembly moved this way keeps its Set Inactive On date.

  • Delete from Location: erases the location record, so the report acts like the assembly was never there, in every year. Deleting a location does the same to every assembly's record at it.

  • Replace: from the assembly page, the old assembly is kept at the location and set to Inactive by default. If "keep at location" is unchecked, it's removed from the location instead. Adding a new assembly as a replacement works the same way, and so does a tester replacement accepted from a test report.

  • New assemblies: Installed On starts blank unless it's entered, including assemblies added by a tester through a test report. So a past year's report picks up assemblies added since then.

  • Created as Inactive: the location record gets the day the assembly was created as its Set Inactive On date. For assemblies billing sync creates as Inactive, that's the day of the sync. For assemblies that were already Inactive when your data was first set up in SwiftComply, it's the day they were loaded.

  • Moving back: an assembly moved back to a location it was at before reuses its old location record there. Removed On is cleared, and its Installed On, Set Inactive On and Assembly Location notes are replaced with the ones from the location it's moving from. If the assembly is Inactive and the location it's moving from has no Set Inactive On date, the old record keeps its own date when that date falls in the assembly's current Inactive period. Otherwise it gets the day the assembly was set Inactive, if SwiftComply has one.

FAQ

Why does D plus the two "reinspections completed" lines come out lower than the number of surveys done?

  • Each line counts a location once, no matter how many surveys it had.

  • D and E only see accepted surveys and dates entered by hand. Surveys that were never accepted aren't counted there.

  • A survey at a location that already had survey dates before XXXX can't count in D. It only shows up if it counts as completed in E.

  • A survey dated before the location's current Last Surveyed On doesn't change anything when it's accepted.

  • While a location's Next Survey Due is still in XXXX, a failed survey, or a passing survey done too early to change the due date, doesn't count as completed.

  • With Preserve Date on, a passing survey done after the due date can get a new due date later the same year, so it doesn't count as completed.

  • A second passing survey in the same year can take the location out of line E completely.

  • A survey done in the year before a location was due doesn't count as completed in either year.

  • A survey dated Jan 1 doesn't count as completed.

  • Locations without one of the five Zoning values aren't counted anywhere.

Why did a past year's numbers change when the report was run again?

Most lines read current data, or the history as it is now. These changes move past years:

  • Zoning, Hazard Level and deleting a location change C, the High/Low split and every other line.

  • D changes if a survey dated in XXXX is accepted later, or a location's only survey is reset.

  • E changes with edits saved after the year ended. For example, a location surveyed in Feb 2026 counts as completed in 2026. If its Next Survey Due is extended by hand in Jan 2027 while the Last Survey Result is Pass, re-running 2026 no longer counts it as required or completed. Accepting a newer survey and then resetting it can do the same.

  • F changes if a survey dated in XXXX is entered later, and G uses each survey's current status.

  • I and J change when assemblies are removed, moved, replaced, set to Inactive or deleted after the year, when assemblies added later have a blank Installed On, and when Last Test Result is changed by hand.

Why is "required" so much higher than "completed"?

Required includes every location whose Next Survey Due is on or before Dec 31 of XXXX, including ones that were already past due before XXXX, so required is normally higher than completed even after the year is over. When the current year is run before it's over, completed only has the surveys done so far.

Why is J lower than the number of tests done?

J counts each assembly once, and only assemblies in line I. An assembly tested in XXXX doesn't count if it was later replaced, removed from its location or set to Inactive during XXXX, or deleted at any time. A test that was accepted after a newer one doesn't count either.

Can I see which locations are in each line?

No. The report screen only shows counts. The Locations list gets close for C and the High/Low split: show inactive locations too, and add the srp:zoning and srp:hazard_level columns (under State Report Location Details). That list only covers the organization you're in, not child organizations.

The other lines can't be rebuilt from a list. The first survey date (D) isn't shown anywhere in SwiftComply, E reads the history of each location's survey dates, and the Corrective Action Required answer (F and G) isn't in any list, so each survey would have to be opened. The location's Compliance history tab helps trace E for one location.


0001.jpg
0002.jpg
0003.jpg
0004.jpg
0005.jpg
0006.jpg
0007.jpg
0008.jpg
0009.jpg
0010.jpg
0011.jpg
0012.jpg
0013.jpg
0014.jpg
0015.jpg
0016.jpg
0017.jpg
0018.jpg
0019.jpg
Did this answer your question?