Field note
A useful service report separates what the customer said, what you observed, what you measured, what you proved, and what still remains uncertain.
Use a repeatable structure
- Complaint
- Symptoms/observations
- Measured readings
- Diagnostic steps and comparisons
- Confirmed root cause
- Repair or temporary action
- Final readings/outcome
- Follow-up required
- Safety notes and lesson learned
Record numbers with context
- Include units and whether the value is nameplate, measured, target, or comparison.
- For refrigerant work, record refrigerant type, pressures/temperatures, superheat/subcooling when appropriate, and ambient/load context.
- For electrical work, record voltage, phase current, capacitor values, and which device was commanded.
Separate confirmed from suspected
Use language such as 'confirmed leak at...' for proven defects and 'suspected control-board fault; further testing required' when the evidence is incomplete. This makes the case more useful and prevents a future technician from treating a guess as a fact.
Write for the next technician
Include what changed after each test. A good report should let someone else understand why you moved from airflow to refrigeration, from thermostat to BAS, or from pump status to flow-proving without repeating every step.
Safety / model checks
- Remove customer-identifying information before using a case for training/community content.
- Do not present a temporary workaround as a permanent repair.
Safety note
HVAC work can involve high voltage, rotating equipment, pressurized refrigerants, and combustion systems. Use this site as a reference only. Follow the equipment manual, applicable codes, PPE, lockout/tagout, and current refrigerant rules. Field cases and troubleshooting paths are case-specific and are not OEM procedures or universal targets.