The manual opens with a table of contents that reveals a tightly structured, hierarchical organization: chapters progress from the medical threat through command and control, levels of care, and specialized environments. The language is consistently imperative and procedural, as in “Actions Before a Nuclear, Biological, or Chemical Attack” (Chapter 3, Section 3-5). This voice establishes the manual as a directive reference rather than a descriptive text.

However, the excerpts also show a striking shift in pace and detail when moving from chapter headings to the appendices. The sample/specimen background document and CB Incident Interview form (Figure B-2) introduce a checklist-driven, interrogatory style—complete with fields for odor, consistency, and symptom onset—that contrasts with the earlier expository paragraphs. This change signals a move from broad tactical guidance to granular, on-the-ground data collection.

From Directive to Checklist: Two Registers of Language

The manual operates in two distinct linguistic registers. The first, found in chapters 1–4, uses declarative, instructional sentences: “Health Service Support Command and Control Planning Considerations” (2-2) and “Medical Triage” (3-13) are presented as numbered lists and subheadings. The tone is impersonal and authoritative, with frequent use of the future tense (“will be”) and passive constructions (“is conducted”).

The second register appears in the appendices, where language becomes interrogative and granular. The CB Incident Interview form asks: “ODOR: _____NONE _____SWEET _____FRUITY _____IRRITATING _____PEPPER _____FLOWER _____CHANGING _____ OTHER.” This shift from prescription to inquiry reflects the manual’s dual purpose: to instruct and to collect evidence. The checklist format forces a methodical pace, slowing the reader from skimming procedures to scrutinizing individual symptoms.

The Voice of Authority and the Voice of the Witness

The manual’s narrative voice changes depending on its target audience. In the main body, the speaker is the Department of the Army—an institutional “we” that issues commands: “Leaders must ensure…” (implied in 2-6). This voice assumes a commander or medical officer as reader, someone who needs broad operational guidance.

In the interview form, the voice shifts to that of an investigator or medic addressing a subject: “SUBJECT'S NAME: _____________________________________________________ ALIAS #1_____________________________ #2_____________________________.” The form’s structure anticipates a real-time conversation, with blank lines for narrative responses (“DESCRIBE DEVELOPMENT OF COLOR:_______________________”). This change in voice—from omniscient directive to neutral data collector—reflects the manual’s recognition that battlefield conditions require both top-down planning and bottom-up reporting.

Pacing Through Structure: Numbered Lists vs. Open-Ended Fields

The manual’s pacing is governed by its formatting. Early chapters rely on numbered paragraphs (e.g., 3-5, 3-6, 3-7) that create a predictable, skimmable rhythm. Each section is brief, often a single sentence or short paragraph, allowing rapid consultation during operations.

In contrast, the appendices introduce open-ended fields that demand slower, more deliberate reading. The sample/specimen background document includes lines for “COMMENTS: _____________________________________________________________” and “RELATED SPECIMENS_________________________________________.” These blank spaces visually break the dense text, inviting the user to pause and write. The interview form’s checkboxes (“YES___ NO___”) and lined prompts (“DESCRIBE:_________________”) create a hybrid pace: quick ticks for binary data, longer pauses for narrative description. This structural variation mirrors the manual’s function as both a quick-reference guide and a detailed recording tool.

Readers should note that the manual’s appendices are not afterthoughts but integral to its purpose. The shift from procedural prose to data-collection forms reflects a core tension in NBC medical support: the need for standardized, rapid action versus the need for precise, individualized documentation. Pay attention to how the manual uses white space, checkboxes, and blank lines to modulate reading speed—a subtle but crucial feature for field use.