Everyday technology

Prepare a clear device problem report before asking for help

Collect the symptom, relevant device details, and what you already tried. A short, organized report helps support understand the problem without asking you to repeat the same background.

By Repair Robin · Updated 2026-09-22 · About 10 minutes hands-on

What you’ll need

• Paper or a notes app
• The affected device, only if it is safe to use
• Optional: a screenshot or photo with personal information removed

Before you start

This is information gathering, not a repair or reset. Do not open the device, erase data, disable security features, install remote-control software, or share passwords as part of this checklist.

If there is smoke, swelling, unusual heat, exposed wiring, or liquid damage, stop routine troubleshooting and get appropriate help. Do not repeatedly power up a damaged device to produce a better report.

Step by step

1. Write the goal and the actual result

   Use two sentences: 'I was trying to…' and 'Instead, the device…'. For example: 'I was trying to print a one-page document. The printer displayed an error and no page came out.' Describe the observation before suggesting a cause.

2. Add the device and software context

   Record the make, model, and the app or operating-system version if readily available in its normal information screen. Include the relevant accessory. Keep full serial numbers, account identifiers, and receipts private until a verified support provider actually needs them.

3. Record when and how it happens

   Note when you first noticed the issue and whether it happens every time or only sometimes. List the few actions immediately before it occurs. If a recent update or accessory change preceded the problem, record that as timing information, not proof of the cause.

4. Save the exact message safely

   Copy an error code and the short message that accompanies it. If a screenshot is useful, inspect the entire image before sharing: crop out unrelated windows and remove names, email addresses, account numbers, passwords, and private documents. Text is enough when an image would expose too much.

5. List attempts and their outcomes

   Write what you already tried, one action per line, with its result. 'Restarted; the same message returned' is more useful than 'tried everything.' Do not repeat a risky or destructive step for completeness. State clearly if you have not tried anything yet.

6. Choose the next contact and prepare for it

   Use the manufacturer's known support site or a provider you have independently verified. Before handing over a device for service, check its specific preparation instructions and backup status. If a backup cannot be completed, say so before authorizing work; do not assume your information can be recovered.

If it’s not working

The problem does not happen during the appointment

Give the provider your timing notes and the saved error message. Describe the circumstances you observed rather than inventing a repeatable sequence.

A pop-up insists you call support immediately

Do not use the number in the warning. Navigate independently to the manufacturer's support site. Unexpected calls, urgent payment demands, and requests for remote access are reasons to stop and verify the contact.

You cannot find the model or version

Say 'unknown' and provide the product name or a photo of its non-sensitive label. Do not disassemble a device to locate information.

Check your result

• Your note includes the goal, actual symptom, device, timing, and previous attempts.
• Attachments do not reveal private information.
• You know which trusted support channel you will use.

Where this guide stops

• This checklist cannot diagnose a fault or guarantee a repair.
• For work or school devices, follow your organization's support and data-handling rules.