Physical Review D Pre Submission Checklist: 12 Items Editors Verify Before Peer Review
Before submitting to Physical Review D (APS), verify these 12 items covering scope-fit, methods completeness, data availability, ethics, and reference cleanliness. Each is something Physical Review D editors check at desk-screen.
Next step
Choose the next useful decision step first.
Use the guide or checklist that matches this page's intent before you ask for a manuscript-level diagnostic.
Quick answer: Before submitting to Physical Review D, verify 12 PRD-specific items: APS article type, the 100-word justification statement, Letter length, a physics-visible abstract, REVTeX readability, a Data Availability Statement, arXiv/prior-submission disclosures, conflict handling, figures, references, and journal-fit against PRL, JHEP, and JCAP. In our pre-submission review work, the recurring PRD risk is equations without an early physical consequence. Last reviewed: July 7, 2026.
Run the Physical Review D pre-submission readiness check to test the same risks against your manuscript. Need broader cluster context? See the Physical Review D journal overview, submission guide, and review-time guide.
What does the Physical Review D pre submission checklist look like?
This page is not a generic "clean your manuscript" checklist. PRD is an APS physics journal for particles, fields, gravitation, cosmology, and related mathematical physics. The first editorial question is whether the paper makes a complete physics claim that belongs in PRD, not whether it has enough formatting polish.
Official APS sources define the upload system, article types, length rules, data-sharing policy, and peer-review model. Manusights adds the pre-submission layer: where PRD-targeted manuscripts lose editorial confidence before a specialist referee can evaluate the technical result. In our pre-submission review work on PRD manuscripts, we see before submission that the most common weak package has correct equations but does not yet show the observable handle, comparison to existing PRD literature, or validation path clearly enough.
In our PRD pre-submission reviews, we see editors and referees react first to whether the abstract, justification statement, main figure, equations, and data statement all point to the same physics claim.
Readiness check
Run the scan to check your manuscript against this list.
See your readiness score, top issues, and journal-fit signals in 1-2 minutes.
Methodology note and source boundary
This checklist was built from official-source facts, Manusights submission analysis, and a narrow physics-page review. Official APS sources supply the article-type, Data Availability Statement, submission-portal, peer-review, and policy requirements. Manusights interpretation supplies the pre-upload risk layer: which abstract, figure, equation, data-statement, reference, and cover-letter signals make a PRD submission easier or harder for an editor to route.
The boundary matters. This page is based on public APS guidance, publicly available PRD article patterns, and anonymized Manusights review experience. It does not claim a private PRD acceptance rate, a guaranteed desk-screen timing, or access to internal APS editorial deliberations. Use it to decide whether the manuscript package is reviewable before upload, then verify live APS instructions before submitting.
Concrete PRD-shaped examples we used for calibration include 10.1103/PhysRevD.111.063518, 10.1103/PhysRevD.111.065026, and 10.1103/PhysRevD.107.083522. The lesson is not to imitate those topics. It is to make the physics consequence, constraint, benchmark, or validation path visible before the derivation takes over.
Significance and breadth: PRD vs PRL, JHEP, and JCAP routing
Before you upload, decide whether the result is really a PRD paper. PRD can handle long derivations, simulations, lattice work, field-theory structure, gravitation, cosmology, and phenomenology. Physical Review Letters is the better first attempt only when one compact result has broad physics consequence. JHEP is often the native home for high-energy-theory community signaling. JCAP is often cleaner for cosmology and astroparticle manuscripts whose audience is narrower than PRD's full scope.
Axis | Physical Review D target check | Physical Review Letters | JHEP / JCAP / Nature Physics / Science / PNAS ceiling |
|---|---|---|---|
Desk-reject risk | Full physics claim is visible without compressing the argument | Result may be too long or specialized for a Letter | Specialist or broad-prestige venue may be more native |
First decision expectation | Specialist APS review after scope triage | Faster format triage, higher breadth bar | Field-community fit or editorial selectivity dominates speed |
Abstract requirement | State the physics consequence and testability early | One result, one broad consequence | Audience-specific motivation must match the venue |
Figure requirement | Show an observable, benchmark, constraint, or validation figure | One decisive figure may be enough | Technical or broad-story figure must carry the venue choice |
Distinctive requirement | APS submission package plus PRD justification logic | Short-format consequence and tight length | Field-community norm or cross-field importance, not only prestige |
The 12-point Physical Review D checklist
- Article type is chosen before formatting. Mark the draft as a Regular Article, Letter, Comment, Reply, or Erratum before you polish. Do not stretch a letter-shaped result into a long article with background padding.
- The 100-word justification statement says why PRD should publish it. For PRD Articles and Letters, use the justification statement to name the physics advance, not to repeat the abstract. A good version says what is new, why it belongs in PRD, and what existing limitation it resolves.
- The abstract makes the physics claim visible early. By the first few sentences, a PRD editor should see the particle-physics, field-theory, gravitation, cosmology, or particle-astrophysics contribution and the reason it is more than a calculation exercise.
- The title does not hide the result behind notation. PRD readers tolerate technical language, but a title that only names a model, approximation, or parameter scan often leaves the editorial value unclear.
- The main figure or table shows the physical consequence. The strongest visual artifact should expose a constraint, benchmark, allowed region, simulation validation, waveform, cross-section, likelihood, or other checkable physics output.
- REVTeX and equation numbering are readable before upload. APS accepts manuscript uploads through its author system, but physics readability still matters. Make sure equations, appendices, references, and figure callouts survive the PDF build cleanly.
- The Data Availability Statement is specific. APS requires published articles to include a Data Availability Statement. For PRD, the useful version says what numerical data, code, simulation inputs, spectra, chains, event selections, or tables can be shared and where access limits apply.
- Code and simulation artifacts are versioned when they carry the result. If the claim depends on custom code, a tagged release, archive DOI, repository snapshot, or clear availability note is stronger than "available on request."
- arXiv and prior-submission history are disclosed cleanly. PRD readers often see the arXiv version first. Keep the manuscript, cover letter, and submission fields consistent about preprint status, prior rejection, transfer history, and major resubmission changes.
- Suggested referees or exclusions avoid conflicts. Use APS's current submission prompts if they ask for suggestions or exclusions. Do not list close collaborators, recent coauthors, institutional neighbors, advisor-trainee relationships, or direct competitors whose conflict would be obvious.
- References cover the current PRD neighborhood. The introduction should acknowledge recent PRD, PRL, JHEP, JCAP, and arXiv work that materially changes the claim. Missing direct counter-evidence makes the manuscript look stale even when the calculation is new.
- The cover letter names the PRD audience. The first paragraph should say why this belongs in PRD specifically: full-length specialist treatment, complete derivation, observable implication, or technical validation that needs PRD's physics readership.
Data Availability Statement and FAIR numerical package
For PRD submissions, the data statement is not just compliance text. It is part of the trust package. A theory paper may have no raw experimental data, but it can still have parameter grids, notebooks, simulation inputs, likelihood files, spectra, event selections, benchmark points, or derived numerical tables. A simulation paper can fail the reader's trust test if the result is impossible to inspect from the manuscript alone.
Use FAIR data language where it is true: make data findable through a stable repository, accessible under stated conditions, interoperable enough for another physicist to use, and reusable with versioned context. Do not overpromise open data if collaboration, detector, privacy, licensing, or embargo constraints prevent sharing. Instead, explain exactly what can be shared, what cannot, and why.
What official APS requirements should you verify?
Requirement | PRD pre-submission check | Why it matters before upload |
|---|---|---|
Submission system | Use the APS author submission portal | Wrong portal assumptions waste time and create stale checklist copy |
Article type | Regular Article, Letter, Comment, Reply, or Erratum | Article type controls length, framing, and justification expectations |
Letter length | Verify current PRD Letter limit before upload | A compressed result that exceeds the limit needs article framing |
Justification statement | Prepare the short publication-justification field | This is where PRD fit should be explicit |
Data availability | Write a source-specific Data Availability Statement | Vague data language weakens reproducibility confidence |
Peer review | APS Physical Review journals use single-anonymized review | The manuscript must stand without author identity doing hidden work |
arXiv/preprint | Keep disclosure and manuscript version consistent | PRD editors and referees may already know the preprint |
Editor names | Verify current staff pages before naming anyone | Personnel pages change; do not hard-code an editor into a cover letter |
Across our Physical Review D pre-submission reviews: common mistakes that make PRD submissions fail before review
Across our Physical Review D pre-submission reviews, the weak drafts usually are not missing generic polish. They are missing a visible physics decision path. The manuscript may have a correct derivation, a long appendix, or a carefully generated simulation, but the first read still leaves the editor unsure whether the result belongs in PRD, PRL, JHEP, JCAP, or a narrower physics venue. These are Manusights review patterns from PRD-targeted and nearby physics manuscripts, not official APS rejection statistics. The specific failure pattern is usually visible in one manuscript component: the abstract, first figure, equations, benchmark table, data statement, references, or cover letter.
Formalism without a physical consequence. The equations may be correct, but the manuscript does not show what observable, constraint, particle-physics implication, cosmological consequence, or gravitational-wave signature would change if the result is right.
Phenomenology without current bounds. The draft names a beyond-standard-model parameter space or cosmological scenario, but it does not engage the latest collider, astrophysical, precision, lattice, or observational limits that make the result interpretable.
Numerics without benchmark stability. A simulation, lattice, Monte Carlo, or numerical-relativity result appears clean, but the manuscript does not show convergence, calibration, uncertainty propagation, benchmark reproduction, or sensitivity to assumptions.
Letter framing forced into a full article. The core result is compact, but the manuscript grows through background and appendix material rather than added physics. PRD Letters have a current length limit authors should verify before upload; if the physics needs a full article, make the added evidence real.
Data statement written as paperwork. A generic "data available on request" style sentence leaves readers unable to tell whether code, chains, spectra, tables, inputs, or derived data are inspectable.
Cover letter driven by impact factor. PRD fit should come from scope, article shape, reader, and technical completeness. A cover letter that mainly says PRD is prestigious is a weak routing signal.
The strongest PRD-ready packages make the same claim repeat across the abstract, the justification statement, the first figure or table, and the data availability note. If the abstract says "new constraint," the figure should show the constraint. If the paper claims a new numerical result, the table or appendix should show enough benchmark stability for a specialist referee to trust it. If the paper claims a broad consequence, the cover letter should explain why PRD is the right full-article venue rather than PRL, JHEP, or JCAP.
What PRD does well is give technically serious physics papers enough room for the derivation, validation, and comparison that a specialist referee needs. Where PRD falls short as a target is when the paper is actually a short broad-significance result, a purely formal mathematics paper, or a field-community paper whose natural reader is more clearly in JHEP or JCAP. That is the practical pros-and-cons boundary this checklist is meant to expose before upload.
What we see in Physical Review D readiness reviews
Across Manusights pre-submission reviews for PRD and nearby physics venues, the pattern is rarely "not enough formatting." It is usually that a technically serious manuscript has not yet made the physics claim reviewable in the first screen. The abstract may introduce the model but not the test. The first figure may show output but not the benchmark. The data statement may exist but not explain what can be checked. The cover letter may say the work is important without naming the PRD audience.
That distinction matters because PRD referees can handle dense technical detail. What slows or weakens the submission is asking the editor to infer the physics consequence from the derivation. Before upload, the title, abstract, main figure, justification statement, and data statement should all point to the same contribution.
What is the Physical Review D pre submission timeline?
The checklist itself usually takes 60-90 minutes if the manuscript is already mature. It takes longer when the check reveals a real gap in scope, validation, or data availability.
Stage | Planning range | What to verify |
|---|---|---|
Manuscript finalization | 2-3 days | Abstract, figures, appendices, equations, references |
APS package check | 1-2 hours | Article type, justification statement, data statement, file build |
Reference and arXiv check | 1-2 hours | Recent PRD/JHEP/JCAP/PRL context and preprint consistency |
Figure and benchmark audit | 1-3 hours | Main consequence, uncertainty, convergence, comparison |
Final upload | About 1 hour | APS portal fields, cover letter, disclosures, supplementary files |
Submit If
- The manuscript clearly belongs in particle physics, fields, gravitation, cosmology, particle astrophysics, or related mathematical physics.
- The result needs PRD's full technical room rather than a short PRL-style presentation.
- The justification statement, abstract, and first figure make the same physics claim.
- Derivations, simulations, constraints, or observations are complete enough for a specialist referee to audit.
- The Data Availability Statement says what can be inspected and what access limits apply.
Think Twice If
- The abstract only describes a model, approximation, or method, not a physical consequence.
- The strongest result is narrow enough for a Letter but the draft has been expanded with background instead of additional physics.
- The manuscript ignores recent PRD, JHEP, JCAP, PRL, or arXiv work that directly affects the claim.
- A numerical result depends on one setup with no benchmark, convergence, calibration, or uncertainty story.
- The cover letter is trying to justify PRD through JIF or prestige rather than through scope and article shape.
- Manusights internal preview corpus (Physical Review D and nearby physics-venue manuscripts, anonymized 2025-2026 review patterns)
Frequently asked questions
It covers PRD scope fit, APS article-type rules, the 100-word justification statement, Letter length, data availability, REVTeX readability, arXiv and prior-submission disclosures, references, figures, and cover-letter framing.
APS guidance for PRD submissions includes a short justification statement for Articles and Letters. Treat it as the place to say why the result merits publication in PRD, not as a second abstract.
Use APS's current submission prompts if they ask for referee suggestions or exclusions. Do not suggest close collaborators, recent coauthors, institutional neighbors, or direct competitors who create a conflict.
Fix the failed item before upload. For PRD, the usual problem is not a missing generic paragraph; it is an abstract, figure, data statement, or justification statement that does not yet make the physics claim reviewable.
Sources
- Physical Review D author instructions (official APS source checked July 7, 2026)
- APS author information (article preparation, author policies, and APS submission context)
- APS data availability statement guidance (official Data Availability Statement policy)
- APS editorial policies and practices (peer-review and editorial policy context)
- Authors submission portal (APS submission system)
- Crossref cited-by services and Retraction Watch database (reference-cleanliness checks)
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Anthropic Privacy Partner. Your manuscript is never used to train any model.
Where to go next
Start here
Same journal, next question
- Physical Review D Submission Guide
- How to Avoid Desk Rejection at Physical Review D
- Physical Review D Submission Process: What Happens and What Editors Judge First
- Is Physical Review D a Good Journal? Fit Verdict
- Physical Review D Impact Factor 2026: 5.3, Q1, Rank 18/84
- Physical Review D Acceptance Rate: What Authors Can Use