Home / LEV Testing / Guide
LEV testing - filter intervals
It is tempting to want a simple answer - change the filter every so many months. But a filter does not load by the calendar; it loads by how much dust it captures, which varies hugely with the process. So the honest trigger for replacement is the filter's condition, read from its pressure drop, not a fixed date on a wall planner.
The short answer
There is no single right interval for changing an LEV filter, because filters load by how much dust they capture, not by the passage of time. A filter on a heavy-dust process loads far faster than one on a light process, so the same calendar interval would be far too long for one and needlessly short for the other. The honest trigger is the filter's condition, measured as the pressure drop across it: as the filter loads, the pressure drop rises, and once it reaches the point the manufacturer specifies, the filter needs changing. So the interval is set by monitoring, guided by the manufacturer's data - not by a fixed date.
Why there is no single interval
The natural instinct is to schedule filter changes like an oil change - every so many months, marked on the calendar. But a filter is not like engine oil, which degrades with time and use in a fairly predictable way. A filter loads by capturing dust, and how fast it loads depends entirely on how much dust the process throws at it. A filter on a heavy-dust process might load in a fraction of the time a filter on a light process takes. So there is no single interval that fits both - a date that is right for one is wrong for the other.
This is why asking how often to change an LEV filter has no honest fixed answer. The real driver is the dust loading, and that varies with the process, the throughput, and how the system is used. Two identical filters on two different processes can need changing at very different times. A calendar interval imposed across the board would leave heavy-dust filters dangerously overloaded and change light-dust filters far too early. The right approach follows the actual loading, not an arbitrary date - which means watching the filter's condition rather than the calendar.
The honest trigger
The condition of a filter - how loaded it is - is measurable as the pressure drop across it, the difference in pressure between the dirty and clean sides. A fresh filter has a low pressure drop; as it loads, the pressure drop rises. This gives a direct, objective read on how much life the filter has left. So rather than guessing from a calendar, you can watch the pressure drop and change the filter when it reaches the point that signals the filter is loaded - the honest trigger, because it responds to the actual loading rather than an assumed rate.
Manufacturers typically specify the pressure drop at which a filter should be changed - the figure at which the filter is considered loaded and its resistance is choking the airflow. Fitting a simple gauge to read the pressure drop turns this into a practical routine: watch the reading, and when it hits the manufacturer's change point, replace the filter. This means the filter is changed exactly when it needs changing - not too early, wasting a filter with life left, and not too late, when the loaded filter has already been choking the airflow and degrading control. The pressure drop makes the interval self-adjusting to the actual conditions.
Why calendar-only fails both ways
Relying on a calendar interval alone fails in both directions. Set the interval to suit a heavy-dust process and a light-dust filter gets changed while it still has plenty of life - wasteful, though at least safe. Set it to suit a light process and a heavy-dust filter is left in place long past the point it has overloaded - by which time its resistance has been choking the airflow for weeks or months, cutting the capture velocity and letting exposure slip. The second failure is the dangerous one, because it means the system has been under-performing unnoticed.
And because dust loading is not perfectly steady - it rises and falls with how hard the process is run - even a well-chosen calendar interval drifts out of step with reality over time. A busy spell loads the filter faster than usual; a quiet spell slower. A fixed date cannot track that, but the pressure drop can, because it responds to the actual loading whatever the cause. So the pressure-drop trigger is not just more efficient than a calendar; it is safer, because it catches an unexpectedly fast-loading filter that a calendar would miss until the next scheduled change came round - by which point control may have been lost for some time.
What this means in practice
In practice, then, managing filter replacement means monitoring rather than scheduling. Fit a gauge to read the pressure drop across the filter, know the manufacturer's change point for that filter, and replace the filter when the reading reaches it. This ties the replacement to the actual loading, so the filter is changed when it genuinely needs to be, whatever the process is doing. A rough calendar expectation is still useful as a planning aid - so you can anticipate roughly when a change is likely and have filters on hand - but the trigger to actually change is the condition, not the date.
The thorough examination fits into this too. The test assesses the filter and its pressure drop, so it is a periodic check that the filter regime is working and the filter is not choking the system. But the test comes round only on its cycle, whereas the filter loads continuously - so the routine pressure-drop monitoring between tests is what keeps the filter changed at the right time day to day. The two work together: routine monitoring catches the loading as it happens, and the periodic test confirms the whole system, filter included, is still controlling exposure. Condition-based replacement, guided by the manufacturer's data, is the honest way to run it.
The takeaway
There is no single right interval for changing an LEV filter, because filters load by how much dust they capture, not by the passage of time - and that varies enormously with the process. A calendar interval imposed across the board leaves heavy-dust filters overloaded and changes light-dust filters too early. The honest trigger is the filter's condition, read from the pressure drop across it: change the filter when the pressure drop reaches the manufacturer's specified point.
So the practical approach is to monitor rather than schedule - fit a gauge, know the change point, and replace the filter when the loading calls for it, whatever the calendar says. A rough time expectation helps with planning and stocking filters, but the trigger is the condition. This keeps the filter changed exactly when needed - not wastefully early, and not dangerously late when a loaded filter has been quietly choking the airflow. Watching the pressure drop is what makes filter replacement follow reality rather than a guess.
Questions
There is no single right interval, because filters load by how much dust they capture, not by time. A heavy-dust process loads a filter far faster than a light one. The honest trigger is the filter's condition, read from the pressure drop across it, not a fixed calendar date.
The pressure drop across a filter rises as it loads. Manufacturers specify a figure at which the filter is considered loaded and should be changed. Fitting a gauge to read the pressure drop and changing the filter when it reaches that point ties replacement to the actual loading.
Because it fails both ways. Set to suit a heavy process, it changes light-dust filters too early and wastefully; set to suit a light process, it leaves heavy-dust filters overloaded and choking the airflow long past their useful life. Loading varies too much for a fixed date to track.
As a planning aid, yes - a rough expectation of when a change is likely helps you anticipate it and keep filters on hand. But it should not be the trigger to actually change. The trigger is the measured condition, so the filter is changed when it genuinely needs to be.
The test assesses the filter and its pressure drop periodically, confirming the filter regime is working. But the filter loads continuously while the test comes round only on its cycle - so routine pressure-drop monitoring between tests keeps the filter changed at the right time day to day.
A loaded filter left in place chokes the airflow, cutting the capture velocity at the hoods and letting exposure slip - unnoticed, because the system still runs. Condition-based replacement catches an unexpectedly fast-loading filter that a calendar would miss until the next scheduled change.
Our thorough examination assesses your filters and their pressure drop - so you know whether your replacement regime is keeping the filter changed before it chokes the airflow.
