Quiz — Chapter 4: Structure

Target: 70%+ before moving on. Answers and explanations are hidden — attempt each before expanding.

Section 1 — Multiple Choice

1. The chapter's threshold concept is best stated as: - A) Style matters more than structure - B) The reader scans; they do not read - C) Always use the inverted pyramid - D) Headers should be decorative

Answer**B.** "The reader scans; they do not read" is the load-bearing idea—every technique follows from it. (A) is backward for most technical documents (§4.1). (C) is a default, not a law—OCAR sometimes withholds the conclusion (§4.8). (D) is the opposite of the truth; headers are functional navigation (§4.5). See §4.1.

2. "BLUF" means: - A) Brief, Logical, Useful, Factual - B) Bottom Line Up Front - C) Build Logic Under Findings - D) Background, Logic, Use, Finding

Answer**B.** Bottom Line Up Front—state your conclusion, recommendation, or request in the first sentence or two, then support it (§4.3). The others are invented distractors.

3. A writer organizes a report in the order they performed the investigation—checked the database, then the network, then found the real cause last. This is: - A) Top-down organization - B) The inverted pyramid - C) Bottom-up organization - D) Parallel structure

Answer**C.** Bottom-up organization presents evidence in the order it was gathered and builds to the conclusion at the end—it mirrors the *writer's* journey of discovery, not the *reader's* need. Top-down (A) and the inverted pyramid (B) would put the cause first. (§4.2)

4. The single best test for whether your topic sentences are functioning as a navigational map is: - A) Count the words in each - B) Check that each paragraph has exactly one - C) Read only the first sentence of every paragraph and see if they summarize the document - D) Make sure they all start with a transition word

Answer**C.** If reading only the first sentences, in order, gives a coherent summary, your topic sentences map the document for scanners. If it's a jumble, the real points are buried in paragraph middles. (§4.4)

5. Which content is best served by prose rather than a bulleted list? - A) The five fields a bug report must include - B) The three commands to install a tool, in order - C) An explanation of why one architecture was chosen over two alternatives - D) A checklist of pre-launch requirements

Answer**C.** A comparison-and-reasoning ("why X over Y and Z") is connected by logic; bullets would strip the connections that are the whole point. A, B, and D are discrete, parallel items—ideal for lists. Tell: if you'd write "because/therefore/however" between items, use prose. (§4.6)

6. The inverted pyramid puts __ at the top. - A) the methodology - B) the most important information (the bottom line) - C) the background and context - D) the caveats and limitations

Answer**B.** Widest part at top = most important, most general, most broadly relevant info—so a reader who stops early (or an editor cutting from the bottom) still gets the essential message. (§4.3)

7. Why is a correct heading hierarchy (no skipped levels, consistent nesting) also an accessibility requirement? - A) It makes the document print faster - B) Screen-reader users navigate by heading, jumping between them as a sighted reader scans - C) It reduces the file size - D) It is required by copyright law

Answer**B.** Screen-reader users pull up a list of headings and jump between them—exactly analogous to scanning. A broken hierarchy (skipped levels, headers used for visual size) makes the document genuinely harder to navigate with assistive tech. Good structure is inclusive structure. (§4.5)

8. OCAR stands for: - A) Outline, Compose, Assess, Revise - B) Opening, Challenge, Action, Resolution - C) Objective, Context, Analysis, Result - D) Overview, Conclusion, Argument, Reference

Answer**B.** Opening (setting/stakes), Challenge (the problem/tension), Action (what you did), Resolution (what it means). A narrative arc for read-through documents like papers and postmortems. (§4.8)

9. A research paper has an abstract that states the result up front and a body organized as a build-up narrative (problem → method → result). This is an example of: - A) A structural contradiction that should be fixed - B) Layered structure—inverted pyramid on top for scanners, OCAR beneath for deep readers - C) Bottom-up organization - D) Poor signposting

Answer**B.** You layer structures: a summary-first inverted pyramid serves the many who only read the abstract; an OCAR arc serves the few who read the whole body. Not a contradiction—a deliberate design serving two reading modes. (§4.8)

10. The structural failure in the Challenger engineering communication was that: - A) The engineers didn't have the data - B) The sentences were unclear - C) The critical conclusion was present but buried and fragmented, never given prominence as the bottom line - D) There were too many headers

Answer**C.** The engineers knew, and the relationship (cold → O-ring failure, untested this cold) was in the data—but it was scattered and buried, never isolated as the single conclusion at the top of an inverted pyramid, so time-pressured decision-makers never assembled it. Correct information, fatal structure. (§4.9)

11. Which header is informative (does its job for a scanner)? - A) ## Discussion - B) ## Other Considerations - C) ## Recommendation: Ship the One-Line Patch This Week - D) ## Details

Answer**C.** It states the actual content/claim, so a scanner navigating by headers learns the document's gist from the headers alone. A, B, and D describe *form*, not content—they tell the reader nothing about *this* document. (§4.5)

12. A "reverse outline" is: - A) An outline written before drafting, from bottom to top - B) An outline extracted from a finished draft by writing down each paragraph's point - C) A table of contents in reverse order - D) An outline of what to cut

Answer**B.** You make it *from* a draft—one line per paragraph's point—then read the list to expose the skeleton: buried conclusion, illogical order, pointless or overloaded paragraphs. The fastest structural diagnostic. (Project Checkpoint, §4.4, FAQ)

Section 2 — True/False with Justification

T/F 13. "Conclusion first" means you no longer need to show your evidence.

Answer**False.** It changes the *order*, not the amount of evidence. Support still appears—it follows the conclusion instead of preceding it, so a trusting reader can stop and a skeptical one can read on. Withholding the conclusion doesn't make it more proven; it makes it harder to find. (§4.3)

T/F 14. A bulleted list always makes a document more scannable and is therefore the safer default.

Answer**False.** Lists help for *discrete, parallel* items but destroy *connected reasoning*—bulletizing an argument deletes the logical relationships (because/therefore/however) that are its substance. A list is a tool for a specific job, not a default. (§4.6)

T/F 15. Even when a fixed template (like IMRaD) dictates section order, you still control structure within sections.

Answer**True.** Templates fix the skeleton, not the muscles. You can still lead each section with an informative topic sentence, write an abstract that states the finding up front, and use scannable subheaders. Follow the required form, then apply every other principle inside it. (§4.10, FAQ)

T/F 16. Parallel structure is purely a matter of style and doesn't affect how usable a document is.

Answer**False.** At the document level it's a *navigation* tool: when comparable parts share a shape (same subheaders, same order, same form), the scanner learns the pattern once and navigates instantly—comparing like with like, scanning a column of status words. Non-parallel parts force re-orientation every time. It directly serves scanning. (§4.7)

T/F 17. Bottom-up (conclusion-last) organization is never appropriate in technical writing.

Answer**False.** Conclusion-first is the *default*, not a law. Teaching narratives/tutorials may withhold the answer on purpose; sensitive bad news may need brief framing first; consensus-building may walk a resistant audience through reasoning. Even then, signpost relentlessly. The rule is "serve the reader's use," which *usually*—not always—means conclusion first. (§4.10)

Section 3 — Short Answer

18. In one sentence each, distinguish top-down from bottom-up organization, and say which one readers generally need.

Model answer**Bottom-up** presents information in the order the writer discovered it (chronological, evidence first, conclusion last); **top-down** presents it in the order the reader will use it (conclusion first, supporting detail after). Readers generally need top-down. *Rubric: both definitions correct + correct "readers need top-down."*

19. Give the practical "tell" that a piece of content wants to be prose rather than a list.

Model answerIf you find yourself wanting to write "because," "therefore," "however," or "which means" *between* the items, the content is connected by reasoning and wants to be prose; bullets would delete those connections. *Rubric: names the connective-words tell, or equivalently "the items are connected by logic, not discrete/parallel."*

20. Explain, in two or three sentences, how the inverted pyramid and OCAR can coexist in the same long document without contradiction.

Model answerThey operate at different layers for different readers. An inverted-pyramid summary (abstract/executive summary) sits on top and gives the bottom line to scanners who won't read further; an OCAR narrative arc structures the body beneath it for deep readers who want to be walked from problem to insight. You layer them—summary for the decision, arc for the understanding—rather than choosing one. *Rubric: identifies layering + maps each structure to a reading mode (scan vs. read-through).*

Section 4 — Applied Scenario

21. You're handed this email draft. Rewrite it (subject + body) using BLUF and good structure, then in one sentence name the single biggest structural change you made.

Subject: Quick question "Hi Sam, hope your week is going well! I wanted to reach out because the team has been discussing the database migration we talked about last month, and there are a few dependencies we've been untangling. We've now confirmed the backup strategy and tested the rollback procedure twice. Given that, I think we're ready to go, and I was wondering if you'd be able to approve us running the migration this Saturday during the maintenance window?"

Model answer + rubric**Rewrite:** > *Subject: Approval needed by Thursday: database migration, Saturday maintenance window* > *"Hi Sam, can you approve running the database migration this Saturday during the maintenance window? I need your go-ahead by Thursday. It's ready: the backup strategy is confirmed and we've tested the rollback procedure twice. Happy to share details if useful."* **Biggest structural change:** Moved the actual request (approve Saturday migration) and the deadline from the buried end of the email to the first sentence and the subject line (BLUF). *Rubric (4 pts): (1) subject line states the ask + timing; (2) request is the first sentence; (3) deadline is explicit and early; (4) justification demoted to support after the ask. Full marks = all four + correctly names the BLUF/conclusion-first move.*

Scoring & Next Steps

Score What to do
< 50% Re-read §4.1–§4.3 (scanning, top-down, inverted pyramid/BLUF). Redo Section 1.
50–70% Re-read the sections behind your missed items; redo Part B in exercises.md.
70–85% You're ready for Chapter 5. Do the Project Checkpoint reverse outline if you haven't.
> 85% Strong. Try Extension exercises E1–E2 (reverse-engineer a master document).

Back to: Chapter 4 · Exercises · Key Takeaways