Repair history is most valuable when a problem happens twice

The first repair feels like an isolated event. The second time, history matters. Was the symptom the same? Did the same part fail? Was the previous repair temporary? Which company handled it? Was follow-up recommended?

Record the problem in the user’s language

You do not need to diagnose equipment. Write what you observed: “water under front edge,” “intermittent grinding sound,” “screen went dark after 10 minutes.” The technician’s diagnosis can be recorded separately if provided.

Capture the outcome

A repair record should say whether the issue was resolved, monitored or scheduled for later work. If a replacement becomes likely, create a planning task rather than letting the repair note become the end of the story.

Attach the repair to the asset

A home-wide chronological list is useful, but asset history is where patterns become visible. The washing machine page should show its purchases, repairs and maintenance together.

Costs are optional but informative

Tracking repair cost can help with later replace-versus-repair decisions, but the app should not make that decision automatically without context.

Contextual CTA: Add the most recent repair to the asset it affected and include one sentence describing the original symptom. That small habit creates surprisingly useful history.

Found an error or an outdated instruction? Send us the page URL and a reliable supporting source.