← Back to engineering questions
QuestionHVAC maintenance

Is our HVAC maintenance program enough for microbial control?

A practical screening guide for moving beyond contractor attendance to asset-based maintenance, defect close-out and useful records.

The strongest evidence of an adequate program is not how often a contractor visits. It is whether the right assets are inspected, defects are acted upon and the building retains a coherent history.

01

The practical answer

Maybe. A good program should connect assets, tasks, frequencies, competent personnel, service reports, defects, rectification and records. Repeated unresolved moisture or cleanliness problems are a sign that maintenance alone may not be enough.

AS/NZS 3666.2 sets a routine operation and maintenance framework for air-handling and water systems. It also emphasizes manuals and maintenance records.

Where the same defect appears repeatedly, the owner should ask whether the problem is a design issue under AS/NZS 3666.1 rather than simply scheduling more cleaning.

Cooling water and seasonal systems need clear treatment, cleaning, shutdown and restart records in addition to general HVAC servicing.

02

When this question usually matters

AHUs repeatedly have wet filters, blocked drains or odour complaints.

A building uses several HVAC contractors and records are fragmented.

A cooling tower or water system has seasonal shutdowns.

An audit asks for maintenance evidence that the owner cannot readily produce.

The same defect appears in service reports without clear close-out.

03

Red flags that make the question more significant

01

Assets are named differently in different reports.

02

No one owns defect close-out.

03

Maintenance manuals do not reflect current alterations.

04

Seasonal restart procedures are informal.

05

Recurring moisture problems are repeatedly cleaned but never engineered out.

04

How to review the maintenance program

Follow one asset from task to report to defect to close-out. If that chain is weak, the program probably is too.

1

Build the asset list

Identify AHUs, intakes, filters, coils, terminal units, cooling towers and water-treatment systems.

2

Map tasks and frequencies

Inspection, cleaning, testing, calibration and treatment should be explicit.

3

Review service reports

Look for repeated defects and missing evidence.

4

Check close-out

Confirm that reported problems lead to rectification and verification.

5

Escalate design problems

Recurring drainage, moisture or access problems may require engineering changes.

6

Preserve the history

Keep current manuals, alterations, reports and results available and understandable.

05

Detailed practical examples

These examples show how the question changes a real engineering decision. They are not universal answers; they show what needs to be clarified before the right answer becomes obvious.

Case study 1 · Repeated AHU defects

Monthly reports mention the same blocked drain for six months

01
Project context

A service contractor records and clears the same drain blockage repeatedly. Odour complaints continue.

Why this question matters

The program is active but not effective if the root cause remains unresolved.

What made the job difficult

  • No defect owner exists.
  • Reports are filed as completed work.
  • The drain geometry may be a design issue.

How the review should proceed

  1. Track the issue across reports.
  2. Create a defect close-out action.
  3. Assess the drainage design under AS/NZS 3666.1.
  4. Verify the permanent fix.
Practical outcome

Maintenance becomes a feedback system instead of repeated symptom treatment.

Case study 2 · Fragmented records

Cooling-tower service history is spread across three contractors

02
Project context

An owner cannot quickly show inspection, treatment, cleaning and defect history for the last five years.

Why this question matters

The absence of a coherent record weakens future engineering and compliance decisions even if work was probably performed.

What made the job difficult

  • Different asset names are used.
  • Calibration records are incomplete.
  • Defects cannot be linked to close-out.

How the review should proceed

  1. Create one asset index.
  2. Map historical records to assets.
  3. Identify missing evidence and unresolved defects.
  4. Standardize future reporting.
Practical outcome

The owner gains a usable maintenance history rather than a larger document archive.

06

Information to gather before deciding

Asset register

Maintenance manuals

Task and frequency schedule

Service reports

Defect register

Close-out evidence

Water-treatment records

Calibration records

Seasonal shutdown/restart procedures

Alteration history

07

Likely outcomes

1

Program is broadly effective

Assets, tasks, records and defect close-out form a coherent control system.

2

Program needs management improvement

Maintenance work occurs, but asset naming, records or defect ownership are weak.

3

Engineering modification required

Recurring problems point to design, drainage or access issues that routine maintenance cannot solve.