What Editors Actually Read in Your Response to Reviewers.

Editors read a response to reviewers in two passes, and the first one is a triage, not a read. They check that every comment has a reply, that the tone stays civil, and that a handful of claims match what actually changed in the manuscript. Clear that first pass and the editor reads the rest as confirmation; fail it and they read the rest looking for reasons to send the paper back.

Most authors write the response as if the editor will study it word by word. They will not, at least not on the first opening. Understanding the skim is how you write a document that survives it.

How long do editors spend on a response before they read it closely?

Less time than you spent writing it. The first pass is a fast decision about how much of the revision to re-read and whether to involve reviewers again, and it happens before any close reading of your replies.

A handling editor opens the response with two questions in mind: did the authors do the work, and can I move this forward without a full re-review. They answer both by skimming. So the shape of the document does more work than any single sentence in it. A response that forces the editor to hunt for the answer to comment 7, or to cross-reference three files to see whether an analysis was actually run, spends their patience before they reach your strongest reply. The response letter is their reading guide, and a guide that is hard to skim is a guide that gets abandoned.

What do editors check first?

Completeness and tone. They scan for a reply under every comment, and they read the register of a few replies to gauge whether the exchange stayed professional.

Completeness is the faster check and the one that fails most often. Reviewer comments hide sub-questions inside long paragraphs, and a response that answers the first sentence of a comment while ignoring the clause at the end reads as evasive, even when the omission was an accident. An editor who spots one unanswered point starts wondering how many others are buried. The fix is mechanical: split every comment into its separate asks before you reply, and answer each one on the record.

Tone is checked by sampling. Editors do not read all forty replies for civility on the first pass; they read the ones attached to the sharpest reviewer comments, because that is where authors lose composure. A reply that argues with the reviewer's competence, or apologizes six times for a single typo, tells the editor something about how the rest of the file will read. Confident and plain is the register that clears this check. You are reporting completed work to a colleague, not pleading a case.

What makes an editor trust a revision without rereading everything?

Replies specific enough to verify, each anchored to a location, backed by spot checks that hold. When a claim in the letter matches what the editor finds at the page and line you named, they extend that trust to the claims they did not check.

This is the mechanism behind the whole triage. The editor picks two or three of your replies, usually the ones tied to the most important comments, and opens the manuscript to see whether the change is really there and really does what you say. "We have revised the discussion" gives them nothing to verify. "The new paragraph appears in Section 4.1, page 14, lines 402 to 415" gives them an address, and when the address is correct, the next unverified reply inherits its credibility. Anchoring every reply to a location is what lets the editor stop checking.

The reverse also holds. One spot check that fails, a line number pointing to the wrong paragraph, a claimed reanalysis that is not in the file, and the editor stops trusting the summary and starts reading everything. At that point you have turned a skim into an audit.

What red flags trigger another review round?

Missing replies, cosmetic edits dressed up as substantive ones, defensiveness on a central criticism, and any gap between what the letter claims and what the manuscript shows. Each one moves the editor from deciding for themselves toward sending the paper back to reviewers.

The most damaging red flag is the mismatch. If your summary says the main analysis was rerun with a new covariate and the results section still shows the old numbers, the editor cannot resolve that alone, and the safest move is to return the file to the reviewer who raised it. Defensiveness triggers the same reflex for a different reason: when an author refuses a central point without evidence, the editor wants a second opinion on whether the refusal is defensible. You are allowed to decline a comment, but declining it well means answering with data and offering something in return, not restating your original position louder.

Whether a red flag sends the paper back at all depends partly on the decision you received. The distinction between a major and a minor revision shapes how much latitude the editor has to decide without the reviewers, and how much a weak response costs you.

How do you write a response for the skim?

Structure it so the answers are impossible to miss: quote each comment, put your reply directly beneath it, and lead every reply with a plain verdict before the explanation. Signpost the major changes in one paragraph at the top so the editor knows the shape of the revision before they scroll.

Three habits carry most of the weight. First, follow the point-by-point format that editors already know how to scan: comment quoted verbatim, numbered, reply set off visually beneath it. Second, open each reply with the verdict, "We agree and have," "We have added," "We disagree, and here is why," so a skimming editor gets your stance in the first three words. Third, put a summary paragraph at the very top that names only the changes affecting the paper as a whole, because that paragraph is often the only prose the editor reads in full.

One check remains, and revisions fail it constantly: the revised manuscript still has to obey the journal's own formatting rules, which the edits you just made can quietly break. An abstract grows past its cap, a new citation knocks the reference list out of style, a moved figure loses its callout. That final read of the manuscript against the journal's rule set is the one Waraq automates, returning each fix as a tracked change with the rule it enforces. Clear it, and the editor's spot checks find a clean file behind a clean letter, which is the whole point of writing for the skim.