Why liquid damage is the riskiest job to accept
Corrosion is progressive. A board that boots today can be dead in a week, and the customer will believe you killed it. Hidden damage is invisible at intake. The visible corrosion you see when you open the machine is rarely the full extent.
The result: liquid damage produces more disputes per job than any other repair type. Not because techs do bad work, but because expectations were never set correctly at the start.
The framework below exists to protect you and inform the customer. In that order.
Phase 1: before opening
Get the story. When did it happen, what liquid, how much, and what did the customer do afterwards. Each answer changes the assessment.
Fresh water yesterday is a different job from coffee three weeks ago. A machine that was powered off immediately has a real chance. A machine that was put in rice and used for two weeks does not.
Check the device's external state. Liquid residue in ports, corrosion on connector pins, staining around seams. Photograph everything before opening a single screw.
Set the expectation now, before the diagnostic: liquid damage assessments are an evaluation, never a guarantee. The customer needs to hear this sentence at intake, not after.
Phase 2: internal inspection
Open the machine and photograph the board before touching anything. The liquid contact indicators tell part of the story. The corrosion pattern tells the rest.
Map what you see. Which areas were hit, which connectors show corrosion, whether liquid reached the keyboard backlight, the trackpad cable, the battery connector. Note what's clean.
Distinguish active corrosion from residue. Green or white fuzzy growth means the process is ongoing and the board needs cleaning before any assessment of what survived. Dried staining without growth means the event is older and the damage is what it is.
Test only after cleaning. A board with active corrosion will give you false results, and any conclusion drawn before ultrasonic or manual cleaning is provisional.
Phase 3: the decision
After cleaning and testing, the job lands in one of four buckets: full repair is viable, partial function is recoverable, data recovery only, or total loss.
Be honest about which bucket the machine is in. The most expensive mistake in liquid damage work is selling a repair on a board that will fail again in a month. The second most expensive is the time sink: hours of rework on a board that should have been declared unviable at hour one.
What to document and photograph
Every liquid damage job should produce a record that protects you if the situation escalates.
Photograph the external state at intake, the board before cleaning, the board after cleaning, and any component-level damage you find. Date everything.
Write down the customer's account of the incident in their words. If they told you it was "a small splash two days ago" and the board shows weeks-old coffee corrosion, that discrepancy matters later.
Record what worked and what didn't at each stage. A machine that arrived dead and left dead with a declined quote is a very different liability from a machine that arrived "working except the keyboard."
Using AI to write the assessment report
The assessment report is where most techs lose the customer. The findings are technical, the customer is stressed, and the message is usually bad news.
Give AI your raw findings and let it structure the communication:
Write a liquid damage assessment report for a customer. Device: [model]. Incident: [what the customer reported]. Findings: [corrosion locations, affected components, what works and what doesn't]. Recommendation: [repair viable / partial / data recovery only / total loss]. Cost if applicable: [amount]. Include: a clear statement that liquid damage can progress over time, that this assessment reflects the device's current state, and that no liquid damage repair carries a standard warranty. Tone: professional, factual, empathetic. Under 200 words.
The output gives the customer a clear picture and gives you a written record of what was communicated. Both matter.
When to refuse the job
Some liquid damage jobs should not be accepted. Salt water immersion with days of delay. Boards with prior repair attempts and missing components. Customers who refuse the assessment fee but want a guaranteed outcome.
Refusing is a valid professional decision. The sentence is simple: "Based on the condition, I don't think repair is in your best interest. Let's talk about data recovery instead."
You lose one job. You avoid the dispute, the rework, and the review that follows a failed liquid damage repair.
Want the complete toolkit?
The Apple Repair Lab Toolkit — v1.0 includes 5 ready-to-use tools: AI diagnostic prompts, a repair estimate template, 6 customer email templates, a SOP template and a weekly KPI tracker. Everything an independent technician needs to run a more consistent lab.
Want the full prompt pack?
There are four more AI techniques in the free guide — diagnosing faster, writing better estimates, handling difficult customer conversations and building your own SOPs.
AI on the Bench — 5 ways to use AI in your Apple repair workflow.
BenchNotes publishes practical tools and guides for Apple technicians every week. Subscribe free to get them in your inbox.