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 | Reviewed by Lead Technician 25 Jul 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 |
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 |
|---|---|---|
| Field1. Asset and location | Useful detailSite, floor or zone, room, unit identifier and system relationship where known | Decision it supportsConfirms the right asset and prevents room-level findings from being merged |
| Field2. Complaint and operating context | Useful detailReported symptom, timing, affected zones and conditions when it appears | Decision it supportsSets the pattern the visit needs to reproduce or test |
| Field3. Scope performed | Useful detailCleaning, checks, access and repairs actually completed per unit | Decision it supportsShows what the work order covered and excluded |
| Field4. Findings and evidence | Useful detailObserved condition, test basis, photos or readings only when they were taken | Decision it supportsSeparates confirmed evidence from an assumption |
| Field5. Result and status | Useful detailResult after the work and whether the symptom was reproduced, cleared or still present | Decision it supportsSupports close, monitor or further diagnosis |
| Field6. Open action and owner | Useful detailOutstanding issue, next test or scope, responsible party and decision trigger | Decision it supportsKeeps 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 |
|---|---|---|
| Report lineOutdoor terminal showed visible corrosion and an unstable connection during testing | TypeFinding | Why it mattersRecords the evidence behind an industrial aircon breaker trip investigation |
| Report lineRepair the affected connection under a separate approved scope | TypeRecommendation | Why it mattersMakes clear that the repair was not completed during the inspection |
| Report lineThe reported drip did not appear during the visit | TypeFinding with limitation | Why it mattersPrevents a non-reproduced fault from being recorded as resolved |
| Report lineRepeat the drainage check under the conditions when the drip appears | TypeRecommendation | Why it mattersLinks 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 |
|---|---|---|
| Report elementAsset and access | Routine serviceRequired | Fault visitRequired |
| Report elementCompleted cleaning scope | Routine serviceRequired when performed | Fault visitRecord only if it formed part of the fault scope |
| Report elementReported symptom pattern | Routine serviceRecord if one is raised | Fault visitRequired |
| Report elementDiagnostic test and result | Routine serviceOnly when performed | Fault visitRequired for a confirmed cause |
| Report elementRepair recommendation | Routine serviceOnly when supported by a finding | Fault visitRequired when the fault remains open |
| Report elementPost-work result | Routine serviceRecord the condition checked | Fault visitRecord 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.
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.