6 Aircon Service Report Fields Facilities Managers Need
An aircon service report should answer six simple questions. Which unit was involved? What was reported? What work was done? What was found? Did the work change the fault? What remains open? Use these as an operating template, not a statutory report format.
By Team Snowflake | Updated 15 Sept 2026
What should a useful service report let a facilities manager decide?
The report should support the next work-order decision. It should identify the affected asset, show what work occurred and preserve the evidence. The facilities manager can then close the item, monitor it or send it for a separate repair scope.
A completed checklist is not useful if it hides the unit, complaint or result. For a building with split, cassette or ducted units, the report needs a per-unit trail rather than one general statement for the whole site.
| Decision | Evidence needed from the report |
|---|---|
| Close the work order | Completed scope and a recorded result for the correct unit |
| Monitor a condition | Observed finding, current effect and a clear trigger for review |
| Approve a separate repair | Fault evidence, excluded work and the proposed next scope |
| Escalate to another trade | Evidence showing the issue sits outside the aircon service scope |
- Decision
- Close the work order
- Evidence needed from the report
- Completed scope and a recorded result for the correct unit
- Decision
- Monitor a condition
- Evidence needed from the report
- Observed finding, current effect and a clear trigger for review
- Decision
- Approve a separate repair
- Evidence needed from the report
- Fault evidence, excluded work and the proposed next scope
- Decision
- Escalate to another trade
- Evidence needed from the report
- Evidence showing the issue sits outside the aircon service scope
Which six fields belong in the operational template?
Use six fields for every visit. Extra client fields can be added, but these six preserve the minimum operational chain from asset to next decision.
| Field | Useful detail | Decision it supports |
|---|---|---|
| 1. Asset and location | Site, floor or zone, room, unit identifier and system relationship where known | Confirms the right asset and prevents room-level findings from being merged |
| 2. Complaint and operating context | Reported symptom, timing, affected zones and conditions when it appears | Sets the pattern the visit needs to reproduce or test |
| 3. Scope performed | Cleaning, checks, access and repairs actually completed per unit | Shows what the work order covered and excluded |
| 4. Findings and evidence | Observed condition, test basis, photos or readings only when they were taken | Separates confirmed evidence from an assumption |
| 5. Result and status | Result after the work and whether the symptom was reproduced, cleared or still present | Supports close, monitor or further diagnosis |
| 6. Open action and owner | Outstanding issue, next test or scope, responsible party and decision trigger | Keeps an unresolved item from disappearing between visits |
- Field
- 1. Asset and location
- Useful detail
- Site, floor or zone, room, unit identifier and system relationship where known
- Decision it supports
- Confirms the right asset and prevents room-level findings from being merged
- Field
- 2. Complaint and operating context
- Useful detail
- Reported symptom, timing, affected zones and conditions when it appears
- Decision it supports
- Sets the pattern the visit needs to reproduce or test
- Field
- 3. Scope performed
- Useful detail
- Cleaning, checks, access and repairs actually completed per unit
- Decision it supports
- Shows what the work order covered and excluded
- Field
- 4. Findings and evidence
- Useful detail
- Observed condition, test basis, photos or readings only when they were taken
- Decision it supports
- Separates confirmed evidence from an assumption
- Field
- 5. Result and status
- Useful detail
- Result after the work and whether the symptom was reproduced, cleared or still present
- Decision it supports
- Supports close, monitor or further diagnosis
- Field
- 6. Open action and owner
- Useful detail
- Outstanding issue, next test or scope, responsible party and decision trigger
- Decision it supports
- Keeps an unresolved item from disappearing between visits
1. Asset and location
Name the site and the precise unit. Include the room or zone, indoor unit identifier and connected outdoor system when the relationship is known.
If the asset register and site label disagree, record both and flag the mismatch. Do not silently assign a finding to the nearest unit.
2. Complaint and operating context
Preserve what the occupant or operations team reported. Aircon stops after long use is a different test brief from a unit that will not start at all.
Record whether the pattern affects one room, a shared zone or the whole system. Office warm after partition is also useful context because a layout change can alter airflow without creating an equipment fault.
3. Scope performed
State what was cleaned, opened, tested or repaired. A tick beside serviced is weaker than a per-unit note showing which parts were accessible and which checks were outside the work order.
If access prevented a check, say so. An inaccessible condenser, ceiling void or control panel should not be recorded as inspected.
4. Findings and evidence
Record observed condition before recommendation. Return grille packed with lint is a finding; recommend gas top-up is not evidence for that finding.
Attach a reading only when the technician took it with a suitable method and the value helps the decision. Do not add a standard-looking number from another visit or infer a result that was not measured.
5. Result and status
State what happened after the completed scope. If the reported fault could not be reproduced, record that limit instead of marking the unit normal.
A mall shop cassette that drips late in the day may stay dry during a short visit. The status should then remain open to a load-related drainage check rather than closing on the absence of an immediate drip.
6. Open action and owner
Name the next operational step, who must decide it and what evidence should trigger action. This can be a follow-up test, separate repair quote, access arrangement or referral to another trade.
Avoid an invented maintenance date. Use the agreed contract cycle where it applies, or set a condition-based trigger that matches the recorded issue.
How should findings differ from recommendations?
Findings state what was observed or tested. Recommendations state what action may follow from that evidence. Keeping the two separate lets the facilities team challenge the scope without losing the original facts.
| Report line | Type | Why it matters |
|---|---|---|
| Outdoor terminal showed visible corrosion and an unstable connection during testing | Finding | Records the evidence behind an industrial aircon breaker trip investigation |
| Repair the affected connection under a separate approved scope | Recommendation | Makes clear that the repair was not completed during the inspection |
| The reported drip did not appear during the visit | Finding with limitation | Prevents a non-reproduced fault from being recorded as resolved |
| Repeat the drainage check under the conditions when the drip appears | Recommendation | Links the next step to the reported pattern |
- Report line
- Outdoor terminal showed visible corrosion and an unstable connection during testing
- Type
- Finding
- Why it matters
- Records the evidence behind an industrial aircon breaker trip investigation
- Report line
- Repair the affected connection under a separate approved scope
- Type
- Recommendation
- Why it matters
- Makes clear that the repair was not completed during the inspection
- Report line
- The reported drip did not appear during the visit
- Type
- Finding with limitation
- Why it matters
- Prevents a non-reproduced fault from being recorded as resolved
- Report line
- Repeat the drainage check under the conditions when the drip appears
- Type
- Recommendation
- Why it matters
- Links the next step to the reported pattern
What belongs in a fault report but not a routine service line?
A fault report needs a deeper chain from symptom to test and result. A routine service line can record condition and completed upkeep, but it should not invent a diagnosis when no fault investigation was requested or performed.
| Report element | Routine service | Fault visit |
|---|---|---|
| Asset and access | Required | Required |
| Completed cleaning scope | Required when performed | Record only if it formed part of the fault scope |
| Reported symptom pattern | Record if one is raised | Required |
| Diagnostic test and result | Only when performed | Required for a confirmed cause |
| Repair recommendation | Only when supported by a finding | Required when the fault remains open |
| Post-work result | Record the condition checked | Record whether the reported symptom changed |
- Report element
- Asset and access
- Routine service
- Required
- Fault visit
- Required
- Report element
- Completed cleaning scope
- Routine service
- Required when performed
- Fault visit
- Record only if it formed part of the fault scope
- Report element
- Reported symptom pattern
- Routine service
- Record if one is raised
- Fault visit
- Required
- Report element
- Diagnostic test and result
- Routine service
- Only when performed
- Fault visit
- Required for a confirmed cause
- Report element
- Repair recommendation
- Routine service
- Only when supported by a finding
- Fault visit
- Required when the fault remains open
- Report element
- Post-work result
- Routine service
- Record the condition checked
- Fault visit
- Record whether the reported symptom changed
What does this checklist not replace?
This checklist is only an operating aid for split, cassette and ducted units. It does not replace a form set by the client. It also does not replace a commissioning record, engineering paper, safety certificate or report from another trade.
It also does not extend the work completed. A report can identify an issue outside the agreed scope, but the written note does not mean that issue was tested, repaired or certified.
Facilities managers should keep the client's required fields and asset rules where those exist. The six fields here can sit beneath them as the operational evidence chain.
- Do not state a cause without a supporting test or observation.
- Do not copy readings from another unit or visit.
- Do not mark inaccessible areas as checked.
- Do not treat a recommendation as completed work.
- Do not use this template as proof that another reporting duty has been met.
Common questions
What should an aircon service report show for each unit?
How does a finding differ from a recommendation?
Can a fault report close a symptom that did not appear?
Does this template replace a client's reporting requirements?
Sources
- Guidelines for Energy Efficiency of Air-Conditioning Systems (ACMV)
National Environment Agency · Checked
ACMV system checks and maintenance practice.
Ready to get started?
Tell us what’s going on. Symptoms, setup, photos, anything we should know. We’ll assess and come back with the right next step.