Explain a code section to a homeowner who's pushing back

Explain [CODE SECTION — e.g. "NEC 210.8(A)(7)" or "IPC 605.4" or "IBC 1011.5.2"] in plain English to a homeowner who's pushing back on having to do the work. Customer's pushback (in their words, if you have it): [WHAT THEY SAID — e.g. "the old one worked fine, why do I have to upgrade?"] Format the answer in exactly three short sentences: 1. **What the rule says** — one sentence, no code numbers, no jargon. 2. **Why it exists** — one sentence about the problem the rule was written to prevent. Reference an actual hazard if you can. 3. **What we have to do on this job** — one sentence, action-oriented. Voice: friendly contractor, not a lawyer. Don't lecture. Don't use words like "shall" or "compliant." Don't mention how much it costs — that's a separate conversation. Output: just the three sentences. No header, no preamble.

What this is for

You know the code. The customer doesn’t. The fight starts when you can’t explain why a rule exists in language they understand — and they assume you’re upselling them. This prompt gives you a clean three-sentence answer you can say out loud, on the spot, without sounding defensive.

How to use it

Open the AI app on your phone before you go in for the conversation.
Type or paste the code section. Add the customer’s actual pushback if you remember it — that makes the answer hit harder.
Read the three sentences out loud once before you walk in. Adjust one word so it sounds like you.
Deliver it like you’ve been saying it for years.

Pro move

Build a library: the 10 code sections you cite most often (GFCI requirements, panel clearances, water-heater pans, stair geometry, smoke alarm placement, etc.). Pre-generate the three-sentence answer for each, save them in a notes app. When the customer pushes back, you read off your phone in 5 seconds — not flipping through a code book in front of them.

What this is for

How to use it

Pro move

Send it in — we'll publish improvements.