AOV & Smoke Vent Testing PPM Services UK – 6-Monthly Function

Why 6‑monthly AOV and smoke vent testing matters

If you are the Responsible or Accountable Person for a residential block, you must be able to prove that AOV and smoke vent systems still work when needed. One vague “system OK” line is rarely enough when insurers, assessors or the fire service start asking questions.

A structured 6‑monthly function test exercises real triggers, follows the sequence through to vents or fans and confirms a clean reset with usable evidence. Instead of guesswork, you gain clear records that support your fire strategy, maintenance planning and audit defence without overcomplicating day‑to‑day management.

• Prove end‑to‑end operation from trigger to vent or fan
• Get clear, audit‑ready reports you can show to regulators
• Separate user checks from competent‑person testing to buy correctly

6‑Monthly AOV & Smoke Vent (SHEV) Function Testing — prove end‑to‑end operation with retrievable evidence

You use a 6‑monthly AOV and smoke vent test to prove the system still works when you need it and to show exactly how you know.

In many blocks the vents were installed at handover, commissioned once and then left alone until a fire risk assessment, insurer query, new managing agent or fire service audit puts them under the spotlight. At that point a generic “system OK” certificate will not carry you very far.

A well‑planned 6‑monthly function test starts at a real initiating input and follows the sequence through to vents or fans, then back to a clean reset. A specialist smoke control engineer uses the configured trigger, watches what the panels and field devices do, confirms the system returns to normal and records what actually happened in a way you can reuse.

Under the Regulatory Reform (Fire Safety) Order 2005 you, as Responsible Person or Accountable Person, must keep fire precautions on a suitable system of maintenance. Six‑monthly AOV and SHEV function testing is a straightforward way to show that smoke ventilation measures are being maintained in efficient working order, with a dated trail of what was done, when and by whom.

All Services 4U is a specialist smoke control contractor and our engineers build every visit around that duty. You see what was triggered, what moved, what did not, and what we recommend next, rather than being left trying to defend vague paperwork.

If you want engineer‑led proof that your smoke vents operate on demand, with audit‑ready documentation you can stand behind, book a 6‑monthly function test with our specialist team.

What 6‑monthly AOV & SHEV function testing means (and what it doesn’t)

A 6‑monthly AOV and SHEV function test is a live cause‑and‑effect check on the real installation, not a quick glance at the panel.

What it is in plain English

In a typical block, an Automatic Opening Vent (AOV) or smoke and heat exhaust ventilation (SHEV) system is designed so that a fire condition signal operates specific vents or fans and shows clear indications on a control panel. A 6‑monthly function test takes that sequence and proves it still works in practice.

An engineer triggers the system through the configured inputs, then observes how panels and field devices respond. They check that the system can be reset to normal and write down what was seen in a way you can show to fire risk assessors, regulators or insurers.

What it is not

A 6‑monthly function test is not design work, commissioning or certification. It will not make a non‑compliant design compliant and it does not remove the need to fix known defects. Findings from the visit should feed into remedial works, which are then re‑tested against agreed acceptance criteria.

It is also not the same as a caretaker pressing a local “open” switch. Routine user checks are useful, but they rarely prove interfaces, reset logic or standby power in the way a competent‑person function test does. Keeping that distinction clear helps you buy the right service and explain what has and has not been covered.

What’s included in a 6‑monthly visit: interface testing from trigger to vent/fan and safe reset

A credible 6‑monthly function visit follows the full chain your fire strategy relies on, from trigger to output and back to normal.

Triggers and inputs

Across your programme of visits, each relevant initiating method should be exercised at least once, for example:

• fire alarm interfaces or input modules that send a “fire” signal to the smoke control panel
• local smoke vent switches on corridors or stair cores
• firefighter override or priority controls where fitted

For each scenario, you agree in advance which trigger will be used, which devices should respond and how that will be recorded. That removes debate later about what was or was not included.

Controls, indications and feedback

The engineer then proves the control equipment behaves properly. Panels or controllers should change state as designed, show clear “fire” indications and raise visible faults where circuits are supervised. Loss of communication or device failure should never sit silently until a real incident exposes it.

By tying each state change back to the trigger used, you gain a clear cause‑and‑effect record instead of a vague “system OK” line.

Outputs, reset and “left safe”

Finally, the outputs are observed. Vents, actuators and any smoke‑extract fans are checked for real movement and end‑positions within safe access limits. The engineer then carries out a controlled reset, removes temporary overrides and confirms the system has returned to its intended normal condition with monitoring re‑enabled.

That last step matters: you want documented confirmation that nothing has been left disabled, isolated or in manual mode when the engineer leaves site. Ask us to scope your next 6‑monthly AOV function visit to this standard so you know exactly what has been proven.

Pass/Fail criteria & the evidence you should receive (reporting, logs, photos, cause‑and‑effect outcomes)

A 6‑monthly visit is only as useful as the evidence it leaves behind and how clearly that evidence is presented.

What your report must contain

As a minimum, your report should show for each asset or scenario:

• where it is (asset ID and location)
• what was done to trigger it
• what was expected to happen
• what actually happened
• the condition after reset (normal, faulted, isolated)
• who tested it and when

Those fields give you something you can lay alongside the fire strategy, feed into a digital system or present in an audit without extra explanation.

How passes, failures and limitations are recorded

A “pass” should always be tied to a defined scenario and acceptance criteria, for example “triggered by fire alarm interface X, vent Y opened fully and indicated open, system reset to normal”.

If something fails, the report should say what was affected and what interim measures and remedial action are required before the next test. Where access, safety or resident constraints prevent full proving, that must appear as a limitation with the reason and the enabling works or alternative method required. It should never be hidden inside a blanket “satisfactory”.

Using photos and logs sensibly

Selective photographs can help you and future contractors identify panels, vents and locations, but they should be linked to specific findings rather than filling the report with unstructured images. Your provider should avoid unnecessary images of residents or belongings and make sure logbook entries are easy to file, search and understand months or years later.

Accreditations & Certifications

Why 6 months is the norm: risk‑based assurance for safety‑critical smoke ventilation

Six months is a practical interval that balances risk, deterioration and how often you can realistically bring engineers to site.

Why six months is commonly chosen

For safety‑critical systems, inspection intervals are set so that likely deterioration is found in time but visits remain workable. AOVs and smoke control components can suffer wear, contamination, water ingress or electrical faults that will not show up in a simple visual check. A mid‑year function test cuts down the period a hidden fault can sit between annual services or major reviews.

Many maintenance schedules pair regular user checks by caretakers with competent‑person functional tests every six months, then use an annual service to follow manufacturer’s instructions and relevant smoke‑control maintenance guidance.

What happens when tests slip

When six‑monthly visits are missed you create gaps in the logbook, increase the chance that the next test uncovers multiple defects and make it harder to answer direct questions from fire and rescue services, regulators, insurers or residents. For higher‑risk residential buildings, building safety legislation places greater emphasis on documented, continuous management of fire precautions, so missing cycles without a clear catch‑up plan quickly becomes a governance issue.

How 6‑monthly fits with your other checks

Weekly or monthly checks by caretakers or site staff are ideal for obvious issues: signs of damage, obstructions, controls left in manual, visible panel faults. Six‑monthly and annual competent‑person visits then deal with interfaces, detailed functional proving and deeper inspection. Taken together, they give you a layered regime that is risk‑based, defensible and easier to explain to boards, residents and regulators.

AOV vs full SHEV/Smoke Control: identify what you have on site (and map it to the right evidence)

You can only test properly if you are clear what system you actually have and what the fire strategy expects it to do.

AOV‑only arrangements

In some lower‑rise or simpler blocks, the arrangement may be limited to natural AOVs: a stair head vent and end‑of‑corridor vents, often with simple local controls and a basic panel. In these cases, the focus is on proving that the configured triggers operate the specific vents and that those vents physically open and close as intended, with the panel monitoring the circuits and resetting reliably.

Full smoke control systems

Other buildings use more complex smoke control, such as smoke shafts with dampers, mechanical extract fans or pressurisation systems. These may include multiple control panels, integration with the fire alarm, firefighter controls, pressure sensors and powered smoke control components.

In those cases, the 6‑monthly function test must be matched to the system architecture and the fire strategy. That means proving not only that devices move, but that the right combination of vents, dampers and fans respond in each scenario.

Why classification matters

Treating every system as if it were a single AOV risks under‑testing complex arrangements. Treating every building like a major engineered system risks unnecessary disruption and spend. The right approach is to classify what is installed, check it against the strategy, decide which standards and guidance are relevant and design the test around that reality. Your test reports should then describe the system in those terms, so anyone reviewing the evidence can see that the right thing was proven.

Responsibilities in residential blocks: dutyholders, competent delivery, and missed‑test control

Clarity about who is responsible for what makes it much easier to keep AOV and smoke vent testing on track.

Who is accountable

In England and Wales, the legal duty to maintain fire precautions sits with the person or organisation in control of the premises. That may be the freeholder, landlord, housing association, RMC or RTM company, or a managing agent where they have sufficient control. That Responsible Person or Accountable Person may appoint agents and contractors, but accountability for arranging, completing and recording testing does not transfer.

You should still be able to point to an up‑to‑date maintenance regime, logbook entries and service reports if challenged.

How tasks are shared in practice

Day to day, you will usually see:

• the dutyholder or board setting policy and approving budgets
• a managing agent or in‑house team arranging visits, access and resident communications
• a specialist smoke control contractor carrying out the testing and issuing reports
• on‑site staff doing simple visual and functional checks between visits

It helps to name a single “record owner” for the fire safety logbook or digital equivalent, so reports are stored consistently and can be retrieved quickly.

What to do if tests have been missed

If you discover gaps, the safest route is to treat them as a non‑conformity, not an embarrassment to hide. That means recording which tests were missed and over what period, considering whether interim measures are needed until proof is restored, arranging a catch‑up function test with a defined scope and date, and documenting limitations honestly in the logbook and the next report.

If you have gaps in your logbook, you can share them with All Services 4U and we will design a catch‑up function test programme so you move from uncertainty back to a clear, dated trail.

Reliable Property Maintenance You Can Trust

From routine upkeep to urgent repairs, our certified team delivers dependable property maintenance services 24/7 across the UK. Fast response, skilled professionals, and fully insured support to keep your property running smoothly.

Book Your Service Now

Book Your Free Consultation With All Services 4U Today

You often do not need a full tender exercise to get control of AOV and smoke vent testing.

You need clarity, a sensible scope and a provider who will stand behind the evidence. On a short consultation call, you explain your building or portfolio, any current fire risk assessment actions and what you already know about the installed system. We ask practical questions about building type and height, numbers of vents or shafts, panel locations, existing fire alarm integration and access constraints, then outline a test sequence and evidence pack that fits.

After that consultation you leave with:

• a proposed 6‑monthly test sequence matched to your building and fire strategy
• a clear outline of the evidence pack and reporting format you can file and share
• an agreed approach for handling limitations, defects and any catch‑up testing you need

You see in advance what our engineers will trigger, what they will observe, what they will record and how limitations and defects will be handled. That means fewer surprises on the day, fewer aborted visits and reports you can share with boards, residents, fire risk assessors, regulators and insurers.

If you want to turn “we think it works” into “here is exactly when and how it was proven”, share your building details and preferred dates with All Services 4U and book your consultation today.

Frequently Asked Questions

Explore our FAQs to find answers to planned preventative maintenance questions you may have.