JACC Response to Reviewers: A Clinical Revision Guide
A JACC revision guide for converting editor and reviewer concerns into clinical, statistical, visual, and manuscript-level evidence.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
How to use this page well
These pages work best when they behave like tools, not essays. Use the quick structure first, then apply it to the exact journal and manuscript situation.
Question | What to do |
|---|---|
Use this page for | Building a point-by-point response that is easy for reviewers and editors to trust. |
Start with | State the reviewer concern clearly, then pair each response with the exact evidence or revision. |
Common mistake | Sounding defensive or abstract instead of specific about what changed. |
Best next step | Turn the response into a visible checklist or matrix before you finalize the letter. |
Quick answer: A JACC response to reviewers should make the editors' decision easier. Start with the controlling clinical and methodological issues, then answer every comment point by point. For each issue, state agreement or disagreement, describe the action, report what the new evidence shows, and quote or locate the exact change. Cite page and line, table, figure, endpoint analysis, supplement, Central Illustration, or Clinical Perspectives box. A polished letter cannot rescue a revision whose primary claim, statistics, visuals, and clinical interpretation still disagree.
Last reviewed: July 13, 2026.
Use the JACC revision readiness scan before uploading. Initial scope belongs to the JACC submission guide, status interpretation belongs to JACC under review, and the JACC journal profile provides venue context.
From our manuscript review practice
In JACC revisions we review, the most dangerous mismatch is a statistically expanded response that never makes the clinical consequence clearer. The editor still needs the endpoint, effect magnitude, uncertainty, safety, Central Illustration, and Clinical Perspectives to tell one decision-ready story.
What JACC editors need from the revision
JACC's published editorial guidance describes a useful response sequence: restate the issue, indicate agreement or disagreement, explain the response, and delineate the specific manuscript change. Current author materials also distinguish a Revision Required decision from acceptance. The revised submission can return to reviewers, while editors judge the whole package.
Translate that into a clinical evidence map:
Revision concern | Evidence the editor needs | Incomplete response |
|---|---|---|
Clinical importance | Absolute effect, uncertainty, population, comparator, and practice consequence | Repeating statistical significance |
Endpoint integrity | Protocol alignment, hierarchy, multiplicity, missingness, and sensitivity | Renaming a secondary result as primary |
Confounding or bias | Design rationale, adjustment, diagnostics, negative controls, or bounded inference | Adding covariates without explaining identification |
Safety | Denominators, exposure, severity, timing, adjudication, and competing risk | Reporting only frequent adverse events |
Generalizability | Enrollment, sites, exclusions, subgroup interaction, and external context | Listing demographics without testing transport |
Clinical communication | Abstract, Central Illustration, Clinical Perspectives, tables, and conclusion agree | Repairing only the response letter |
Copyable JACC response template
Put editor and reviewer text in bold or shaded blocks. Keep author responses in regular text. Use one location convention throughout.
Dear Editor-in-Chief and Associate Editor,
Thank you for inviting revision of manuscript JACC-2026-1842,
"Early Rhythm Control After Acute Heart Failure." Your decision identifies
three controlling issues: endpoint hierarchy, residual confounding, and the
clinical interpretation of the safety result. We address these first, then
respond to every editor and reviewer comment. Page and line references use
the clean revised manuscript; changes are visible in the marked copy.
Editor Issue 1: Endpoint hierarchy
Response: We agree that the original abstract overemphasized the secondary
hospitalization endpoint. We restored the prespecified primary composite as
the headline result, added the multiplicity plan, and report the secondary
endpoint as exploratory. See page 3, lines 8-24; page 10, lines 4-27; Table 2;
and revised Central Illustration.
Reviewer 1, Comment 3
"Residual confounding may explain the treatment association."
Response: We added inverse-probability weighting diagnostics, an E-value,
negative-control analysis, and a complete-case sensitivity analysis. The
estimate attenuates but remains directionally consistent. We now describe
the result as an adjusted association rather than a treatment effect. See
page 12, lines 2-31 and Supplemental Tables S5-S8.
Reviewer 2, Comment 5
"The safety conclusion is not supported by the event table."
Response: We agree. We rebuilt the safety table with treatment-exposure
denominators, severity, timing, and adjudication. The conclusion now states
that no excess was detected within the observed follow-up, not that the
strategy is proven safe. See page 15, lines 11-29 and Table 4.
Sincerely,
Dr. A. Researcher, on behalf of all authorsDo not write "all comments were addressed" as a substitute for an audit trail. The response should let an editor verify the action and its consequence without searching the entire manuscript.
Put page, line, endpoint, and artifact in every reply
The page-and-line citation is the minimum. A clinical revision should also name the endpoint, model, cohort, table, figure, or supplement. If the response changes the headline, identify every place where that headline appears: title, abstract, Central Illustration, Results, Clinical Perspectives, discussion, and conclusion.
Verify locations after final formatting. A page reference copied from the marked file may not match the clean file. State which version the coordinates use.
Typography for JACC revision letters
Keep each editor or reviewer comment visually distinct from the author response with bold text, a shaded block, or explicit labels and indentation. Do not rely on color alone. Use the same convention for editor priorities, Reviewer 1, Reviewer 2, statistical reviewer comments, and second-round text.
In the marked manuscript, make analytical and interpretive changes as visible as prose edits. A changed hazard-ratio label, denominator, or endpoint hierarchy can matter more than an added paragraph.
Build a clinical concern-to-change ledger
Before writing prose, create one shared ledger for the author team:
Comment | Underlying uncertainty | Analysis or artifact | Claim affected |
|---|---|---|---|
Primary endpoint unclear | Selective emphasis | Protocol cross-check, abstract, Table 2 | Efficacy headline |
Confounding remains | Causal validity | Weighting diagnostics, controls, sensitivity | Effect language |
Safety underreported | Clinical tradeoff | Exposure-adjusted event table | Benefit-risk conclusion |
Subgroup claim too strong | Heterogeneity | Interaction test and confidence interval | Population boundary |
Figure is not clinically legible | Decision communication | Central Illustration redesign | Practice relevance |
Disclosures differ | Trust and compliance | Author and funding reconciliation | Submission integrity |
If one new analysis narrows the claim, revise every high-salience artifact. Do not preserve a stronger abstract by burying the qualification in limitations.
Tone calibration for JACC responses
Avoid | Better |
|---|---|
"The reviewer misunderstands the endpoint." | "We agree the hierarchy was not legible. We now identify the prespecified primary endpoint in the abstract and Table 2 and label secondary analyses exploratory." |
"Residual confounding has been eliminated." | "The added diagnostics reduce several measured imbalances; unmeasured confounding remains possible, and we narrowed causal language accordingly." |
"The subgroup clearly benefits." | "The subgroup estimate is directionally larger, but the interaction is imprecise. We now present it as hypothesis-generating." |
"There were no safety concerns." | "No excess was detected within the observed exposure and follow-up; Table 4 now reports severity, timing, and denominators." |
"The Central Illustration has been improved." | "The illustration now displays the cohort, primary estimate, absolute event difference, uncertainty, and clinical boundary." |
Concede a real reporting or analytical gap directly. Push back by showing why a requested analysis answers a different clinical question, then offer the closest valid test and a bounded statement.
In our review work with JACC revisions
In our pre-submission and revision work with JACC-targeted manuscripts, we read the response alongside the protocol, statistical analysis, tables, figures, abstract, Central Illustration, Clinical Perspectives, and conclusion. These are qualitative Manusights patterns, not JACC acceptance statistics or access to confidential editorial records. Each can be tested against an author's own files.
Pattern 1: the JACC response expands statistics but not clinical meaning
A reviewer asks whether the result matters clinically, and the revision adds another adjusted model, p-value, or subgroup table. The response becomes longer while the abstract still omits absolute risk, uncertainty, follow-up, or the decision consequence. We trace the primary endpoint from protocol through Table 2, Central Illustration, and Clinical Perspectives. If the clinical interpretation cannot be stated with magnitude and boundary, another model is not the missing artifact.
Pattern 2: endpoint hierarchy changes silently
In JACC revisions, a secondary or exploratory result may become the headline after the prespecified primary result weakens. The response discusses the new analysis but does not reconcile protocol, registry, methods, abstract, and figure order. We build an endpoint ledger and mark every deviation. The honest repair can still produce an important paper, but the labels and conclusion must preserve the hierarchy.
Pattern 3: safety and efficacy use different evidentiary standards
The efficacy result receives adjusted estimates and confidence intervals, while safety is summarized as "no difference" from sparse counts. We inspect exposure, denominators, event definition, severity, timing, adjudication, competing risk, and follow-up. The JACC response should not claim reassurance beyond the precision of the safety data.
Pattern 4: the manuscript and response use different causal verbs
The rebuttal carefully says "association," but the title, Central Illustration, or conclusion still says "reduces," "prevents," or "improves." We run a claim-language audit across every high-visibility component. Returning reviewers notice the strongest version first, so a qualified letter does not neutralize an overclaimed manuscript.
The useful information gain is the cross-artifact check: endpoint, estimate, uncertainty, safety, visual summary, and clinical perspective must remain one coherent result after revision.
Check the JACC response and revised clinical evidence together before re-review.
Handling reviewer disagreement
When reviewers request incompatible endpoint emphasis, models, or interpretations, summarize the conflict for the Associate Editor. Identify the clinical uncertainty each request targets and propose one coherent revision. Do not satisfy one reviewer by creating a contradiction elsewhere.
The editor integrates the reports. Ask for clarification only when complying with both requests would change the study question or create incompatible analyses.
Why a JACC revision can still be rejected
Revision Required is not acceptance. Rejection-on-revision risk remains when endpoint hierarchy is unresolved, a new analysis reveals weaker evidence but the claim stays unchanged, safety reporting is incomplete, or the response is detailed while the manuscript retains the original problem.
Most dangerous are revisions that look comprehensive because they contain many pages. Completeness is not length; it is alignment between each concern, action, result, location, and claim.
Submit if; think twice if
Submit if: editor priorities are resolved, endpoint hierarchy remains faithful to the protocol, safety and efficacy use transparent denominators and uncertainty, and the response points to a synchronized abstract, tables, Central Illustration, Clinical Perspectives, and conclusion.
Think twice if: the headline depends on an exploratory result, subgroup interaction is unresolved, safety follow-up is too sparse for reassurance, or the response uses careful associational language while the manuscript still makes causal or practice-changing claims. Those mismatches are rejection-on-revision risks, not cosmetic issues.
Readiness check
Run the scan to see how your manuscript scores on these criteria.
See score, top issues, and what to fix before you submit.
Final JACC revision audit
- Put editor priorities before reviewer sections.
- Quote or faithfully subdivide every comment.
- State action, result, and exact location.
- Reconcile protocol, registry, endpoint hierarchy, and multiplicity.
- Report absolute effects, uncertainty, follow-up, and missingness.
- Treat safety with explicit denominators and precision.
- Test subgroup differences with interactions.
- Synchronize abstract, tables, Central Illustration, Clinical Perspectives, and conclusion.
- Keep comments and responses typographically distinct.
- Recheck page and line numbers in the final clean manuscript.
How this page was reviewed
We reviewed current JACC author materials and the journal's published manuscript-revision guidance, then applied the endpoint-to-clinical-artifact audit above. This page helps authors test whether a response and revised manuscript agree; it does not predict acceptance or replace the current decision letter.
Measure this page after 14 complete GSC days. At day 21, keep, revise, or stop based on indexing, owned queries, impressions, clicks, and qualified review starts. Four preview starts are a product-intent proxy, not proof of exact-query volume.
JACC sources establish the revision workflow and journal artifacts. The clinical concern-to-change framework is Manusights analysis.
Frequently asked questions
Restate each editor or reviewer issue, state whether you agree or disagree, describe the analysis or revision completed, and quote or locate the exact manuscript change. Begin with the editors' controlling clinical and methodological priorities, then answer every reviewer comment in order.
No. JACC describes Revision Required as a manuscript that is not acceptable in its current form but may be reconsidered after thorough revision. The authors must address all editor and reviewer comments, and the revision may be re-reviewed and treated as a new submission.
Yes. JACC's editorial guidance says reviewers advise the editors and that a compelling, courteous rebuttal can prevail. Identify the clinical or validity question behind the request, supply the closest decisive evidence, and state the remaining boundary rather than dismissing the request.
Synchronize the abstract, primary endpoint, methods, statistical analysis, tables, figures, Central Illustration, Clinical Perspectives, discussion, limitations, and disclosures. A response is incomplete when the letter changes but the high-salience manuscript artifacts retain the old claim.
Sources
Final step
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan. See score, top issues, and journal-fit signals before you submit.
Anthropic Privacy Partner. Zero-retention manuscript processing.