What should I document when a repaired product is returned with the original issue still present?
Quick answer
Record the product’s identifying details, the repair dates and paperwork, and a neutral description of the original issue as it appears now. Keep copies of relevant documents, retain originals, and note your communications with the provider. The FTC recommends explaining what happened and sharing relevant repair records when a repair did not fix a problem; it does not prescribe product-specific tests. Follow the provider’s current process and official product instructions. [S1]
The question, the details, the next step.
A product came back from repair, but the issue I sent it in for is still there. What should I write down before I contact the service provider?
Make a brief record that separates known details from what you observe now. Include:
- Product identification, such as the brand, model, and serial number if available.
- When you first contacted the provider, when you sent or handed over the product, and when it was returned.
- The original symptom in your own words, the repair or service described in the paperwork, and any work the provider said it performed.
- What you can currently observe about the issue, when you noticed it, and the conditions in which it appeared, if those are already known.
Keep copies of the repair order, service report, receipts, and relevant messages. Retain original documents and make notes of conversations. The FTC recommends describing what happened and providing copies of relevant records for a repair that did not fix the problem. [S1] This general record does not establish why the issue remains or what remedy the provider must offer.
How do I describe the issue without guessing at the cause or doing extra tests?
Stick to what you directly noticed and what the paperwork says. Avoid diagnosing the product, claiming the repair was done incorrectly, or adding tests that are not part of the product’s official instructions. If the issue is intermittent or you cannot confirm it at the moment, say that plainly rather than presenting it as certain.
For example, assuming these details match your situation: “Before service, the product [brief description of issue]. The service report dated [date] says [relevant wording]. Since it was returned on [date], I observed [same issue or specific difference] on [date or occasion]. I have not determined the cause.” Replace every bracketed field with accurate information or remove it. Do not include details you did not observe.
What should the actual message to the provider look like?
Use the provider’s current follow-up process, and keep your message short enough to scan. For example:
Subject: Follow-up on repaired [product/model] — [service reference]
Hello,
I’m following up about [product/model], returned to me on [date] after service under reference [number, if available]. The original issue I reported was [brief factual description]. Since the product was returned, I have observed [what you can currently observe, and when].
The service paperwork dated [date] states [relevant description, or “I have attached a copy of the service report”]. I’ve attached copies of [relevant records]. Could you please let me know the next step under your current follow-up process?
Thank you, [name or preferred sign-off]
Attach copies rather than sending irreplaceable originals. Keep a copy of the message and note when you sent it. The FTC advises keeping notes of communications as part of working through a business problem. [S1]
What if the report is vague, or the issue is not happening every time? How do I keep the record useful?
Quote or summarize the report carefully; if its wording is unclear, identify the part you do not understand and ask the provider to explain it. Do not fill gaps with assumptions. For an intermittent issue, record only occasions you actually observe: the date, what happened, and any relevant circumstances you already know. You can say, “I have observed this on [occasion or date], but not consistently.”
A reusable follow-up note can be as simple as:
- Product and service reference: [details]
- Original reported issue: [description]
- Service dates and report wording: [dates; wording]
- Current observation: [what happened; when]
- Records attached: [list]
- Message or conversation log: [date; channel; person or team if known; summary; next step stated]
Ask the provider what it needs next, rather than assuming a particular inspection, retest, deadline, or resolution applies. The cited FTC guidance supports clear descriptions, relevant repair records, and communication notes; it does not set product-specific testing steps or determine the outcome of an individual case. [S1]
A practical checklist
Write down product details and the service reference, if available.
Record the original issue, repair dates, return date, and relevant service-report wording.
Describe only what you currently observe; label uncertainty or intermittent behavior.
Attach copies of relevant records and keep the originals.
Use the provider’s current follow-up process and save your message and communication notes.
A few more useful answers
Should I send the original repair paperwork?
Keep original documents and provide copies of relevant records. The FTC recommends providing copies and keeping originals. [S1]
Should I run additional tests to prove the issue is still present?
Do not add tests beyond the product’s official instructions. Describe observations you already have and ask the provider what it needs next.
Does this record guarantee a particular repair or refund?
No. It helps present the facts and relevant records, but it does not establish the cause of the issue or guarantee a particular outcome.
Sources
References used for this guide.
- [S1] FTC Consumer Advice: Solving Problems With a Business consumer.ftc.gov · Checked