Home / LEV Testing / Guide
LEV testing - the schedule
Everyone agrees LEV needs maintaining between tests - and then, without a plan, it quietly does not happen. A written maintenance schedule is what turns good intentions into a routine that actually holds up: defined tasks, at defined intervals, with someone responsible and a record kept.
The short answer
A maintenance schedule that holds up turns the general idea of keeping LEV working into a concrete plan: it lists the specific maintenance tasks (checks, filter changes, cleaning, servicing), the interval for each (daily, weekly, periodic), who is responsible for each, and it records that each was done. Without that structure, maintenance depends on memory and good intentions and quietly lapses. With it, the upkeep happens reliably and is evidenced - which is what keeps the LEV genuinely working between the statutory tests.
Intentions aren't a plan
Everyone agrees that LEV needs maintaining between the statutory tests - the checks, the filter changes, the cleaning, the prompt fixing of faults. The problem is that agreement is not a plan, and without a plan, the maintenance quietly does not happen. It depends on someone remembering, having time, and knowing what to do - and in a busy workplace, tasks that depend on memory and good intentions are exactly the ones that slip. The system runs, nothing obvious goes wrong for a while, and the maintenance drifts.
A written maintenance schedule is what closes that gap between intention and action. It turns the general idea of keeping the LEV working into a defined routine - specific tasks, at specific intervals, assigned to specific people, and recorded. That structure is what makes the maintenance actually happen reliably, rather than depending on someone remembering. So a schedule is not bureaucracy for its own sake; it is the mechanism that turns the good intention of maintaining the LEV into a routine that holds up over time, which good intentions alone do not.
Define the tasks and intervals
The foundation of the schedule is defining the tasks and how often each is done. The tasks are the specific maintenance actions the LEV needs: the daily and weekly user checks (looking and listening, watching airflow indicators, checking for damage and capture), the periodic replacement of consumables like filters before they clog, the cleaning of the system, and the servicing of components. Listing them concretely - what specifically needs doing - is the first step, because a task that is not defined is a task that does not get done.
Each task then gets an interval matched to how often it genuinely needs doing. The daily checks are daily; the weekly checks weekly; filter changes on a schedule suited to how fast they load; cleaning and servicing at appropriate periods. The intervals should reflect the real needs of the system - a filter that loads quickly needs changing more often than one that does not. So the schedule pairs each defined task with a defined interval, turning a vague sense of ongoing maintenance into a concrete list of what to do and how often, which is what makes the routine specific enough to actually follow.
Assign responsibility
A schedule of tasks and intervals still fails if no one is responsible for doing them - a task that is everyone's job is no one's. So a schedule that holds up assigns responsibility: each task has someone accountable for making sure it is done. The daily and weekly checks might be the operators' responsibility; the periodic filter changes and servicing someone else's, or an external provider's. What matters is that for each task, it is clear who does it, so it does not fall between people and lapse.
Assigning responsibility is what turns the schedule from a list into a working routine, because it gives each task an owner who is accountable for it happening. Without that, the schedule describes what should be done but relies on someone spontaneously taking it on - which is the same gap a schedule was meant to close. So clear ownership of each task is essential: the daily checks owned by the operators, the periodic maintenance owned by whoever does it, and the whole schedule overseen by someone responsible for it as a whole. Defined responsibility is what makes the defined tasks actually get done.
Record and review
The final elements that make a schedule hold up are recording and reviewing. Recording that each task was done - a simple log or checklist - does two things: it confirms the maintenance actually happened rather than being assumed, and it creates evidence of the upkeep, which supports the compliance picture alongside the statutory test reports. A schedule with no record leaves you unable to know, or show, whether the maintenance was actually carried out. So the schedule should include recording each completed task, keeping the routine honest and evidenced.
And the schedule should be reviewed periodically to keep it fit, because the system and its needs can change - a filter that starts loading faster, a new part needing servicing, a task that turns out to need doing more often. Reviewing the schedule against how the system actually behaves keeps it matched to the real needs rather than becoming an outdated document. So a schedule that holds up is one that is recorded (so it is done and evidenced) and reviewed (so it stays fit) - the two things that keep it a living routine rather than a document that is written once and then quietly ignored, which is exactly the fate a schedule exists to prevent.
The takeaway
Keeping LEV working between tests needs a plan, not just good intentions - and a written maintenance schedule is that plan. It holds up when it defines the specific tasks (the checks, filter changes, cleaning, servicing), sets an interval for each matched to real need, assigns clear responsibility so each task has an owner, and records that each was done - reviewed periodically to stay fit for the system.
Without that structure, maintenance depends on memory and quietly lapses, however genuine the intention. With it, the upkeep happens reliably and is evidenced, which is what keeps the LEV genuinely controlling exposure between the statutory tests. The schedule is the mechanism that turns agreeing the LEV needs maintaining into the LEV actually being maintained - tasks, intervals, responsibilities and records, kept fit by review. That structure is what makes a maintenance schedule one that holds up rather than one that is written and forgotten.
Questions
Defining the specific tasks (checks, filter changes, cleaning, servicing), setting an interval for each matched to real need, assigning clear responsibility so each task has an owner, and recording that each was done - reviewed periodically to stay fit for the system.
Because agreement is not a plan. Without structure, maintenance depends on someone remembering, having time and knowing what to do - and those tasks quietly slip in a busy workplace. A written schedule turns the intention into a routine that actually happens.
The daily and weekly user checks, the periodic replacement of consumables like filters before they clog, the cleaning of the system, and the servicing of components - listed concretely, because a task that is not defined is a task that does not get done.
Because a task that is everyone's job is no one's. Assigning each task an owner who is accountable for it happening is what turns the schedule from a list into a working routine - the daily checks owned by operators, the periodic maintenance by whoever does it.
Recording each completed task confirms the maintenance actually happened rather than being assumed, and creates evidence of the upkeep that supports the compliance picture alongside the statutory test reports. A schedule with no record leaves you unable to know or show it was done.
Because the system and its needs change - a filter loading faster, a new part needing servicing, a task needing doing more often. Reviewing the schedule against how the system actually behaves keeps it matched to real needs rather than becoming an outdated document.
We carry out the statutory examination and test, and can help build a maintenance schedule - tasks, intervals, responsibilities and records - that keeps your LEV working between examinations.
