Chapter 35: Writing for Science: The Conventions That Govern Scientific Publication

"The scientific paper has, since its origins, served a dual function: to make new knowledge public, and to claim it as one's own." — adapted from the standard account of the origins of scientific publishing; treat as Tier 2 attributed history

Chapter Overview

Dr. Lena Foss has been here before. Three years ago, the electrolyte-additive paper you met in Chapter 14 (Research Papers) taught her that a paper is an argument, not a chronicle — and that a reviewer who asks for a major revision is offering to publish your work if you'll meet them halfway. She learned to frame a claim, shape an hourglass, and respond to Reviewer 2 without setting the building on fire. She got published. The science was right; the writing finally matched it.

Now she has a bigger result. Her lab has moved from liquid electrolytes to solid-state cells — a sulfide solid electrolyte that holds 91% capacity retention after 1,000 cycles at a current density other groups can't sustain without the cell short-circuiting. It's the best work she's done. She writes it up, frames the argument cleanly, builds a beautiful hourglass — and then runs straight into everything Chapter 14 didn't teach her. Should the Methods be in passive voice or active? Her chemist co-author says passive; her cell-biologist collaborator from a joint project says her field switched to active years ago. How exactly does she write "the retention was higher in the treated cells" so a statistician won't wince — what's the right way to report an F statistic, and does she owe the reader an effect size? Forty pages of raw cycling data can't go in the paper, but they can't vanish either — where? Should she post a preprint before review, or does that scoop her? Science rejected it without review in four days; a specialist journal wants it — how should the cover letter have been different? And when the reviews come back, two of them sharp, how does she write the response letter that turns a "major revision" into an "accept" — again, but for higher stakes?

None of these are questions about the argument. The argument is sound; Chapter 14 saw to that. These are questions about convention — the specific, often unwritten rules of how science is packaged, submitted, defended, and shared. They differ by field, by journal, and by decade, and getting them wrong gets good science rejected or ignored. This chapter is the operating manual for the machine you feed your paper into. By the end of it you will be able to write to your subfield's actual voice, report statistics so a skeptic can check them, build a supplement that earns trust, post a preprint without fear, write the cover letter that gets you past the editor's desk, and answer reviewers in a way that gets a hard paper published.

In this chapter, you will learn to:

• Read and write to your subfield's voice conventions instead of a generic "science voice."
• Report statistics in a standard, checkable form — the right statistic, degrees of freedom, exact p, and an effect size.
• Decide what goes in the paper versus the supplementary materials, and write the supplement well.
• Handle the modern apparatus of publishing: preprints, open access, author-contribution statements, and data-availability statements.
• Write the two letters that decide a paper's fate — the cover letter to the editor and the response to reviewers — gracious and firm.

📕 Engineering/Science track: This is a core chapter for you, and it assumes Chapter 14 (Research Papers). If you write in CS or software, the spirit here transfers — conventions are local, gatekeepers are human — but your venue is more often conferences and your "supplement" is more often a code repository; Chapter 34 (Writing for Computer Science) is your closer fit. If you're on the Business/Professional track and never plan to publish, you can skim — but the response-letter section is the best training in disagreeing professionally you'll find in this book.

35.1 There Is No "Science Voice" — There Are Field Voices

Open a chemistry journal and a molecular-biology journal to the Methods section of any paper, and you are reading two different languages that happen to share an alphabet.

Here is a Methods sentence as a synthetic chemist would write it:

The additive was synthesized by refluxing the precursor in anhydrous THF for 12 h under argon. The product was purified by column chromatography and characterized by ¹H NMR.

Here is the same kind of sentence as a contemporary cell biologist might write it:

We treated the cells with 10 µM of the compound for 24 h and then measured viability using a standard assay.

Read them again. The chemist's sentences have no people in them. Things get synthesized, purified, characterized — the grammatical subject is always the substance, and the human who did the work has vanished into the passive voice. The biologist's sentences put we right at the front: we treated, we measured. Neither is wrong. Each is correct in its field and would look slightly off in the other. A chemist writing "we refluxed the precursor" reads as faintly informal to other chemists; a biologist writing "the cells were treated" reads as needlessly stiff to other biologists. Same language family, different dialects.

This is Theme #2 (audience is everything) arriving in its most concrete form yet. In Chapter 3 (Clarity) you learned that the active voice is usually clearer and that the passive often hides the actor — true, and still true. But "usually" is doing real work in that sentence. A convention is an audience expectation, and violating it costs you credibility even when your sentence is objectively clearer. The skill of this section is not "always use the active voice" or "always use the passive." It's reading your subfield's actual practice and writing to it.

Why chemistry kept the passive

The passive voice in chemistry isn't an accident of tradition; it does a job. Chemistry Methods are recipes meant to be reproduced exactly, and the reader does not care who held the flask. Putting the substance in the subject position foregrounds the thing that matters — the compound, the reaction, the conditions — and lets the human recede. "The product was purified by column chromatography" centers the product; "We purified the product by column chromatography" centers you, which is not where a replicating chemist's attention should go. The passive also generalizes cleanly: the recipe works regardless of who runs it, and the impersonal grammar quietly says so.

This is the same logic Chapter 13 (Lab Reports) gave you for Methods sections generally — "put the sample, not you, in the subject position." Chemistry simply takes that logic furthest, and its journals have codified it.

Why biology drifted toward the active

Molecular and cell biology drifted the other way over recent decades, and several major journals now explicitly encourage the active voice and the first-person "we" in their author guidelines. The reasoning is the mirror image: in experimental biology the choices the researchers made — which line, which dose, which timepoint — are part of what's being evaluated, so naming the agent ("we chose," "we treated") is honest about the design rather than hiding it behind grammar. The active voice is also shorter and clearer, and biology, with its sprawling multi-step protocols, has more to gain from cutting words.

🔄 Check Your Understanding. A geologist writes: "The samples were collected from three sites and were analyzed for trace-element composition." A neuroscientist writes: "We recorded from 47 neurons across four animals." Without knowing either field's rules, what can you infer about each field's conventions from these two sentences — and what does that tell you about how to find your own field's convention?

Answer

The geologist uses the passive ("were collected," "were analyzed") and erases the agent — suggesting a field, like chemistry, where the sample and the measurement are the focus and who collected them is irrelevant. The neuroscientist uses the active first-person "we recorded" and even foregrounds the design (47 neurons, four animals) — suggesting a field, like experimental biology, where the researcher's choices are part of the evidence. The deeper lesson: you don't infer your field's convention from a rule, you infer it from reading your field's papers. Pull three recent papers from your exact target journal, read their Methods, and write the way they write. The convention is on the page.

How to actually find the convention (the only reliable method)

You do not learn a field's voice from a style guide. You learn it the way Chapter 14 told you to find a venue: read three recent papers in your exact target journal and imitate their Methods voice. That is not a shortcut; it is the method. Author guidelines sometimes state a preference ("we encourage the active voice"), but the lived convention is on the page, in what the editors actually accepted last year. When in doubt:

• Match the journal, not the field in the abstract. A multidisciplinary journal (Nature, Science, PNAS) tolerates more first-person and more narrative than a specialist one. A specialist chemistry journal will be more conservative than a specialist biology one.
• Be consistent within the paper. The worst choice is to switch voices paragraph to paragraph because you couldn't decide. Pick the convention and hold it.
• Use the active voice for your choices, even in a passive-leaning field. Even conservative chemistry journals now accept "we hypothesized that…" or "we therefore chose to…" in the Introduction and Discussion, where you are the agent. The passive belongs to the recipe (Methods), not to the reasoning.

Lena's situation is the interesting edge case: she's a chemist by training (passive instinct) submitting to a materials journal that publishes both chemists and engineers. She pulls three recent papers from her target journal and finds the Methods uniformly passive — so she writes the Methods passive. But the Introduction and Discussion in those same papers use "we" freely for the reasoning. So she does too. The convention isn't "Lena always writes passive"; it's "passive recipe, active reasoning, as this journal's authors do."

🔍 Why Does This Work? Why is it defensible to use the passive voice in Methods but the active voice in the Discussion of the same paper, when Chapter 3 told you the active voice is clearer? Think before reading.

Answer

Because the two sections answer different questions and have different agents. Methods answers "what was done?" — and the honest agent is the procedure, which works regardless of who runs it; foregrounding the substance ("the product was purified") serves the replicating reader and matches the recipe's impersonal generality. The Discussion answers "what do we make of it?" — and the agent there genuinely is you: you interpreted, you inferred, you chose to bound the claim. Hiding that behind the passive ("it was concluded that") is not more rigorous, it's evasive — it dodges responsibility for a judgment that is yours. Chapter 3's rule ("prefer the active") still holds; the passive earns its place in Methods precisely because the actor is genuinely irrelevant there, which is the one condition under which Chapter 3 said the passive is justified.

[📍 Good stopping point — the rest of the chapter is the machinery: statistics, supplements, and the letters.]

35.2 Reporting Statistics So a Skeptic Can Check You

Here is a results sentence that should never reach a journal:

❌ Before: "The treated cells performed significantly better than the controls."

A reviewer reading that has three immediate questions and no way to answer them. Significantly — by what test? Better — by how much? And what's the actual evidence — the numbers behind "significantly"? The sentence asserts a result without reporting it. It is the statistical cousin of Chapter 14's fatal abstract flaw ("the results are promising"): it tells you a result exists without telling you what it was.

Now the same finding, reported so a skeptic can check it:

✅ After: "Capacity retention after 1,000 cycles was higher in cells with the sulfide electrolyte (M = 91.2%, SD = 1.8) than in the liquid-electrolyte controls (M = 78.4%, SD = 3.1), a difference of 12.8 percentage points, t(38) = 9.4, p < .001, d = 2.1."

Why it's better: Every one of the reviewer's questions is now answered in a form they can verify. They can see the means and spreads (so they know how big and how variable the effect is), the test and its degrees of freedom (so they know what was computed and on how many samples), the exact p-value (so they can judge the strength of evidence), and the effect size (so they know the difference is large, not just "significant"). This is Theme #3 in numerical form: clarity is not the enemy of precision. The vague sentence wasn't more careful by staying general; it was less useful. The precise one is both more honest and more persuasive.

Most fields report statistics in a house style descended from the APA (American Psychological Association) Publication Manual, whose conventions have become the lingua franca far beyond psychology. You should check your target journal's specifics, but the APA defaults below will be recognizable and correct almost everywhere.

The anatomy of a reported test

A statistical result in APA-descended style has a predictable shape: the test statistic with its degrees of freedom, then the exact p-value, then the effect size. Read these as a fixed grammar:

t(38) = 9.4, p < .001, d = 2.1
   │     │      │          └─ effect size (Cohen's d): the difference is ~2 SDs — huge
   │     │      └─ p-value: probability this extreme if there were no real effect
   │     └─ the computed statistic
   └─ degrees of freedom (here ≈ sample size − 2 for a two-group t-test)

F(1, 47) = 4.23, p = .045, η² = .08
  │   │     │       │         └─ effect size (eta-squared): ~8% of variance explained
  │   │     │       └─ exact p, reported to two or three decimals
  │   │     └─ the F statistic
  │   └─ two df for F: numerator (between-groups) and denominator (within-groups/error)

Notice the details that mark a writer who knows the conventions:

• Statistic symbols are italicized (t, F, p, r, M, SD, d) but the numbers are not. (In Markdown that's *t*, *p*, etc.) Greek-letter statistics — η², χ², β — are not italicized.
• Degrees of freedom go in parentheses right after the statistic: t(38), F(1, 47), χ²(3, N = 200). For F there are always two df, and getting them in the wrong order (F(47, 1)) instantly signals you don't know what you're doing.
• Report the exact p-value, not just "p < .05." Write p = .045 or p = .003. The one exception is genuinely tiny values: write p < .001 rather than p = .0000003.
• In APA style, p-values have no leading zero because p can't exceed 1: write p = .045, not p = 0.045. The same goes for correlations and other quantities bounded by ±1 (r = .62, not 0.62). Quantities that can exceed 1 — means, t, F — keep their leading zero where relevant.
• Round sensibly: test statistics and most values to two decimals; p-values to two or three. Don't report t(38) = 9.41728; the spurious precision tells the reader you pasted from software without thinking.

⚠️ Warning — the leading-zero rule trips up nearly everyone. "p < 0.05" is the single most common statistical-formatting error in submitted manuscripts. In APA style it's p < .05 — no zero before the decimal, because a probability can never reach 1. Get this one right and you immediately read as someone who has done this before.

Effect size: the number reviewers increasingly demand

For two decades the message from methodologists and journal editors has been the same: a p-value alone is not enough. A p-value tells you whether an effect is detectable given your sample size; it does not tell you whether the effect is large enough to matter. With a big enough sample, a trivial difference becomes "statistically significant." So modern reporting standards — and a growing number of journal policies — require an effect size alongside every significance test.

🧩 Productive Struggle. Two studies both report p = .04. Study A has 20 participants; Study B has 20,000. Before reading on: which result are you more impressed by, and why might the p-value alone mislead you here? Write down your reasoning.

Answer

With 20,000 participants, statistical significance is cheap — a tiny, practically meaningless difference will clear p = .05 easily because the test has enormous power to detect even trivial effects. So Study B's p = .04 might describe a difference too small to care about. Study A's p = .04 with only 20 participants had to overcome low power, which usually means the underlying effect is larger. But — and this is the real lesson — you cannot actually tell from the p-values, which is exactly why they're insufficient. You need the effect size: Cohen's d, η², r, an odds ratio, or the raw difference with a confidence interval. Report p = .04, d = 0.2 (Study B) and p = .04, d = 1.1 (Study A) and the picture is instantly clear. This is why "report an effect size" is now a near-universal expectation: the p-value answers "is it detectable?"; the effect size answers "is it big?" — and only the second question usually matters.

Common effect-size measures, by the kind of test:

The "rough interpretation" column carries a warning: those thresholds (Cohen's conventions) are rules of thumb, not laws. A d of 0.3 might be huge in one field and negligible in another. Report the number; interpret it in context of your field, not by reflexively calling 0.5 "medium."

Confidence intervals: the form that's quietly winning

Increasingly, journals — especially in medicine and ecology — prefer (or require) a confidence interval over, or alongside, a bare p-value. A CI does more work: it reports the effect and its uncertainty in the units you care about.

❌ Weaker: "The treatment significantly reduced internal resistance (p = .02)." ✅ Stronger: "The treatment reduced internal resistance by 8.3 Ω (95% CI [2.1, 14.5], p = .02)."

Why it's better: The CI tells you the effect is probably somewhere between a trivial 2 Ω and a large 14 Ω — useful, and honest about the imprecision — whereas "significant" hides all of that. Note the bracket-and-comma format APA uses for intervals: 95% CI [2.1, 14.5].

💡 Tip — three things to standardize across your whole paper. (1) Decide how many decimals each quantity gets and use it everywhere. (2) Report the same effect-size measure for the same kind of test throughout — don't give d for one comparison and η² for an identical one. (3) State your alpha and any corrections for multiple comparisons once, in Methods, rather than re-litigating significance in every Results sentence. Consistency here reads as competence.

🔄 Check Your Understanding. Fix this reported result: "There was a significant effect of electrolyte type on capacity (F(2,57)=8.9, P=0.0003)." Name every convention it violates.

Answer

Violations: (1) F and P should be italicized, the numbers should not (*F*, *p*); (2) lowercase p, not capital P; (3) no leading zero on the p-value — p < .001 (and at that magnitude you'd write < .001 rather than = .0003); (4) spacing — APA puts a space after each comma and around the equals sign: *F*(2, 57) = 8.9; (5) most importantly, no effect size and no means — the reader can't tell how big the effect is or in which direction. A corrected version: "Electrolyte type affected capacity retention, F(2, 57) = 8.9, p < .001, η² = .24; retention was highest for the sulfide electrolyte (M = 91.2%) and lowest for the control (M = 78.4%)."

35.3 Supplementary Materials: The Room Behind the Paper

Lena has forty pages of cycling curves, three additional control experiments, the full synthesis characterization, a table of every cell's individual performance, and the code that fit her degradation model. None of it fits in a 6,000-word paper. All of it matters to somebody. This is what supplementary materials (also called supporting information, SI) are for: the room behind the paper where everything that supports the argument but would interrupt it goes to live.

The threshold question — and it is a genuine judgment call — is what goes in the paper versus what goes in the supplement. Get this wrong in either direction and you hurt the paper. Bury a load-bearing result in the SI and reviewers miss it; stuff the main text with material only a specialist replicator wants and you drown your argument.

The rule follows directly from Chapter 14's principle that a paper is an argument:

Main text gets exactly what the argument needs to stand. The supplement gets what a skeptic needs to verify it.

Two failure modes to avoid:

• The supplement as a dumping ground. A 90-page SI of unlabeled figures and uncommented spreadsheets is not "thorough" — it's an abdication. The supplement is still writing. Every supplementary figure needs a caption that stands alone (Chapter 9's lesson doesn't pause at the SI boundary); every table needs a header; the whole thing needs enough structure ("Section S1: Synthesis details," "Figure S3") that a reader can find what a main-text callout points to.
• The supplement as a hiding place. Moving an inconvenient result, a failed replicate, or a key limitation into the SI to keep the paper clean is a small act of dishonesty that reviewers are trained to catch. If a result bears on your claim, it belongs where the claim is. The SI is for supporting detail, not for suppressing awkward detail.

A small but real convention: refer to supplementary items with the S prefix (Figure S1, Table S2, Section S3) so they're unmistakable from main-text items (Figure 1, Table 2), and make sure every S-item is actually called out somewhere in the main text. An uncited supplementary figure is one the reviewer assumes you forgot to delete.

✏️ Try This. Take a result from your own work — a robustness check, a secondary analysis, a piece of method detail. In one sentence, argue for putting it in the main text; in one sentence, argue for the supplement. Whichever argument is harder to make tells you where it belongs.

35.4 Preprints and Open Access: Publishing Before, and Beyond, the Journal

For three centuries the model was simple: you submitted to a journal, waited months, and your work became public only when it was accepted. Two changes have rewired that pipeline, and a modern scientist has to make a deliberate choice about each.

Preprints: making it public before review

A preprint is a complete manuscript posted to a public preprint server — arXiv (physics, math, CS), bioRxiv (biology), medRxiv (health), ChemRxiv (chemistry), and others — before or alongside peer review. It is the same paper, just made public early and unreviewed.

The case for posting a preprint is strong and increasingly mainstream:

• Speed. Your result is timestamped and readable the day you post it, not eight months after you submit. In fast-moving fields, that's the difference between leading and trailing.
• Priority. A public, dated preprint is a citable claim to having had the idea first — which addresses the very anxiety ("will I get scooped?") that makes some researchers hesitate.
• Feedback. Strangers email you about errors and extensions before the work is frozen in print. That's free review.
• Access. Anyone can read it immediately, for free, forever.

The case against (or rather, the cautions):

• It isn't peer-reviewed, and you must label it so. A preprint is a draft made public, not a validated result; reporting it as if it were vetted is a misrepresentation.
• Some journals have rules — most now explicitly allow preprints (and many encourage them), but a few high-profile venues have historically been restrictive. Check your target journal's preprint policy before posting, not after.
• In a few clinical or sensitive areas, posting unreviewed findings that the public might act on carries real risk — the medical-writing caution you'll meet in Chapter 36 applies here too.

Lena's call: her field moves fast and her result is strong, so she posts to ChemRxiv the same day she submits to the journal, with a clear "This is a preprint and has not been peer-reviewed" banner. The preprint gets read and cited within weeks; one of those readers turns out to be a reviewer who already respects the work by the time the formal review starts. Posting cost her nothing and bought her priority, feedback, and reach.

Open access: who can read it once it's published

Open access (OA) is about the published version: whether readers can get it free, or whether it sits behind a subscription paywall. The vocabulary is worth knowing because it comes with very different price tags and obligations:

The crucial, often-painful detail is the article processing charge (APC): in gold OA, you (your grant, your institution) pay — sometimes $2,000–$11,000 — to make the article free for readers. Many funders now mandate open access (the work they paid for must be public), which makes OA not just a preference but a compliance requirement. Plan for the APC when you budget the grant (Chapter 17's lesson), and know that green OA — self-archiving the accepted manuscript in your institution's repository or a preprint server — is the free route to compliance when an APC isn't in reach.

⚠️ Warning — don't confuse open access with predatory publishing. Chapter 14 warned you about predatory journals: the tell is not that a journal charges a fee (legitimate gold-OA journals charge APCs); the tell is the fee plus no real peer review, plus unsolicited flattery and absurd speed. A real OA journal does everything a subscription journal does — rigorous review, real editing — and simply shifts who pays. Vet OA venues exactly as carefully as any other.

🔄 Check Your Understanding. A colleague says: "I can't afford the $3,000 APC, so there's no way to make my paper open access." Is she right? What are her options?

Answer

She's wrong — APC-funded gold OA is only one route. Her options: (1) Green OA — publish in a subscription journal and self-archive the accepted manuscript (the peer-reviewed version, often pre-typesetting) in her institutional repository or a preprint server, which is free and satisfies most funder mandates after any embargo; (2) APC waivers — many gold-OA publishers waive or discount fees for authors from lower-income countries or without funding (you have to ask); (3) Diamond/platinum OA journals that charge neither readers nor authors; (4) check whether her institution or funder has a read-and-publish "transformative" agreement that covers the APC. The takeaway: open access is increasingly a funder requirement, and there is almost always a free or subsidized path to it — the APC is the visible route, not the only one.

35.5 Who Did What: Author-Contribution Statements

A generation ago, authorship was a black box: a list of names in a disputed order, with no statement of who actually did the work. That opacity bred two chronic problems — guest authorship (a senior name added for prestige who contributed nothing) and ghost authorship (someone who did real work but was left off) — and it made misconduct hard to localize when a paper went wrong. The response is now near-universal: the author-contribution statement.

Most journals now require one, and a large and growing number use a specific controlled vocabulary called the CRediT taxonomy (Contributor Roles Taxonomy) — fourteen standardized roles such as Conceptualization, Methodology, Investigation, Formal analysis, Writing – original draft, Writing – review & editing, Supervision, and Funding acquisition. The statement maps each author to their roles:

Author contributions (CRediT): L.F.: Conceptualization, Methodology, Investigation, Formal analysis, Writing – original draft. R.O.: Investigation, Data curation. A.N.: Methodology, Software, Formal analysis. M.S.: Supervision, Funding acquisition, Writing – review & editing.

This is more than bureaucratic box-ticking. The contribution statement does real ethical and practical work:

• It makes credit precise and fair — the first-year student who ran every cell gets Investigation in print, not silent erasure.
• It localizes responsibility — if the statistics are later questioned, the reader knows who did the Formal analysis.
• It governs authorship disputes — the act of filling it out forces the awkward, necessary conversation about who did what before submission, not after.

Closely related is the role of corresponding author — the one who manages the submission, communicates with the editor, handles the response letter, and remains the contact after publication. It's often (not always) the senior PI or the person who led the writing; for Lena's paper, it's Lena. The corresponding author carries an extra duty of care: they're the one the journal holds accountable for the integrity of the submission.

The ICMJE (International Committee of Medical Journal Editors) recommendations set the most widely cited bar for who qualifies as an author at all — substantial contribution to conception or analysis, plus drafting or revising, plus approving the final version, plus agreeing to be accountable. The principle generalizes well beyond medicine: authorship means intellectual contribution and accountability, not just proximity to the project. Acquiring funding or supervising a lab, by itself, does not earn authorship under the ICMJE bar — a useful thing to be able to cite, gently, when a senior figure expects a free name.

💡 Tip — settle authorship early, in writing. The most poisonous disputes in science are about author order and inclusion, and they're worst when raised at submission. Agree on roles and order at the start of a project and revisit it as contributions change. The contribution statement is the artifact that forces this; treat it as a planning tool, not a closing formality.

35.6 The Cover Letter: Getting Past the Editor's Desk

Before a single reviewer sees Lena's paper, one person decides whether reviewers ever will: the handling editor. They triage dozens of submissions, and they desk-reject — reject without review — anything that's a poor fit, under-significant for the journal, or badly presented. The document that speaks to that editor is the cover letter, and a generation of researchers treats it as a formality. It is not. It is a short, high-leverage piece of persuasive writing aimed at a single, busy, expert reader — which is to say it's a pure exercise in everything this book teaches.

Here is the cover letter that got Lena desk-rejected from a general-science journal in four days:

❌ Before (generic, mis-aimed, says nothing the abstract doesn't):

Dear Editor,

Please find attached our manuscript titled "Capacity Retention in Sulfide Solid-State Electrolyte Cells" for consideration for publication in your esteemed journal. In this work we investigate a novel solid electrolyte and report its electrochemical performance. We believe our findings will be of interest to your readers. All authors have approved the manuscript and it is not under consideration elsewhere.

Thank you for your consideration. Sincerely, Dr. Lena Foss

Read what this letter fails to do. It restates the title (the editor can read the title). It calls the journal "esteemed" (flattery that signals you'll say it to anyone). It says the work will "be of interest" without saying why it matters or to whom. Above all, it never answers the editor's actual question — why does this belong in this journal, and why now? For a high-selectivity general journal, the unanswered "why is this significant to a broad audience?" is fatal: the editor can't see the broad importance, so the paper never reaches review.

Now the letter she should have written to a journal that fits — a specialist materials/energy journal — and what it does differently:

✅ After (specific, makes the significance case, fits the venue):

Dear Dr. [Editor's name],

We are submitting our manuscript, "Capacity Retention in Sulfide Solid-State Electrolyte Cells," for consideration as an Article in [Journal].

Solid-state batteries promise higher energy density and safety than liquid-electrolyte cells, but their adoption is blocked by capacity fade at the high current densities that practical fast-charging requires. We report a sulfide solid electrolyte that sustains 91% capacity retention after 1,000 cycles at 2 mA/cm² — a current density at which comparable cells in the recent literature short-circuit within 200 cycles. To our knowledge this is the first demonstration of stable cycling in this electrolyte class at this current density, and it directly addresses the dendrite-suppression problem that [Journal] has published extensively on (e.g., the work in your [year] special issue on solid-state interfaces).

We believe this result is well suited to [Journal]'s readership of electrochemists and materials engineers working on next-generation storage. The manuscript is original, is not under consideration elsewhere, and all authors have approved it. A preprint is posted on ChemRxiv. We suggest [2–3 potential reviewers with no conflict of interest] and request the exclusion of [any conflicted reviewers], if appropriate.

Thank you for considering our work. Sincerely, Dr. Lena Foss (corresponding author), on behalf of all authors

Why it's better: It does the four things a cover letter exists to do. (1) It states the specific contribution with the headline number (91% / 1,000 cycles / 2 mA/cm²) — the editor learns the result without opening the PDF. (2) It makes the significance case for this journal — naming the exact problem (dendrites at high current density) and even the journal's own prior work, proving fit rather than asserting it. (3) It handles the housekeeping editors require (originality, no concurrent submission, author approval, preprint disclosure) crisply. (4) It offers suggested and excluded reviewers, which most journals invite and editors appreciate. Notice it does not oversell ("revolutionary," "paradigm-shifting") — the claim is bounded exactly as the paper's is, which reads as the confidence of someone whose result speaks for itself.

The deeper lesson is the one Lena learned the expensive way: the cover letter is where you choose your venue's frame. The same paper failed at the general journal and fit the specialist one, and the difference the editor saw first was the letter. A general journal needs the "why does a non-specialist care?" case; a specialist journal needs the "why is this a real advance within the field?" case. Aim the letter at the actual reader — which is just Chapter 2, with the editor as the audience.

🪞 Learning Check-In. Pause and notice something. Every "new" skill in this chapter so far — field voice, statistical reporting, the cover letter — has turned out to be an application of a principle you already have: audience (Ch 2), clarity-vs-precision (Ch 3), structure (Ch 4), the paper as argument (Ch 14). What feels genuinely new here, and what feels like an old principle wearing field-specific clothes? Being able to tell the difference is what lets you walk into an unfamiliar field and write well in it fast — you port the principles and learn only the local conventions. That transfer is the skill this whole Part is teaching.

35.7 The Response to Reviewers: Where Hard Papers Get Published

The reviews come back. The editor's email says major revision — which, as Chapter 14 taught Lena, is a victory: it means "we'll publish this if you address these concerns." But the concerns are sharp. Reviewer 1 likes the work but wants more. Reviewer 2 is skeptical and a little condescending. Lena's first instinct, reading Reviewer 2 at 11 p.m., is to defend everything. That instinct is the enemy, and learning to overrule it is the most valuable writing skill in a scientist's career.

The response to reviewers (or rebuttal letter — though "rebuttal" is a misleading name, since the goal is rarely to rebut) is a distinct genre with its own conventions, and Chapter 14 gave you its three rules: address every comment; concede what's right, gladly; disagree with evidence, not attitude. This section is where you build the whole letter, end to end, and learn the mechanics that make it work.

The mechanics that make a response letter work

A response letter is read by busy people checking whether you did what they asked. Its form is therefore as important as its content:

• Quote every comment in full, then respond beneath it — usually in a visually distinct block (a different color, or the comment in bold/italic and your response in plain text). The editor must be able to read the comment and your answer as a standalone unit without flipping back to the original reviews.
• Number them to match the reviewers' numbering, so nothing gets lost.
• State exactly what changed and where — "we have added this control (new Figure 6)," "revised text, Discussion para. 4, p. 11," "new Table S3." Reviewers verify; make verification effortless.
• Open with a brief, genuine thank-you and a one-line summary of the main changes, so the editor sees the shape of the revision before the details.
• Never silently ignore a comment. Concede it, answer it, or honestly decline it with a reason — but every comment gets a visible response.

The whole letter, before and after

Here is the kind of response Lena drafted at 11 p.m. — the one her past self from Chapter 14 might have sent before she learned better. Reviewer 2 has raised three points: the novelty claim, a missing comparison, and the durability of the effect.

❌ Before (defensive — the letter that turns a major revision into a reject):

We thank the reviewers. Responses below.

Reviewer 2, Comment 1 ("The novelty over prior sulfide-electrolyte work is unclear"): We disagree. Our novelty is clearly stated in the introduction. The reviewer appears not to have read it carefully. No change.

Reviewer 2, Comment 2 ("No direct comparison to the [competing] electrolyte"): A direct comparison is outside the scope of this paper, which is about our system. The reviewer is asking us to do a different study. No change.

Reviewer 2, Comment 3 ("1,000 cycles may not capture long-term fade"): Our 1,000-cycle protocol is standard. We see no reason to extend it and decline to do so.

Now read what that letter does, comment by comment. To Comment 1 it says, in effect, you can't read. To Comment 2 it refuses a reasonable request and offers nothing. To Comment 3 it stonewalls a legitimate scientific concern. Even where Lena has a real point (her protocol is standard), the framing guarantees Reviewer 2 digs in — and Reviewer 2 is the one advising the editor. Three "no change" responses to a major revision read as an author who won't revise, which is the one thing that converts "major revision" into "reject."

Here is the same set of disagreements, handled by the Lena who wants the paper published:

✅ After (gracious and firm — the letter that gets a hard paper accepted):

We thank both reviewers for their careful reading. The manuscript is substantially stronger for it. In brief, we have added a direct comparison to the [competing] electrolyte (new Figure 4), extended cycling to 1,500 cycles for a representative subset (new Figure 6), and sharpened our novelty claim in the Introduction. Point-by-point responses follow; reviewer comments are in bold, our responses in plain text, and new or changed manuscript text is quoted in italics.

Reviewer 2, Comment 1: "The novelty over prior sulfide-electrolyte work is unclear." We appreciate this — on rereading our Introduction, we agree the novelty was stated too obliquely. The advance is not the electrolyte class itself but stable cycling at 2 mA/cm², a current density at which prior sulfide cells (refs. 12, 14) short within ~200 cycles. We have rewritten the relevant paragraph to make this explicit: "Unlike prior sulfide-electrolyte cells, which fail by dendrite penetration above ~1 mA/cm² [12,14], the cells reported here cycle stably at 2 mA/cm² for 1,000 cycles…" (Introduction, para. 3, p. 2). We hope this resolves the ambiguity; if the distinction is still not sharp enough, we are glad to revise further.

Reviewer 2, Comment 2: "No direct comparison to the [competing] electrolyte." The reviewer is right that this comparison strengthens the paper, and we were wrong to omit it. We have run our protocol on [competing]-electrolyte cells under identical conditions and added the result as new Figure 4; our electrolyte retains 91% versus 81% for [competing] at 1,000 cycles. We thank the reviewer for pushing us toward a comparison that materially improves the work.

Reviewer 2, Comment 3: "1,000 cycles may not capture long-term fade." This is a fair concern, and the reviewer is right that early gains can fade. We have extended cycling to 1,500 cycles for a representative subset of cells (new Figure 6); the retention advantage persists (89% at 1,500 cycles). We note that 1,000 cycles is the standard endurance benchmark in this subfield (e.g., refs. 9, 16), so we have retained it as the primary metric while adding the 1,500-cycle data as supporting evidence. Behavior beyond 1,500 cycles remains an open question, which we now state explicitly as a limitation (Discussion, para. 5, p. 12).

Why it's better: Walk the same three comments. To Comment 1, instead of "you didn't read it," Lena concedes the writing was unclear (her fault, not the reviewer's) and shows the exact rewrite — disarming the criticism by acting on it. To Comment 2, instead of "out of scope," she does the experiment and thanks the reviewer for improving the paper; the comparison that felt like an attack becomes a new figure that strengthens her case. To Comment 3 — the one place she actually holds her ground — she first concedes the concern is fair and adds 1,500-cycle data, and only then defends her primary metric, with citations showing it's the field standard, and even adds a limitation. That's the pattern: concede first and visibly, defend second and narrowly, and back the defense with evidence rather than irritation. A reviewer reading this feels heard and sees the paper improved by their input — which is the reviewer who flips to "accept."

Notice that the firm response (Comment 3) is more persuasive precisely because it sits next to two genuine concessions. Lena gave ground on the writing and ran a new experiment, so when she holds the line on the cycle count, Reviewer 2 reads it as "this author concedes when they're wrong, so they probably have a reason here" — not as reflexive defensiveness. That's Chapter 14's principle made operational: conceding valid points buys credibility for the points you defend.

🚪 Threshold Concept. Publishing is a negotiation with named humans, not a verdict from an impartial standard. Before you cross this, the editor and reviewers feel like an exam board grading a fixed answer, and a critical review feels like a failing mark to argue against. After, you see the truth: the reviewers are collaborators-by-friction whose buy-in you are negotiating, the editor is a person you are persuading, and the cover letter and response letter are moves in that negotiation — not paperwork around the "real" science. The same result, packaged and defended by someone who understands the negotiation, gets published; packaged and defended by someone who thinks the science should speak for itself, gets rejected. The science is necessary. It was never sufficient.

🔄 Check Your Understanding. A reviewer asks for an experiment you genuinely cannot run — the specialized cell-cycling rig you used has been decommissioned. Chapter 14 had you walk through this; now apply the response-letter mechanics. Write the skeleton of your response to this comment.

Answer

Skeleton: (1) Quote the comment in full and respond beneath it — don't bury or skip it. (2) Concede the request is reasonable: "The reviewer is right that this experiment would strengthen the causal claim." (3) Explain the genuine constraint honestly: "Unfortunately the cycling rig used for this study was decommissioned in [month], and we no longer have access to an equivalent instrument." (4) Offer the best available alternative — a partial analysis with existing data, a citation to prior work that supplies the missing control, or an explicit new limitation in the Discussion. (5) State exactly what you added: "We have added a limitation noting this (Discussion, para. 6)." What you must not do: silently ignore it, or dismiss it as "out of scope" without explanation — both read as evasion to the person deciding your paper's fate. Editors are reasonable about real constraints when you're transparent; they turn hostile at evasion.

35.8 Writing for Different Journal Audiences

One more convention deserves its own section, because it determines everything else: a paper written for Science and the same paper written for a specialist journal are different documents. This is Theme #2 at the level of the whole manuscript, not just the sentence.

A broad/multidisciplinary journal (Nature, Science, PNAS, PLOS Biology) is read by scientists outside your field. They will not know your subfield's jargon, won't care about incremental method refinements, and need the significance spelled out in terms a chemist and a geologist can both grasp. Writing for them means:

• A jargon budget close to zero. Define or avoid every specialist term. (This is Chapter 28's science-communication discipline applied to a technical audience that simply isn't your technical audience.)
• Significance up front and broad. The first paragraph must answer "why does this matter to science generally?" — not "why does this matter to people who study sulfide electrolytes?"
• Method detail pushed to the supplement. The main text carries the story; the SI carries the recipe.
• Brevity. These journals enforce hard, short length limits precisely because their readers are non-specialists.

A specialist journal (a dedicated electrochemistry or materials journal) is read by people who do exactly what you do. Writing for them means:

• Field jargon is fine and even expected — using the shared vocabulary correctly signals membership (Chapter 3: jargon helps a shared audience).
• Significance is within-field. You argue the advance against the specific prior work, not against "science."
• Method detail belongs in the main text, because your readers will reproduce it and want it where they can see it.
• More room for nuance, secondary results, and careful qualification.

❌ Opening for a broad journal that reads like a specialist one: "We report that a Li₆PS₅Cl argyrodite electrolyte suppresses dendrite nucleation at the anode interface, maintaining Coulombic efficiency above 99.7% across 1,000 galvanostatic cycles at 2 mA/cm²." ✅ The same finding opened for a broad journal: "Batteries that store more energy and charge faster are limited by a stubborn failure: the liquid inside them is flammable, and solid replacements tend to crack and short-circuit. We report a solid material that resists this failure even under fast charging, retaining 91% of its capacity after 1,000 charge cycles." Why it's better (for that audience): The first version is correct and would be perfect in a specialist journal — but a broad journal's readers don't know "argyrodite," "Coulombic efficiency," or "galvanostatic," so the sentence is opaque to them and the significance is invisible. The second trades precision for reach deliberately, because the audience changed. Note the trade is audience-appropriate, not dumbing-down: in the specialist journal, the second version would read as condescending and under-informative. Same result, two audiences, two documents — exactly the judgment this whole book trains.

This is why Chapter 14's advice — choose your venue before you write — matters so much: the venue isn't a destination you ship the finished paper to, it's a decision that shapes the paper from the first sentence.

🔄 Check Your Understanding. You have one result. A broad journal and a specialist journal both might take it. Name three concrete things that change in the manuscript itself depending on which you choose — not in the cover letter, in the paper.

Answer

Any three of: (1) Jargon level — near-zero and defined for the broad journal, full field vocabulary for the specialist. (2) Where Methods detail lives — supplement for broad, main text for specialist. (3) How significance is framed — broad importance ("why science cares") versus within-field advance ("why this beats refs. 12, 14"). (4) Length — shorter and tighter for the broad journal's hard limits. (5) The opening sentence — a wide, accessible hook versus a precise field-specific claim. (6) How much nuance and secondary results you include — trimmed for broad, fuller for specialist. The deeper point: it's not the same paper submitted to two places — it's two papers built from one result, because the audience differs.

📐 Project Checkpoint

Your Communication Portfolio's first piece was the technical report from Chapter 13, which grew into the research-paper thinking of Chapter 14. This chapter doesn't add a new piece — it hardens the academic piece you already have into something submission-ready, by adding the apparatus that surrounds a real submission.

This chapter's addition — the submission packet. Take the report-or-paper draft already in your portfolio (or, if you're not in a research field, a substantial analytical document you've written) and build the three things a real submission requires around it:

1. A statistics audit. Find every quantitative claim in the document. For each, check it against §35.2: is there a test statistic with degrees of freedom, an exact p-value (no leading zero), and an effect size? Rewrite any claim that fails — especially any sentence that says "significant" or "better" without a number behind it. Even if your document isn't statistical, audit it for vague quantitative claims ("substantially faster," "much higher") and replace them with figures and uncertainty.

2. A cover letter (≈250 words). Write the letter to the editor (or, for a non-research document, the cover note to the decision-maker) using the §35.6 four-part move: specific contribution with the headline number, the significance case for this venue, the housekeeping, and — for a journal — suggested reviewers. Aim it at one named reader.

3. A contribution and availability note. Write a one-line author-contribution statement (use CRediT roles even for a solo document — it clarifies your own scope) and a one-line data-/material-availability statement saying where the underlying data or materials can be found.

Self-review before you file it: read the cover letter as the editor — does it tell you the result and why it fits this journal, or does it just restate the title? Read the statistics as a hostile reviewer — can you check every number, or are some just asserted? File all three with your portfolio piece.

Next increment: Chapter 37 will turn an analytical finding into an executive summary and a one-page brief for a non-technical decision-maker — the same result compressed for the opposite end of the audience spectrum from the specialist reviewer you wrote for here.

35.9 Common Mistakes & Practical Considerations

The conventions in this chapter fail in predictable ways. These are the ones that get good science rejected, delayed, or quietly distrusted.

Treating the cover letter and response letter as formalities. They are the two highest-leverage documents in the whole process — the cover letter decides whether you reach review, the response letter decides whether review ends in acceptance — and researchers routinely dash them off. Spend real writing time on both.

Reporting "significant" without a number. The most common Results-section weakness. "Significantly higher" is not a result; M = 91.2% vs. 78.4%, t(38) = 9.4, p < .001, d = 2.1 is a result. If a sentence claims a difference, it must report the difference.

The leading-zero error and other formatting tells. p < 0.05 (should be p < .05), un-italicized statistics, F with its degrees of freedom reversed, four-decimal p-values pasted from software. Individually trivial; collectively they tell a reviewer you haven't done this before, which colors how charitably they read everything else.

Using the supplement to hide rather than support. Moving an inconvenient result or a key limitation into the SI to keep the main text clean is a small dishonesty reviewers are trained to catch. If it bears on the claim, it goes where the claim is.

Writing one "science voice" for every venue. A specialist-journal manuscript submitted to Nature (dense with jargon, significance framed within-field) gets desk-rejected; a broad-journal manuscript submitted to a specialist journal (everything defined, method in the SI) reads as condescending and thin. Match the venue, and the field's actual voice, by reading recent papers in it.

Defending everything in the response letter. The single most expensive habit. An author who fights every comment signals they can't tell good criticism from bad, so reviewers distrust even the legitimate rebuttals. Concede freely; defend narrowly.

Mismanaging authorship. Adding a guest author for prestige, omitting a contributor, or surfacing the author-order argument at submission. Settle roles early, in writing, against the ICMJE bar; use the contribution statement as the forcing function.

Posting a preprint without checking the journal's policy — or without labeling it. Most journals allow preprints now, but a few don't; check before you post, and always banner the preprint as not-yet-peer-reviewed.

Decision framework — which convention governs?

Frequently Asked Questions

Should I use active or passive voice in my scientific paper?

It depends on your field and section, not on a universal rule. Chemistry and many physical sciences still favor the passive in Methods ("the sample was heated"); molecular and cell biology increasingly favor the active first-person ("we treated the cells"), and several major biology journals explicitly encourage it. The reliable method: read three recent papers in your exact target journal and match their Methods voice. In nearly every field, use the active voice for your own reasoning and choices (Introduction, Discussion) even if Methods stay passive — and be consistent within the paper.

How do I report a p-value correctly?

Report the exact value to two or three decimals (p = .03, p = .024), not just "p < .05," except for very small values where p < .001 is standard. In APA-descended style, italicize p, use a lowercase letter, and omit the leading zero (p = .03, never 0.03) because a probability can't exceed 1. Always pair the p-value with the test statistic and its degrees of freedom (t(38) = 9.4) and an effect size (Cohen's d, η², r). A p-value alone tells the reader an effect is detectable, not whether it's large enough to matter.

What's the difference between a preprint and open access?

A preprint is about timing: a complete manuscript posted publicly (on arXiv, bioRxiv, ChemRxiv, etc.) before or during peer review, so the work is readable and citable early — but it is explicitly not peer-reviewed. Open access is about the published version: whether the final, peer-reviewed article is free to read (gold OA, where the author pays an article-processing charge; green OA, where the author self-archives a copy for free) or sits behind a subscription paywall. You can do both: post a preprint and publish open access.

What should go in supplementary materials versus the main paper?

The main text gets what the argument needs to stand: the key results, the figures a reader must see, the main statistical tests, and the method detail needed to understand what you did. The supplement gets what a skeptic needs to verify it: full datasets, every replicate, exhaustive protocol detail, robustness checks, and confirmatory figures. Two rules: never move an inconvenient result or a real limitation into the supplement to keep the paper clean (that's hiding, not supporting), and write the supplement as carefully as the paper — every supplementary figure needs a stand-alone caption and an S-prefixed callout in the main text.

How do I respond to harsh peer-review comments without sounding defensive?

Address every comment; concede what's right, gladly and first; and disagree only with evidence, never with attitude. Quote each comment in full, respond beneath it, and state exactly what you changed and where (section, figure, page). Conceding valid points early buys credibility for the few points you defend — an author who fights everything is distrusted even when right. Where you must hold firm, concede the underlying concern first, then defend narrowly with citations or new data, and offer an alternative or a limitation rather than a flat "no." A "major revision" is an offer to publish; the response letter is how you accept it.

Chapter Summary

Key Takeaways - There is no single "science voice." Conventions are local — passive in chemistry, increasingly active in biology — and you learn yours by reading recent papers in your target journal, not from a rule. - Report statistics so a skeptic can check you: test statistic with degrees of freedom, exact p-value (no leading zero, lowercase italic p), and an effect size. "Significant" without a number is not a result. - The supplement holds what a replicator needs; the main text holds what the argument needs. Never use the supplement to hide an inconvenient result. - Modern publishing adds a preprint (public, early, unreviewed — about timing) and open access (free to read — about the published version); know your funder's mandate and your journal's policy. - Author-contribution statements (often CRediT) and the ICMJE bar make credit precise and authorship accountable. Settle authorship early, in writing. - The cover letter gets you past the editor's desk; the response letter gets you past the reviewers. Both are persuasive writing aimed at one named reader — treat them as the high-leverage documents they are.

Action Items - Before writing, pull three recent papers from your target journal and note their voice, statistical-reporting style, and what they put in the SI. - Audit every quantitative claim in your draft against the §35.2 checklist; rewrite any "significant"/"better" sentence that lacks a number and an effect size. - Write the cover letter to a named editor, leading with your headline result and the significance case for that journal. - Draft the author-contribution statement and a data-availability statement before submission, not after. - When reviews arrive, sleep on the harsh ones; then write a response that concedes first, defends narrowly, and documents every change.

Common Mistakes - Dashing off the cover letter and response letter as formalities. - "Significant" with no number; the p < 0.05 leading-zero error and other formatting tells. - A one-size "science voice" submitted to the wrong kind of venue. - Hiding awkward results in the supplement; posting an unlabeled preprint without checking journal policy. - Defending every reviewer comment instead of conceding freely and defending narrowly.

Decision Framework

Spaced Review

A few questions reaching back, to strengthen retention.

1. (From Chapter 13) Chapter 13's threshold concept was that Results and Discussion are "two different cognitive acts kept in separate rooms." How does this chapter's rule about where statistics go and what belongs in the supplement extend that same separate-rooms discipline?
2. (From Chapter 7) Chapter 7 taught the linguistics of hedging — "may suggest" versus "proves." How does that skill show up in this chapter's effect-size discussion and in the response letter, where you must calibrate how strongly you claim and how firmly you disagree?
3. (From Chapter 14, bridging) Chapter 14 called a "major revision" a victory and gave you three rules for responding to reviewers. This chapter built the whole response letter. What did Chapter 14 give you (the principles) versus what this chapter added (the mechanics) — and why do you need both?

What's Next

Chapter 35 lived at one extreme of the audience spectrum: you wrote for the most expert, most adversarial reader your work will ever meet — a specialist reviewer with a red pen and a grudge. Chapter 36 swings to the highest-stakes audience of all and a different kind of expert convention: writing for medicine and healthcare, where a clinical note's reader is another clinician acting on it under time pressure, a patient-facing instruction's reader may be frightened and unwell, and — unlike a battery cell — a misread sentence can hurt someone. The principle that has run through this whole Part holds there too: same skills, local conventions, and an audience you must respect enough to study. The conventions just matter more when the stakes are a life.

Practice: Exercises · Quiz Go deeper: Case Study · Case Study 2 Review: Key Takeaways · Further Reading