How should an inspector describe a system that has been well maintained but is old?

Maintenance and age are independent facts and the report should keep them that way. Good maintenance genuinely improves the odds — a flushed water heater with a replaced anode, a furnace serviced annually, a roof kept clear — but it does not reset the clock on material fatigue, corrosion or the wear of moving parts. Reporting a well-kept twenty-year-old system as effectively new would give the client a false basis for deferring a reserve; reporting it as failed because of its age alone would ignore observable evidence and push them toward unnecessary replacement. Stating the age, describing the condition, and noting the maintenance evidence lets the client hold all three facts and decide. It also keeps the inspector inside their role, since maintenance history is inferred from what is visible rather than known.

The report states the component's age and notes the evidence of maintenance alongside it. Both facts are relevant and neither cancels the other, so presenting them together gives the client an accurate basis for planning.

Inspection reports describe observed condition and provide service-life context. Evidence of maintenance — service tags, clean equipment, replaced components — is an observation that informs the picture without altering the component's age.

Care Slows It, It Does Not Reverse It. Report the years and the upkeep side by side, and let the client hold both.

Note the evidence you relied on for maintenance — service stickers, a clean burner compartment, a recent anode. That makes the observation verifiable rather than an impression.

• •Letting maintenance evidence override the component's age
• •Declaring an operating system failed on age alone
• •Telling the client no further attention is needed