Guides
Part of Repair diagnosis guide: define the fault before paying for parts
How to prepare a device for repair without losing data or evidence
Prepare a device for repair by recording its condition, backing up and verifying data, protecting accounts, removing extras, and defining service approval.
What to take away
- Photograph the device and record its identifiers before it leaves your possession.
- Make a backup, verify that it can be read, and decide how the repairer may handle storage.
- Remove cards, accessories, and account access only after checking the maker's service instructions.
- Describe the fault with exact reproduction steps and evidence.
- Get the diagnostic charge, spending limit, data terms, and repair warranty in writing.
A repair intake should preserve three things: the device, the data, and the facts about the fault. Preparation reduces misunderstandings, but it should not hide evidence or make an unsafe product operate longer than necessary. It also goes faster when the route was picked deliberately, and the phone repair routes comparison shows what each one asks of you.
1. Stop if the device is unsafe
Power down a device with battery swelling, smoke, a burning smell, liquid intrusion, exposed wiring, severe impact damage, or abnormal heat. Do not charge it simply to make a backup. Tell the repairer what you observed before transporting it, and ask for safe packing instructions if the battery may be damaged.
Do not clean away corrosion, residue, scorch marks, or impact evidence before assessment. A photograph is useful, but the physical evidence may help a technician establish what happened.
2. Record identity and condition
Write down the manufacturer, exact model, serial number, device identifier, storage size, color, and visible distinguishing marks. Photograph all sides in good light, including cracks, dents, ports, seals, and the screen. Capture the device powered on only if it is safe.
List every item being handed over. A laptop intake might say "computer only, no charger, no case." If a charger or accessory is part of the fault, label it and include its model or rating. Do not send unrelated accessories.
3. Capture the fault
Give the shop a short description that another person can follow:
- Starting state
- Exact action
- Observable result
- Expected result
- Frequency
- Conditions that change it
Attach photographs, videos, error codes, and dates. State whether a drop, spill, update, repair, new accessory, or power event came before the problem. Separate facts from guesses. "Fails to charge with two tested cables" is stronger than "charging port is bad." That discipline comes straight from the repair diagnosis method.
4. Back up and test the backup
Copy accessible files to a destination you control. Include documents, photos, messages, authentication recovery codes, application data, local email, browser data, and project files that are not already synchronized. Confirm that important files open from the backup. A progress message alone does not prove that a usable copy exists. The NCSC's guidance on backing up your data covers cloud and removable-media copies and gives restoring its own section, which is the right emphasis: a backup you have never restored from is untested.
Record any encryption recovery key needed to restore the system, but keep that record away from the device. If the device cannot start, decide whether data recovery comes before ordinary repair. Replacing or erasing storage may destroy the best remaining recovery path. A phone set up with a tested backup from day one makes this step routine instead of frightening.
5. Protect accounts and personal data
Follow the exact service instructions for the product. Makers commonly require anti-theft locks and find-my features to be switched off before they accept a device, and no legitimate intake needs your account password. Keep account security details to yourself, stay present if a credential must be entered for a software step, and expect the required sequence to differ by maker, model, service route, and whether the device responds.
Remove payment cards or passes when the platform's instructions call for it. Remove SIM and memory cards unless the reported fault requires one and the shop agrees to accept it. Sign out or use a dedicated repair mode when supported. If a passcode is necessary for testing, ask whether a temporary test account can provide enough access.
For a work-owned or managed product, contact the administrator before resetting, unenrolling, or disclosing credentials. For regulated or confidential data, use the organization's approved repair and data-destruction process.
6. Decide what not to erase
Do not erase a device blindly. Logs, settings, error messages, and the current state may help reproduce a fault. Balance that evidence against privacy and the service provider's stated process. The ICO's guidance on deleting data from devices is blunt about the other side of that balance: storage in a faulty device still holds personal data, and a device that will not switch on does not mean the data inside is out of reach.
Ask whether the shop will:
- access user files
- run tests under your account
- remove or replace storage
- reset or update software
- retain diagnostic data
- send the product to another facility
- return the original storage or failed part
Record the agreed answer. If privacy requirements cannot be met, choose another service route or arrange data recovery and secure erasure first.
7. Set commercial terms
Before transfer, record the diagnostic fee, initial estimate, maximum authorized amount, tax, delivery charge, likely turnaround, and storage or uncollected-device policy. State that extra work needs your written approval. Ask what happens if the fault cannot be reproduced or the repair does not solve it.
Define the replacement part's condition and the warranty on parts and labor. Ask whether old parts will be returned, recycled, or kept for a core credit. Get an intake receipt with the device identity, accessories, condition, stated problem, and agreed terms. The repair intake checklist lists every box that receipt should tick.
8. Check the return
Match the serial number and accessories at pickup. Inspect the case, screen, ports, screws, seals, and fit. Repeat the original fault test, then check charging, network, sound, cameras, controls, and other functions affected by the work. Review software version and storage before restoring data.
Save the invoice, part description, test result, and repair warranty. Note the date and any condition that the shop says remains unresolved.
Common questions
Should I give a technician my main password?
Avoid sharing account passwords. Ask for a repair mode, temporary local account, supervised entry, or a test that does not need access.
Is one cloud backup enough?
Only if the needed data is present, synchronized, and recoverable. Open representative files and confirm the account recovery method.
Should I include the charger?
Include it when charging or power is part of the fault and the shop requests it. Otherwise, list exactly what you leave.
What if the device will not turn on?
Do not keep forcing it to start. Record the last known behavior and discuss data recovery, diagnosis, and storage replacement before authorizing work.