Commercial RTU Service Reports With Controls Notes

The property manager does not need a page of shop talk about RTU-4.

They need to know what the rooftop unit was asked to do, what it actually did, what the technician measured, what safety or access limits affected the work, what needs approval next, and whether the invoice matches the visit.

"Checked unit. Working now." is not a commercial HVAC service report.

For small HVAC shops, a good RTU report is a bridge between the work request intake, HVAC work order, HVAC service report, HVAC inspection report, HVAC quote, change order, invoice, and completion sign-off. The report should be technical enough for the next technician and plain enough for the customer who approves the repair.

That does not mean every one-truck shop needs a controls engineer's narrative on every call. It means the service report should stop hiding the sequence problem behind vague language.

If the unit failed because the economizer stayed open, the report should say that. If the thermostat was in occupied mode but the building automation system commanded the fan off, say that. If the sensor reading looked wrong, say which sensor, what it read, and what you did or did not verify. If the roof access was unsafe, say why the work stopped.

Start with the unit, not the complaint

Commercial buildings often have more than one unit, more than one tenant, and more than one person calling.

The first line of the report should identify the asset:

Do this before the readings.

If the report says "unit on roof" and the property has eight rooftop units, the next visit starts by wasting time. If the HVAC work order named RTU-4 but the technician actually serviced RTU-5, the report should catch the mismatch before the invoice goes out.

For multi-unit sites, attach a roof sketch, asset photo, or unit tag photo. The site assessment checklist can carry the first asset map. The service report should keep it alive.

Name the operating mode at arrival

Controls notes start with one question:

What was the unit supposed to be doing when the technician arrived?

Record the mode before changing settings:

Example:

Arrival at 9:42 a.m. Unit tagged RTU-4. BAS occupied schedule active. Space sensor Suite 210 reading 78 degrees F with cooling setpoint 72 degrees F. Outdoor air 84 degrees F. Supply fan commanded on and running. Stage 1 compressor commanded on, not running. Economizer damper visible near minimum position. No active smoke alarm or fire shutdown indication observed at unit display. Diagnostic limited to approved no-cooling complaint.

That paragraph is better than three pages of screenshots nobody can interpret.

It also protects the shop. If the customer later says the unit "never ran," your report shows the unit condition at arrival and what command it was under.

Do not write "sequence checked" unless you say what sequence

The sequence of operation is the order and logic the unit should follow. On a simple RTU, that may be thermostat call, fan enable, safeties, economizer position, compressor stage, heating stage, and shutdown. On a larger commercial job, the sequence may come from a design document, controls contractor, building automation system, commissioning record, or manufacturer controls manual.

The service report should not invent the design sequence.

It should say what source the technician used:

That last sentence matters. A small HVAC shop should not be held responsible for a controls sequence it never received.

Use the statement of work scope attachment or HVAC proposal when the customer wants deeper controls verification. A service report can document what was observed. A controls audit is a different scope.

Controls and sensor notes belong in plain English

Commercial RTU calls often become arguments because the tech found a controls problem but the customer hears "the unit is fine."

Write controls findings as a chain:

1. What command was present?
2. What device reported the condition?
3. What did the unit do?
4. What reading or test supports that finding?
5. What remains unverified?

Use a compact table:

Notice the language: "possible," "recommend," "not approved this visit."

That is how the report stays honest. Do not make a sensor replacement sound certain if you did not test the sensor circuit. Do not sell a compressor if the call has not passed through fan, filter, coil, airflow, safeties, and controls checks.

Separate readings from recommendations

Readings are facts. Recommendations are judgment.

Keep them close, but do not blur them.

Then write the recommendation as a separate line:

Finding: Stage 1 compressor did not start under active cooling call. Contactor pulled in. Compressor did not draw running current. Capacitor tested below rated range. Recommendation: replace capacitor, restart unit, then recheck compressor operation and refrigerant readings. Customer approved capacitor replacement only. Compressor condition after restart to be documented in follow-up service report.

That is a service report a customer can approve from their phone.

It also keeps the invoice honest. The invoice should not say "compressor repair" if the approved work was "replace capacitor and retest."

Refrigerant records need their own discipline

EPA Section 608 is not a paperwork decoration.

EPA's Section 608 program covers stationary refrigeration and air-conditioning equipment and prohibits intentional venting of ozone-depleting refrigerants and their substitutes during maintenance, service, repair, or disposal. Leak-repair paperwork is more specific than that broad anti-venting rule.

Do not reduce every refrigerant note to one threshold. Under 40 CFR 82.157, the leak-repair rule applies to 50-pound-and-up appliances using class I or class II refrigerants, or blends containing them, and does not apply to appliances containing only substitute refrigerants. Under 40 CFR 84.106, the HFC management leak-repair rule applies from January 1, 2026, to covered 15-pound-and-up refrigerant-containing appliances when the refrigerant contains a regulated substance or a high-GWP substitute, with listed exclusions that include residential and light-commercial air-conditioning and heat-pump equipment.

A small package unit, a light-commercial RTU, a larger comfort-cooling appliance, and refrigeration equipment can sit in different buckets. The report should identify the refrigerant, full charge basis, appliance category if known, and what information was given to the owner or operator. Then the owner, compliance lead, or qualified professional can decide which rule applies.

Do not turn that into a vague note:

Added gas.

Write the useful record:

For covered equipment, the record burden can become much more serious. The service report should help the owner keep the information EPA expects, including appliance identity, location, date, service performed, technician, refrigerant amount and type, full charge, leak-rate context where applicable, leak inspection details, verification test results, and other applicable records.

Even when the unit is smaller, the habit is worth keeping. A customer who pays for a leak search wants to know what was checked. A warranty reviewer wants refrigerant and startup notes. The next tech wants to know whether "low charge" was measured, guessed, repaired, or only temporarily addressed.

Use the HVAC service report for the technical record, the HVAC quote for the approved repair path, and a change order when the customer expands the visit from diagnostic to repair.

Roof safety notes are part of the report, not office gossip

RTU work puts technicians around ladders, hatches, roof edges, weather, electrical gear, rotating parts, hot surfaces, refrigerant cylinders, and sometimes grease or tenant debris.

The service report is not a substitute for the job hazard analysis or safety inspection checklist. It should still record safety conditions that changed the work:

OSHA's ladder, fall-protection, and lockout rules are not blog-post checkboxes. They are reminders that a report should not imply a technician completed work that the site made unsafe.

If the site condition changes the price or schedule, use a schedule change notice, change order, or revised HVAC proposal. Do not bury the reason in a text thread.

The work-order safety briefing guide covers this workflow from the dispatch side. The service report closes the loop after the technician sees the actual roof.

Tier recommendations so the customer can act

Commercial customers need to route approvals.

Do not hand them a flat list of "recommended repairs" with no priority. A property manager may need to tell ownership which item is urgent, which item affects comfort, and which item is preventive maintenance.

Use clear tiers:

That structure helps the customer approve the next document:

• HVAC quote estimate for a priced repair;
• HVAC proposal for a broader maintenance or controls scope;
• HVAC bid when the work is competitive or property-managed;
• HVAC contract agreement when the job becomes a larger replacement or recurring service arrangement;
• general warranty when the repair or replacement needs coverage terms.

The customer should not have to reverse-engineer your approval request from the invoice.

Match the report to warranty and closeout

RTU service reports often become warranty evidence.

A compressor claim, control-board claim, heat-exchanger claim, or labor warranty argument may turn on boring details:

• model and serial number;
• install or startup date;
• service date;
• fault code;
• maintenance history;
• filter and coil condition;
• refrigerant type and charge notes;
• electrical readings;
• sensor or controls finding;
• who approved the repair;
• whether the unit was left running, locked out, or waiting on parts.

That is why the manufacturer warranty pass-through guide keeps pushing serial numbers, startup records, registration, maintenance duties, and service notes into the job file. The customer does not care whether the missing field was "office paperwork" or "field paperwork." They care that the claim is stuck.

For a replacement or major repair, the service report should feed the owner training walkthrough: filter sizes, thermostat instructions, maintenance interval, warranty registration, condensate notes, disconnect location, and service contact.

If the service report leads to an energy upgrade quote, the rebate paperwork guide for HVAC, solar, and EV work explains why model numbers, product specs, invoices, photos, permits, and completion records cannot wait until after installation.

A simple RTU report format

Use a predictable order. The customer should not have to hunt for the decision.

You can keep this to one page for a basic PM visit. The point is not length. The point is traceability.

Example: no-cooling call that does not overstate the repair

Here is a compact version a small shop could write:

RTU-4 west roof serving Suite 210. Tenant reports warm space after 1 p.m. Work order approved no-cooling diagnostic only. Arrival 9:42 a.m.; BAS occupied schedule active; Suite 210 sensor 78 degrees F, setpoint 72 degrees F; outdoor air 84 degrees F. Supply fan running. Stage 1 compressor commanded on but not running. Unit disconnect used for inspection; stored energy checked before contact. Roof dry; hatch access acceptable; edge-side panel not opened.

Found failed run capacitor for Stage 1 compressor. Customer approved capacitor replacement by phone at 10:18 a.m. Replaced capacitor and restarted unit. Compressor started, current draw within nameplate range during test. Return/supply readings after 12 minutes: 78 degrees F return, 59 degrees F supply. Refrigerant readings recorded after airflow confirmed; no refrigerant added. Economizer at minimum position during test. Outdoor air sensor on BAS read 66 degrees F while handheld roof reading was 84 degrees F; recommend controls contractor or return visit to verify outdoor air sensor and economizer logic if afternoon complaint continues.

Unit left running in cooling mode. Panels secured. Photos attached: unit tag, capacitor, disconnect, BAS screen, supply/return readings. Quote requested for economizer sensor verification and condenser coil cleaning. Invoice should bill approved diagnostic plus capacitor replacement only.

That report does three things at once:

1. It documents the repair that was actually approved.
2. It preserves the unresolved controls clue.
3. It gives the office the next quote without making the invoice do the explaining.

Sources

• U.S. EPA, Stationary Refrigeration and Air Conditioning, for Section 608 program context, refrigerant-management resources, certification resources, and EPA links for stationary air-conditioning and refrigeration equipment
• 40 CFR 82.157, Appliance maintenance and leak repair, for covered class I/class II appliance leak-rate thresholds, leak inspections, verification tests, retrofit or retirement plans, records, reports, and 50-pound-plus appliance recordkeeping fields
• 40 CFR 84.106, Leak repair, for the HFC management leak-repair framework effective January 1, 2026, including covered 15-pound-and-up applicability, listed exclusions, leak-rate thresholds, service records, full-charge records, inspections, verification tests, and retrofit or retirement plans
• OSHA 29 CFR 1910.23, Ladders, for ladder inspection, condition, use, stabilization, and access requirements relevant to commercial rooftop service
• OSHA 29 CFR 1910.28, Duty to have fall protection and falling object protection, for general-industry walking-working-surface fall-protection duties, including unprotected sides and edges
• OSHA 29 CFR 1910.147, The control of hazardous energy, for lockout/tagout scope, application, and energy-control program context during servicing and maintenance
• ASHRAE, Standards and Guidelines, for the current ASHRAE standards and guidelines index, preview access, addenda, errata, and interpretations workflow
• ICC Digital Codes, 2021 International Energy Conservation Code, Section C408 Maintenance Information and System Commissioning, for examples of commercial energy-code commissioning, operating, and maintenance information expectations
• IRS Publication 583, Starting a Business and Keeping Records, for business recordkeeping context around supporting documents such as invoices, receipts, and paid bills
• 15 U.S.C. 7001, Electronic Signatures in Global and National Commerce Act, for federal electronic-signature and electronic-record validity and retention context

---

Verify refrigerant rules, roof safety, lockout duties, code requirements, controls responsibility, warranty terms, licensing, electronic records, and record retention with the AHJ, EPA guidance, OSHA guidance, building owner, engineer, controls contractor, manufacturer, state licensing board, safety professional, insurer, attorney, or CPA before acting.