A customer hands you a dead iPhone. Or a MacBook that won't power on. No physical damage, no liquid history mentioned, but the board-level fault is obvious within the first two minutes of testing.
Now you have a decision to make, and most independent techs make it badly.
Some say yes to everything, because turning away revenue feels wrong. Some say no to everything, because board-level work feels risky. Both instincts are wrong for the same reason: neither one is actually a decision. They're defaults.
Why "yes to everything" fails
Chasing every board-level job sounds like more revenue. In practice it's the opposite.
A job that should take 90 minutes turns into a 6-hour rabbit hole once you're two components deep and the fault moves. You've now got a customer waiting, a bench slot occupied, and a repair that isn't generating enough per hour to justify the seat. Multiply that by three or four jobs a month and board-level work quietly becomes your least profitable category, even though it looks impressive on the bench.
There's also the comeback risk. A board repair that "works" for two weeks and then fails again costs you the labour twice and the trust once.
Why "no to everything" fails too
Refusing all board-level work protects you from the risk above. It also hands the job, and the customer relationship, straight to a competitor or a mail-in specialist.
Most board-level faults aren't actually difficult. A shorted charging IC, a corroded connector, a blown fuse on a known line: these are bread-and-butter fixes for anyone with a hot air station and the right schematic. Treating every board job as too risky means turning away the easy 60% along with the genuinely hard 40%.
The fix isn't an attitude. It's a filter.
The 5-minute framework
Before you commit to a board-level job, answer four questions. Out loud, on paper, or in your head, but answer all four before you touch a soldering iron.
1. What's the fault, specifically?
Not "it doesn't turn on." The actual fault: no charging current draw, shorted rail, corrosion visible under the board, data corruption after liquid exposure. If you can't name the fault within a few minutes of diagnostics, that's information too.
2. What's the component cost versus what you'd charge?
A €15 IC on a job you'd quote at €180 is a good ratio. A board that needs three unknown components and a donor board for testing is a different ratio entirely, even before you count your time.
3. What's your realistic time estimate, and what's your hourly rate on it?
Not the optimistic estimate. The one based on the last time you did this exact repair. If your realistic estimate puts you under minimum wage for the slot, the job needs to be re-quoted, outsourced, or declined.
4. What's your track record with this specific fault?
Not board-level work in general. This fault, on this chip, on this generation of device. A charging IC swap you've done twenty times carries a different risk profile than a fault you've seen once.
Turning the answers into a decision
Accept when the fault is identified, the component cost is low relative to the quote, your time estimate is realistic and profitable, and you've fixed this exact issue before with a good success rate.
Outsource when the fault is identified but requires equipment or experience you don't have yet. Send it to a trusted micro-soldering specialist, mark up the service, and keep the customer relationship. You lose the labour margin on this one job. You keep the account.
Decline when the fault is vague, the component cost or time estimate is unclear, or your track record with this specific fault is thin. Declining isn't a failure. Quoting a job you can't estimate accurately is the actual failure, and it shows up three hours later.
Using AI to build the checklist
You don't need to memorise these four questions every time a board-level job walks in. Turn them into a printed checklist you fill in at intake, before you agree to anything.
I run an independent Apple repair lab and take in board-level repairs (logic board, charging IC, liquid damage). Build me a one-page intake checklist with four sections: fault identified (yes/no, description), component cost vs quoted price, realistic time estimate at my hourly rate, and past success rate with this specific fault. End with a clear accept / outsource / decline recommendation based on the answers. Format for printing, one page, fillable by hand in under 5 minutes.
Print a stack of these. Fill one in before every board-level quote. The goal isn't to say yes less. It's to stop saying yes on instinct and start saying it on data.
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, including 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.