Rather than being “bare bones” or “just the data,” the most effective technical reports are actually heavy on framing and transitional language. That is because technical reports are not usually intended to be read straight through. Instead, information in each section should be as “stand-alone” as possible, so that readers can easily identify the information they need and also locate an explanation of its purpose. Abstracts, introductions, and conclusions all provide information about the structure and purpose of the document so that it’s clear to readers how everything is laid out and logically organized.

Not only should engineering communications include sufficient focus and framing language and be logically organized, they should also be elegantly designed at the sentence and paragraph levels. Tone should be professional (in the third person to add professionalism and objectivity, where appropriate). Meaning should be easily accessible, arguments should be well-constructed, and language should be “polished.”

Below are some resources to help you get started composing documents that flow logically, are clear and precise, and use objective, professional language. In addition, browse the drop down menu under the “Composition” tab to get specific information and resources pertaining to organization and framing, augmentation, sentence-level clarity, IEEE formatting, and revision/editing strategies

Additional Resources
Print Friendly, PDF & Email