Technical Writing Cheat Sheet 2026

The 30 highest-yield Technical Writing facts, distilled from real exam questions. Print it, save it as a PDF, or study it here — free, no sign-up.

1. Which practice helps maintain consistent tone across a large documentation set? → A style guide or voice and tone guidelines
2. Which document is created to explain how two parties must fulfill agreed-upon service levels? → Service Level Agreement (SLA)
3. What does the term 'minimalism' mean in the context of technical documentation? → Including only the information users need to complete their tasks
4. Which document type is BEST suited for capturing agreed-upon system behaviors between stakeholders and developers? → Software Requirements Specification (SRS)
5. In documentation, what is 'single sourcing'? → Writing content once and reusing it across multiple outputs or formats
6. A writer notices inconsistent capitalization of a product name throughout a 50-page manual. What is the BEST corrective action? → Search and replace using the style guide's approved capitalization
7. Which rule applies to the use of contractions in technical documentation? → Contractions may be used to create a friendly tone when the audience and context allow
8. Which writing style guideline does the US federal plain language standard emphasize? → Use common, everyday words
9. What is minimalism in technical writing (after John Carroll)? → Giving users only what they need to complete tasks, minimizing unnecessary content
10. What should a figure caption in technical documentation include? → A brief, descriptive label that explains what the figure shows
11. When should a technical writer use second-person 'you' in documentation? → Procedural instructions addressing the user
12. The '7±2 rule' in technical writing documentation relates to: → The ideal number of items a reader can process in a list or menu
13. What is a user persona in technical writing? → A fictional profile representing a target reader type
14. What is the purpose of a legend (key) in a technical diagram? → To explain the symbols, colors, or abbreviations used in the diagram
15. What is 'white space' in the context of technical document design? → Intentional empty space around text and visuals that improves readability
16. What is the rule for capitalizing job titles in technical documents? → Capitalize job titles only when they precede a person's name
17. What is the PRIMARY purpose of a document's executive summary? → To provide a brief overview so decision-makers can grasp key points quickly
18. Today, the ___________________ is quite helpful for providing business reports. → MS PowerPoint
19. What is a use case in the context of technical documentation? → A scenario describing how a user interacts with a system to achieve a goal
20. What is the difference between editing and proofreading? → Editing addresses content and structure; proofreading catches surface errors
21. A procedure step reads: 'It may be necessary to restart the application.' What is wrong with this instruction? → It is vague and not action-oriented; users need a clear directive
22. Which rule dictates how to handle units of measurement in technical documents? → Use abbreviations consistently and follow a recognized standard such as SI
23. What is a job aid in technical communication? → A quick reference tool (card, poster, checklist) used on the job to support performance
24. Which metric best measures whether technical documentation is effective? → Task completion rate in usability tests
25. What is the purpose of a style guide review in technical writing? → Ensure conformance to voice, tone, and terminology standards
26. What is a release note's primary function? → Document changes, fixes, and new features in a software release
27. Why are templates used? → Templates provide guidelines for the formatting of a document.
28. What key subject matter do many technical writing courses cover? → Technical writings
29. When writing error messages in US software documentation, which tone is recommended? → Helpful and non-blaming
30. Which iterative development approach most directly influences modern technical writing practices? → Agile