How to Document Screen Damage Before Repair or a Claim

Stop first if handling the device may be unsafe

Evidence matters, but safety comes first. Stop normal troubleshooting if the device is wet, was recently exposed to liquid, smells unusual, gives off smoke, feels unusually hot, looks swollen or deformed, or has a screen or back cover lifting away from the body.

Do not keep charging, pressing, bending, prying, or trying to force the case or display back together. If liquid exposure is part of the story, follow screen water-damage guidance before collecting more photos or running screen tests.

If the device is dry, stable, and readable, collect the record before the pattern changes. If the display is cutting out, worsening quickly, or hard to control, backup and access may be more urgent than perfect photos.

Build the basic evidence packet

Start with the information most support, repair, return, warranty, insurance, school, and workplace processes tend to ask for. The exact upload form may differ, so treat this as a clean preparation packet and follow the provider instructions when they are more specific.

Device identity

• Device type, brand, exact model, color, storage size, and configuration when relevant.
• Serial number, IMEI, service tag, or school/work asset tag. Keep these private unless you are submitting them through a trusted provider form.
• Accessories connected to the problem, such as a case, keyboard cover, dock, charger, stylus, external cable, screen protector, or shipping packaging.

Purchase, assignment, or plan record

• Proof of purchase when available: receipt, invoice, order confirmation, delivery date, retailer or seller, or school/work assignment record.
• Warranty, protection-plan, insurance, trade-in, return-window, claim, or service-request information.
• Any provider case number, claim number, repair ticket, return authorization, tracking number, or intake receipt.

Symptom record

• What is visible, where it appears, whether it is constant or intermittent, and whether it affects touch, readability, brightness, or device control.
• Whether the outer glass, frame, hinge, back cover, corners, ports, or camera area show visible damage.
• Whether the issue appears during startup, on a plain background, in a screenshot viewed elsewhere, or on an external display when that comparison is safe and relevant.

Timeline

• Date and approximate time first noticed.
• What the device was doing immediately beforehand.
• Any known drop, pressure, shipping event, repair, liquid exposure, heat exposure, cleaning, accessory change, or no known incident.
• Whether the symptom changed and what you already tried.

Photograph the screen so the problem is understandable

Take at least one photo that shows the whole device and the screen in context. Then take closer photos only after there is enough surrounding screen and frame visible to make the close-up meaningful.

• Use normal room lighting for most screen-damage photos. Avoid direct flash, mirror-like reflections, and dark-room photos unless the symptom only appears in that condition.
• Tap to focus on the display and adjust exposure so bright areas are not blown out. Retake blurry, tilted, or reflection-heavy images.
• Photograph the screen powered on when the symptom is visible in normal use. Photograph it powered off when surface cracks, glass scratches, frame separation, swelling, or shipping damage matter.
• For a fixed spot, line, discoloration, or uneven patch, compare the same area on a few plain backgrounds. The Screen Color Test can provide simple white, black, red, green, and blue screens for observation. It does not prove the cause or repair the display.
• Inspect the photos on another device before relying on them. A damaged display can make a good photo look damaged when viewed on the same screen.

Match the evidence to the symptom

Different screen problems need different proof. A still photo can document a fixed mark, but it can miss symptoms that happen over time or during touch.

Screenshots and recordings need another display

A screenshot records the digital image the device is generating. It does not photograph cracked glass, pressure marks, panel bruises, backlight bleed, or anything physically wrong with the screen surface or display hardware.

1. Capture the screenshot or short screen recording while the symptom is visible.
2. Send or open the file on a separate display you trust.
3. Inspect the file there, not only on the damaged screen.

If the problem appears in the file on another display, captured content, app behavior, rendering, source-device, or graphics-output issues become more likely. If the file looks clean elsewhere while the original display still shows the problem, the evidence points more toward the original screen, surface, or hardware behind that screen.

Write the issue summary in facts, not guesses

A useful summary separates what you saw from what you think may have caused it. That matters because warranty, insurance, repair, and IT reviews often depend on provider inspection and policy language.

Fill in only what you know:

• Device:
• Serial number, IMEI, service tag, or asset tag:
• Purchase date, seller, or assigned organization:
• Issue first noticed:
• What is visible and where it appears:
• Constant or intermittent:
• What happened beforehand, if known:
• What has changed since first noticed:
• Photos, videos, screenshots, or test results saved:
• Backup status and access concerns:
• Support, claim, return, or repair number:

Avoid naming an internal component unless a qualified repair report has already identified it. “A green line is visible during startup” is stronger than “the internal cable failed.”

Before repair, shipping, return, or IT handoff

Once the basic evidence is saved, prepare for the handoff itself. Providers may inspect the device, erase it, replace it, or reject extra accessories that were not requested.

• Back up data when the device is stable enough to do so safely. If a phone display is becoming unreadable or touch control is failing, the broken-display backup page may help before access is lost.
• Follow the provider instructions for Find My, account locks, repair mode, passwords, SIM cards, memory cards, cases, covers, chargers, and accessories. Do not erase or modify a school or workplace device unless the organization tells you to.
• Photograph the full front, back, edges, corners, ports, and accessories immediately before handoff or shipping. Record which accessories were included.
• Make sure the serial number or service tag on the intake record matches the device. Keep the intake receipt, claim number, shipping receipt, tracking number, and delivery confirmation.
• Photograph packaging if the device arrived damaged, may have been damaged in transit, or is being returned in a shipping box.

For a stable laptop with an unreliable built-in display, an external monitor can preserve access while you collect records and back up files. The external-monitor workflow covers that setup.

What changes by review type

The same evidence packet can be reused, but each review type emphasizes different facts. Do not rewrite the story to fit a preferred outcome; make the record clear and let the provider decide the category.

Manufacturer warranty

Focus on the exact device, proof of purchase when requested, the visible symptom, when it began, any diagnostic behavior, and the presence or absence of visible physical or liquid damage. The manufacturer decides eligibility.

Retailer return

Focus on order date, delivery date, return deadline, condition on arrival, first-use evidence, packaging, and written communication with the seller.

Protection plan or device insurance

Focus on the device and plan, incident date, factual description of what happened, requested documents, deductible or service fee, claim number, and shipping or repair option selected by the provider.

Repair dispute

Focus on before-service condition photos, original complaint, intake ticket, accessories included, written estimate or quote, post-service condition, and messages with the shop or provider.

School or workplace device

Focus on asset tag, assigned user, IT ticket, incident deadline, organization instructions, and anything the organization says not to erase, repair, or ship independently.

What the evidence can and cannot prove

A well-kept record can show the visible condition at a point in time, whether the symptom was constant or intermittent, whether the outside of the device looked damaged, which files were attached, and what was handed over or shipped.

It usually cannot prove the exact internal cause, the failed component, who caused the damage, whether a defect is covered, whether an insurance claim must be approved, or whether repair is worth the cost.

If the provider confirms repair is needed and you are deciding whether to approve it, compare the quote, coverage, age of the device, and replacement cost on the repair-versus-replacement guide.

If the main question is what a particular pattern means, document it first, then read the specific symptom page: dark spots, lines after pressure, ghost touch after damage, or touch dead zones.