jpart-rebuttal

R&R Rebuttal (jpart-rebuttal)

A JPART R&R is the normal path to publication, and its reviews are detailed and developmental —

they report perceived strengths/weaknesses, the basis for the decision, and advice on how to proceed.

Treat the reviews as a roadmap. The response letter must move every reviewer toward yes while keeping

the editor confident the public-management theory contribution survives the revision.

When to trigger

• An R&R decision arrived and you are planning the revision + response letter
• Reviewers disagree with each other and you must reconcile their demands
• A reviewer requests analyses that would change the paper's claims
• Writing the cover note to the editor summarizing the revision

Strategy

1. Read the editor's letter as the rubric. The editor signals which points are decisive (often the

theoretical contribution and the identification/common-method threat). Solve those first.

1. One point-by-point response, every comment addressed. Quote each comment, then respond. Never

skip one — silence reads as non-compliance.

1. Concede or rebut explicitly, with evidence. For each: did what was asked (say where, with the new

text/table number), or push back respectfully with a reason (theory, design, or evidence).

Developmental reviewers respect a well-argued disagreement over a hollow capitulation.

1. Reconcile conflicting reviewers openly. When R2 wants the opposite of R3, say so, choose a

principled path, and explain the tradeoff to the editor.

1. Protect the theory contribution. Add robustness and clarifications; resist changes that turn the

paper into a policy report or strip the mechanism. Defend scope conditions rather than over-claiming.

1. Update the public package. Re-verify the data and code so every new table/figure re-runs, and

keep the Data Availability Statement current (see jpart-transparency-and-data); keep the revised

manuscript double-blind.

Triage table for a JPART R&R

| Comment signal | Who owns the call | Default move in the response |

|----------------|-------------------|------------------------------|

| Editor flags it as decisive | editor | solve first, headline it in the cover note |

| "This is atheoretical / no mechanism" | author + editor | strengthen the theory move; make the mechanism observable |

| "This is common-method bias / selection" | author | add a separate-source/sensitivity analysis; report honestly |

| Two reviewers want opposite things | editor | pick a principled path, explain the tradeoff openly |

| Reviewer asks for an analysis that would change the claim | author + editor | run it, then defend or re-scope the contribution honestly |

| Reviewer wants the result generalized beyond design | author | add scope conditions; resist over-claiming |

Response-letter format

For each reviewer comment:

> [Quoted reviewer comment]

Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].

Open with a short summary of the main changes to the editor; group by reviewer; end each entry with

the location of every change so the editor can verify quickly.

Worked micro-example (illustrative)

A hypothetical R&R on a representative-bureaucracy survey experiment draws three reviews. The editor's

letter names two decisive points (the mechanism for passive→active representation, and a common-method

concern). R2 wants the formal framing cut; R3 wants it expanded. The disciplined letter opens

with a three-sentence summary to the editor, addresses the mechanism and common-method points first with

new text/table locations (adding a separate-source outcome and a sensitivity analysis), then reconciles

R2/R3 by **keeping a compact theory section in the main text and moving the extended derivation to the

supplement — stating the tradeoff explicitly. Of 27 comments, 27** receive a quoted response;

19 are conceded with a change location, 8 are rebutted with a reason. (Counts illustrative.)

Referee-pushback patterns and the JPART repair

• "The revision turned the paper into a policy report." → Restore the theory framing; lead the

discussion with implications for public-management theory, not just for practice.

• "New tables don't match the deposited package." → Re-run the public data-and-code so every revised

exhibit reproduces; update the Data Availability Statement.

• "You ignored a comment." → Silence reads as non-compliance; quote and answer every one, even to say

why you respectfully disagree.

• "Capitulation weakened the mechanism." → A well-argued disagreement is respected more than a hollow

concession; defend the scope conditions that carry the contribution.

Calibration anchors (hedged)

• Treat the editor's letter as the rubric; JPART decisions rest on the editors' read of detailed,

developmental reviews.

• The decisive axis is usually the **theory contribution + the PA-specific threat (common-method,

selection)** — answer both head-on.

• Exact decision-category language and review mechanics can change — confirm against the journal's current

author guidelines before quoting them in the letter.

Output format

【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Theory contribution protected】no drift into policy report? [Y/N]
【Anonymity + public package updated】[Y/N]
【Next】resubmit via Editorial Express

Supplementary resources

• [../../resources/official-source-map.md](../../resources/official-source-map.md) — decision process, developmental-review description