The Point-by-Point Response Format Editors Expect, With a Template.

A point-by-point response is a document in which every reviewer comment appears verbatim, numbered, with your reply directly beneath it. Each reply states what you changed and where the change sits in the revised manuscript, down to page and line numbers. The format exists so an editor can confirm in a single pass that no comment was skipped.

That single pass is the whole game. Editors handling dozens of revisions do not study response documents; they scan them for coverage and completeness, and the formatting either makes that scan effortless or makes it a slog.

Why do editors prefer point-by-point over narrative responses?

Because they read your response to verify, not to be persuaded. A numbered document lets the editor tick off comments one by one; a narrative summary forces them to reconstruct the mapping themselves.

Picture the alternative from the editor's chair. Two reviewers raised nineteen comments between them, and the authors returned three paragraphs beginning "we have substantially revised the manuscript in light of the helpful feedback." Now the editor must hold all nineteen comments in mind while hunting through the prose for evidence that each one was addressed. Any comment they cannot match to a sentence reads as ignored, whether it was or not. After a major revision, where the response often goes back to the original reviewers, the same problem repeats twice more.

The numbered format removes the hunt. It also protects you: a comment you handled well but buried in a paragraph earns you nothing.

What goes in each response unit?

Four elements, in a fixed order: the comment quoted verbatim, your response, the change you made, and its location in the revised file.

Quote the comment exactly as written, typos and all. Paraphrasing saves no one any time, and a reviewer who finds their criticism reworded into something milder will assume the softening was deliberate. When one comment hides three questions, split it into sub-points, but keep every fragment word for word.

The response itself says whether you agree, partly agree, or decline, and why. Most replies are short: you agreed and made the change. The rare decline needs evidence and a concession in the text, and there is a craft to disagreeing with a reviewer politely without souring the file.

State the change in the past tense. "We added the missing covariate and reran the analysis" is a completed action; "we will consider this in future work" is a deferral, and editors read it as one. Then give the address: section, page, and line range in the revision, plus which copy the numbers refer to if you submit both a clean and a tracked-changes version.

How do you number comments from multiple reviewers?

Prefix each number with its reviewer: R1.1, R1.2, R2.1, and so on. Editor comments get their own prefix, usually E1 onward.

Never impose your own ordering. If Reviewer 2 numbered their comments, keep those numbers even when they misnumbered something, and note the discrepancy rather than silently fixing it. If a reviewer opened with a paragraph of general remarks before the itemized list, treat that paragraph as its own entry, labeled R2.0 or "General comment," and answer it too. Unnumbered prose reviews are yours to segment: split them at each distinct request and number the pieces in reading order.

Sub-parts take letters, so a two-part comment becomes R1.4a and R1.4b. The scheme matters less than its stability. A response document that calls the same comment "3" in the summary letter and "R2.3" in the annex sends the editor back to counting.

How do you keep the document scannable?

Pick one visual convention for comments and a different one for replies, then apply it without a single exception. The standard pairing is the comment in italics or an indented block, the reply in plain type beneath it.

Labels help when replies have several parts: a short "Response:", "Change:", and "Location:" at the start of each element lets the editor jump straight to the part they need. Avoid distinguishing comment from reply by color alone, since the distinction can vanish in a grayscale print or an accessibility reader. And check the author guidelines before you format anything. Some journals supply their own response template, and theirs wins.

Whitespace is not decoration here. A blank line between units, and a page break before each new reviewer, turn a forty-item document into something an editor can navigate by thumb.

A template you can adapt to any journal

The skeleton below covers the conventions above. Replace the bracketed slots, delete what a given journal's template already provides, and keep the numbering scheme from the first page to the last.

RESPONSE TO REVIEWERS
Manuscript ID: [ID]   Title: [short title]

Reviewer comments appear in italics, numbered R1.1, R2.1, and so on.
All page and line numbers refer to the clean copy of the revision.

REVIEWER 1

R1.1  [Comment, quoted verbatim.]

  Response:  [Agree / partly agree / decline, with reasons.]
  Change:    [What was changed, stated in the past tense.]
  Location:  Section [x], page [x], lines [x] to [x].

R1.2  [Next comment.]
  ...

REVIEWER 2

R2.1  [Comment.]
  ...

Which formatting mistakes irritate editors?

The ones that force rereading. Paraphrased comments top the list, followed by replies that state a change but never say where it landed.

A few others recur in almost every editor's complaints. Thanking the reviewer for their "insightful comment" before all nineteen replies pads the document without warming anyone. Merging two comments into one reply leaves the editor unsure which half was answered. Line numbers copied from an earlier draft point at the wrong text, which tells the editor the authors never checked their own map; lock the manuscript first, then verify every location against the final PDF. Inconsistent numbering between the cover letter and the annex has the same effect. None of these mistakes sink a sound revision on their own. Together they signal carelessness, and carelessness is exactly what the reviewers were checking for.

One quieter failure sits outside the response document. The revision itself must still meet the journal's formatting rules, and revisions break them silently: a rewritten abstract drifts past its word cap, a new reference knocks the list out of style. Waraq runs that final check against the journal's own rule set and returns each fix as a tracked change in Word.

The point-by-point annex is the engine of the resubmission, but it travels inside a short letter to the editor, with its own greeting and a one-paragraph summary of the major changes. How to write that wrapper, and a worked example of the whole package, is covered in our guide to the response to reviewers letter. Format the annex so it can be scanned in two minutes. That is the standard the editor will apply, whether you met it or not.