Revision & Rebuttal (jcr-rebuttal)
When to trigger
- You received a JCR R&R and need a plan plus a response letter
- Reviewers want additional studies, process evidence, or analyses
- You must satisfy data/materials posting now required at invited revision
- You are reconciling conflicting reviewer requests across disciplines
Revise first, write the letter second
A JCR response letter documents revisions that already exist. Sequence the work:
- Triage by the editor's priorities. The co-editor's letter signals which concerns are decisive — fix those substantively, not cosmetically.
- Strengthen the conceptual contribution. If reviewers found it incremental, sharpen the advance/deepen/repudiate claim (
jcr-contribution-framing) — re-running studies will not save a thin contribution.
- Add the evidence the genre demands. Experiments: new studies for process (manipulated mediator, predicted moderators), replications across stimuli/populations, cleaner inference (
jcr-data-analysis). CCT: deeper grounding, additional informants, a tighter audit trail.
- Reconcile conflicts transparently. Where reviewers disagree, choose a defensible path, explain the reasoning, and let the editor adjudicate — do not silently split the difference.
Satisfy the transparency requirements that activate at revision
At invited revision, JCR's transparency regime tightens: posting of data and study materials to an approved repository (OSF, Harvard Dataverse, Qualitative Data Repository, ResearchBox) becomes required (accessible to editors) unless an exemption is granted, and replication code must be provided. Update the Data Collection Statement to cover any new studies. Confirm your data-retention plan (≥ 7 years). Address any transparency reviewer concerns explicitly in the letter.
New-study economy
Do not answer every concern with another study. Use this triage:
| Reviewer concern |
Strong response |
Weak response |
| Mechanism/process unclear |
A targeted mediator, moderator, process measure, or qualitative trace that discriminates the proposed mechanism from rivals |
A broad extra study that repeats the main effect |
| Generalizability challenged |
A sample, stimulus, context, or cultural setting that tests the stated boundary |
A convenience replication with no new boundary information |
| CCT grounding challenged |
More field evidence, negative cases, informant variation, or audit-trail clarity |
Extra quotation volume without interpretive leverage |
| Transparency challenged |
Repository deposit, code, materials, and a revised Data Collection Statement |
A promise that materials will be available later |
Cap the revision plan at the smallest set of changes that resolves the editor's decisive doubts. If a new study does not change the conceptual conclusion, use a robustness appendix or drop it.
Writing the point-by-point response
- Open with a brief summary of the major changes and gratitude for the developmental feedback.
- Address every comment in order, per reviewer: quote the comment, state what you changed, and point to the manuscript location (page/section, new study number, new exhibit).
- Show, don't assert. Reference new results, new figures, and repository links rather than promising compliance.
- Keep anonymization intact. The revised manuscript re-enters double-anonymized review — re-scrub identifiers, keep self-citations neutral, describe field sites generically.
- Respect the page cap. New studies must fit the 60-page manuscript (embedded exhibits count); push supporting material to the web appendix (≤ 40 MB).
Checklist
Anti-patterns
- Promising changes in the letter that the manuscript does not contain.
- Cosmetic edits to decisive concerns.
- Adding studies that bloat the manuscript past the page cap.
- Ignoring transparency requirements that become mandatory at revision.
- Breaking anonymization when describing new data or sites.
- Treating every reviewer request as a demand for a full new study, then losing the conceptual thread.
Output format
【Editor's priorities】addressed: [...]
【Contribution】sharpened? advance/deepen/repudiate restated
【New evidence】studies/analyses (experiments) or grounding (CCT) added
【Conflicts】reconciled with reasoning
【Transparency】repository deposit + code + updated Data Collection Statement: done?
【Response letter】point-by-point, with locations; re-anonymized; ≤60 pp
【Next step】resubmit via ScholarOne → jcr-review-process
1---2name: jcr-rebuttal3description: Use when responding to a Journal of Consumer Research (JCR) revise-and-resubmit — planning the revision, running new studies or analyses, satisfying the transparency requirements that become mandatory at invited revision, and drafting a point-by-point response letter for double-anonymized re-review. Drafts the response after the revision is real; it does not interpret the decision (jcr-review-process).4---56# Revision & Rebuttal (jcr-rebuttal)78## When to trigger910- You received a JCR R&R and need a plan plus a response letter11- Reviewers want additional studies, process evidence, or analyses12- You must satisfy data/materials posting now required at invited revision13- You are reconciling conflicting reviewer requests across disciplines1415## Revise first, write the letter second1617A JCR response letter documents revisions that already exist. Sequence the work:18191. **Triage by the editor's priorities.** The co-editor's letter signals which concerns are decisive — fix those substantively, not cosmetically.202. **Strengthen the conceptual contribution.** If reviewers found it incremental, sharpen the advance/deepen/repudiate claim (`jcr-contribution-framing`) — re-running studies will not save a thin contribution.213. **Add the evidence the genre demands.** Experiments: new studies for **process** (manipulated mediator, predicted moderators), replications across stimuli/populations, cleaner inference (`jcr-data-analysis`). CCT: deeper grounding, additional informants, a tighter audit trail.224. **Reconcile conflicts transparently.** Where reviewers disagree, choose a defensible path, explain the reasoning, and let the editor adjudicate — do not silently split the difference.2324## Satisfy the transparency requirements that activate at revision2526At **invited revision**, JCR's transparency regime tightens: posting of **data and study materials to an approved repository** (OSF, Harvard Dataverse, Qualitative Data Repository, ResearchBox) becomes **required** (accessible to editors) unless an exemption is granted, and **replication code** must be provided. Update the **Data Collection Statement** to cover any new studies. Confirm your data-retention plan (**≥ 7 years**). Address any transparency reviewer concerns explicitly in the letter.2728## New-study economy2930Do not answer every concern with another study. Use this triage:3132| Reviewer concern | Strong response | Weak response |33| --- | --- | --- |34| Mechanism/process unclear | A targeted mediator, moderator, process measure, or qualitative trace that discriminates the proposed mechanism from rivals | A broad extra study that repeats the main effect |35| Generalizability challenged | A sample, stimulus, context, or cultural setting that tests the stated boundary | A convenience replication with no new boundary information |36| CCT grounding challenged | More field evidence, negative cases, informant variation, or audit-trail clarity | Extra quotation volume without interpretive leverage |37| Transparency challenged | Repository deposit, code, materials, and a revised Data Collection Statement | A promise that materials will be available later |3839Cap the revision plan at the smallest set of changes that resolves the editor's decisive doubts. If a new study does not change the conceptual conclusion, use a robustness appendix or drop it.4041## Writing the point-by-point response4243- **Open** with a brief summary of the major changes and gratitude for the developmental feedback.44- **Address every comment** in order, per reviewer: quote the comment, state what you changed, and point to the manuscript location (page/section, new study number, new exhibit).45- **Show, don't assert.** Reference new results, new figures, and repository links rather than promising compliance.46- **Keep anonymization intact.** The revised manuscript re-enters **double-anonymized** review — re-scrub identifiers, keep self-citations neutral, describe field sites generically.47- **Respect the page cap.** New studies must fit the **60-page** manuscript (embedded exhibits count); push supporting material to the **web appendix (≤ 40 MB)**.4849## Checklist5051- [ ] Editor's decisive concerns addressed substantively52- [ ] Contribution sharpened if flagged as incremental53- [ ] New process evidence / replications (experiments) or deeper grounding (CCT) added54- [ ] Conflicting reviewer requests reconciled with transparent reasoning55- [ ] Data/materials posted to an approved repository; replication code supplied; Data Collection Statement updated56- [ ] New-study economy checked: each new study resolves a specific decisive doubt57- [ ] Point-by-point letter quotes each comment and cites manuscript locations58- [ ] Revised manuscript re-anonymized; within 60 pages; overflow in the web appendix5960## Anti-patterns6162- Promising changes in the letter that the manuscript does not contain.63- Cosmetic edits to decisive concerns.64- Adding studies that bloat the manuscript past the page cap.65- Ignoring transparency requirements that become mandatory at revision.66- Breaking anonymization when describing new data or sites.67- Treating every reviewer request as a demand for a full new study, then losing the conceptual thread.6869## Output format7071```72【Editor's priorities】addressed: [...]73【Contribution】sharpened? advance/deepen/repudiate restated74【New evidence】studies/analyses (experiments) or grounding (CCT) added75【Conflicts】reconciled with reasoning76【Transparency】repository deposit + code + updated Data Collection Statement: done?77【Response letter】point-by-point, with locations; re-anonymized; ≤60 pp78【Next step】resubmit via ScholarOne → jcr-review-process79```
brycewang-stanford