The Bullet Point vs Paragraph Decision in a Report

Why this matters

A service report that is all paragraphs makes the customer hunt for the one line that matters, buried in a wall of prose. A service report that is all bullets can strip out the reasoning that makes the diagnosis credible, leaving a list of fragments that reads as a checklist rather than an explanation. Both failure modes cost you the same thing: a customer who does not fully understand what happened, and either questions the invoice or calls back with questions you already answered in the report they did not read closely. Knowing when to switch formats inside a single document is a skill most techs never get taught, and it is the difference between a report that gets skimmed and understood and one that gets skimmed and ignored.

The core rule

Bullets for lists of discrete, parallel items. Paragraphs for reasoning, sequence, and cause-and-effect. If you are naming things (parts checked, readings taken, options available), bullet them. If you are explaining why something happened or what it means, write it as a sentence or two of prose. Most reports need both, switching formats section by section, not committing to one format for the whole document.

When to use bullets

• Listing what was inspected or tested. "Checked: capacitor, contactor, blower motor, condensate line" is genuinely a list, force it into a paragraph and you get a run-on sentence nobody enjoys reading.
• Presenting options with a decision to make. Repair options, pricing tiers, or a menu of next steps read faster and compare more easily as bullets or a short table.
• Naming multiple findings that do not depend on each other. If finding B does not follow from finding A, they are parallel items and belong in a list, not a narrative.
• Any information the customer needs to scan back to later. Bullets are easier to relocate on a second read than a sentence buried mid-paragraph.

When to use a paragraph

• Explaining the "why" behind a finding. "The capacitor tested weak, which explains the hard-start noise you reported" is a cause-and-effect statement. Splitting it into two disconnected bullets ("Capacitor: weak" and "Noise: hard start") loses the connection between them, which is the actual information the customer needs.
• Describing a sequence of events. "We arrived, found the breaker tripped, reset it, and it held for the remainder of the visit" is a short story with an order. Bulleting each step strips out the flow and makes a five-second read take fifteen.
• Setting context or a recommendation with reasoning attached. "We recommend replacing the unit rather than repairing it, since the parts cost alone approaches half of a new unit's price and the compressor is past its typical service life" needs to stay as connected reasoning, not two orphaned bullets that lose the "since."

The tell that you picked the wrong format

If you find yourself writing a bulleted list where every item starts with "and this means" or "which caused," that is a sign the items are not actually parallel, they are a chain of cause and effect, and belong in a paragraph instead. If you find yourself writing a paragraph that is really just three unrelated facts strung together with commas and "additionally," that is a sign it should be three bullets instead. Read your own draft back and ask: is each item independent, or does understanding item two require item one? Independent items are bullets. Dependent items are prose.

A worked comparison

Weak, wrong format for the content: "We checked the water heater and found the anode rod was fully corroded and the pressure relief valve was not seating properly and the thermostat was reading five degrees high and we recommend replacing the anode rod now and monitoring the valve and recalibrating the thermostat while we're here since these are unrelated issues that are each simple fixes."

Strong, matched to the content:

Findings:

• Anode rod: fully corroded, needs replacement
• Pressure relief valve: not seating properly
• Thermostat: reading five degrees high

These are three independent issues, unrelated to each other, and each is a simple fix we can handle today while we're on-site.

The second version separates the parallel findings (bullets) from the reasoning that ties them together and drives the recommendation (a short paragraph after). Neither format alone would have worked as well.

The one-report rule of thumb

If a section of your report answers "what," bullet it. If a section answers "why" or "what happened, in order," write it as a sentence or two. A report that switches deliberately between the two, instead of defaulting to one for the whole document, reads faster and gets remembered more accurately, because the format itself is doing part of the explaining.

References

• Plain Language Action and Information Network (PlainLanguage.gov), formatting for scannability
• See related: The Checklist Format vs Narrative Format Decision
• See related: The Jargon You Should Never Put in Writing