Writing for Different Reading Levels
Why this matters
A written estimate, a text update, and an internal SOP are read by three different audiences with three different amounts of patience and background knowledge. Write all three the same way and one of them fails: the customer glazes over at a wall of jargon, or the new hire misreads a shorthand instruction and does the job wrong. Matching your writing to who is actually going to read it is not dumbing it down, it is doing your job as a communicator.
The three audiences you write for most
- Customers. No trade background, reading fast on a phone, often anxious about cost or timing. They need plain words, short sentences, and the bottom line up front.
- New or junior techs. Some background, but not your years of pattern recognition. They need explicit steps, no assumed shortcuts, and the "why" spelled out so they can adapt when the exact situation does not match the page.
- Experienced peers and vendors. Full trade vocabulary is fine and even expected. Over-explaining basics here wastes their time and can read as condescending.
The mistake most shops make is writing everything at the middle setting: too technical for the customer, too vague for the trainee, too padded for the peer.
Plain language for customers
Plain language is not simple or childish, it is efficient. It gets the point across on the first read, which matters when the reader is standing in a driveway or scrolling a text between meetings.
- Lead with the answer. "Your part is on back order, new estimate is Thursday" beats three sentences building up to that fact.
- Cut jargon or translate it inline. If you must use a technical term, define it in the same sentence: "the capacitor, a small part that helps the motor start, has failed."
- Prefer short sentences and common words. "The unit is not cooling because the outdoor fan motor stopped running" beats "the outdoor unit is experiencing a failure to cool due to non-operational condition of the fan motor assembly."
- Use numbers and dates, not vague time words. "By Thursday at noon" beats "soon" or "shortly."
A rough gut check: read it back and ask whether a smart friend outside the trade would understand it on one pass, with zero follow-up questions. If not, simplify.
Explicit language for training material
Training content fails in the opposite direction from customer writing: not because it is too technical, but because it assumes knowledge the reader does not yet have. A step written for someone who already knows how to do the job is useless to someone learning it.
- Spell out every step, including the ones that feel obvious to you. "Turn off power at the breaker" is not obvious to someone who has never worked a panel; "Turn off power at the breaker labeled for this circuit, and confirm with a voltage tester before touching anything" is.
- Name the why, not just the what. "Torque the fitting to spec, not just snug" teaches a principle the trainee can apply elsewhere. "Torque the fitting" alone teaches nothing beyond the one fitting.
- Anticipate the wrong turn. Good training material calls out the mistake a beginner is likely to make right at the step where it happens, not in a general warnings section nobody reads.
- Avoid shorthand and insider abbreviations until you have defined them once. A term your whole crew uses daily might be gibberish to someone two weeks in.
Full trade language for peers and vendors
When you are writing to another tech, a supplier, or an inspector, plain-language padding actually slows the reader down. Use the correct technical term, skip the definitions, and get to the point. A parts order, a permit note, or a technical email to a manufacturer's rep reads as more credible, not less, when it uses precise trade vocabulary correctly.
How to tell which mode you are in
Before writing anything longer than a one-line reply, ask:
- Who is the primary reader? Not who might see it eventually, who is it written for.
- What do they already know? Assume less than you think for customers and trainees, assume more for peers.
- What do they need to do or decide after reading this? Write toward that action, and cut anything that does not serve it.
References
- Plain Language Action and Information Network (PlainLanguage.gov), federal plain-language guidelines
- See related: Building a Documentation Habit the Crew Will Follow
- See related: The One-Sentence Summary Every Document Needs