SwiftComply works out calculated results for you. When you save sample data on a sample report, it finds the calculated result requirements on that report, gathers the sample results that belong to each one, and fills in the value — averages, minimums and maximums, across periods from daily to annual.

This article covers concentration and measurement calculations. Mass and mass rate calculations work slightly differently and are covered in Setting Up Mass Loading Calculations.

On save. There is no button and nothing to schedule.

If you later add, change or delete sample data, saving again recalculates whatever that data affected. A calculated result with no matching sample data stays empty.

Calculations run for parameters measured in:

The available calculations are:

Each calculated result has a due date, and its calculation period decides how far back to look.

Every window is measured in whole calendar days, ending at the end of the due date's day, then reaching back by the period — 1 day for Daily, 4 for 4 Day Consecutive, 7 for Weekly, 30 for 30 Day, and whole calendar months for Monthly, 6 Month and the annual periods.

💡 The due date's time of day makes no difference. A calculation due at 4 PM and one due at 11 PM on the same day look at exactly the same data. You never need to reason about due times when working out which results were counted.

A result is included when:

⚠️ A result with no sample end date is never included, even if it has a start date. This is the most common reason a calculated value looks wrong or stays empty.

Results you added yourself as one-off sampling events count exactly like scheduled ones. If the analyte and the end date fit, the result is used.

Times are compared to the minute, so seconds never matter.

The calculation converts everything to one unit before doing the maths.

Non-detects are included, not skipped:

This matters most for minimums and averages, where a non-detect counted as zero pulls the result down.

You can type your own value over any calculated one. The row shows that a manual value is in use, and the system's own figure is kept — so you can restore it whenever you like.

💡 A manual value is independent of the sample data. Deleting the sample results behind it does not remove your override, and recalculating does not overwrite it. If you want the system's figure back, clear the manual value.

Every calculation records which sample results it used, their values and units, and the date range it applied. If a figure looks wrong, that record shows whether the cause was a result that shouldn't have been counted, one that was missed, or a unit conversion.

A value is stored at full precision and rounded only when it is displayed.

💡 A value you type into Manual Value is shown exactly as you typed it. This rounding only ever applies to the system's own figure, so your entry is never quietly reshaped.

Because the rounding happens at display time, changing a limit's precision updates existing rows without anything being recalculated.

No sample result matched the analyte and window. Check the analyte matches and the results fall in the period.

It has no sample end date. Add the end date — the start date is not used.

It is on a different sample report. Only results on the same report are eligible.

A non-detect without an MDL counted as zero. This is expected — record an MDL if the method has one.

Its unit is a different kind from the calculation's. Only compatible units are converted.

A manual value is in use. Clear the manual value to restore the calculated one.

Windows are whole calendar days and due times are ignored, so this is expected.

It is rounded to the applicable limit's decimal places, or to 3 significant figures when no limit applies. This is expected — see How values are rounded.