| name | jpart-review-process |
| description | Use to understand how the Journal of Public Administration Research and Theory (JPART) evaluates a manuscript — double-blind review, desk screening on theory and fit, the reject / R&R / accept decision categories, and the PMRA/OUP editorial context. Sets expectations and shapes the paper to survive review; it does not contact editors. |
Review Process (jpart-review-process)
Knowing how JPART screens and decides lets you pre-empt the failure modes before submitting. JPART runs a
double-blind review and screens hard for a theory contribution and field fit before sending a
paper out. Its detailed reviews report perceived strengths/weaknesses, the basis for the decision, and
advice on how to proceed.
When to trigger
- Before submitting, to stress-test against desk-rejection grounds
- Deciding whether the paper is really a JPART paper vs. PAR/JPAM/Governance
- Interpreting a decision letter and setting expectations
- Understanding what reviewers are instructed to weigh
How JPART review works
- Double-blind. Reviewers do not know the authors and authors do not know reviewers. Anonymize the
manuscript accordingly (see
jpart-submission): cite your own work in the third person, keep
acknowledgments/funding on the cover sheet only.
- Desk screening first. The editors screen for fit before external review. The decisive grounds are
typically:
- Theory — no public-management theory contribution; a finding with no mechanism or "implications
for theory." JPART's abstract template makes the theory slot explicit; an empty slot is a red flag.
- Fit — really a PAR (broad/practitioner) or JPAM (policy-analysis) paper, or comparative
institutions better suited to Governance.
- Rigor / completeness — design cannot support the claim; missing a key element of a research article.
- External review. Papers passing the desk go to expert public-management reviewers.
- Decision categories: reject, revise and resubmit (R&R), or accept (acceptance after
one or more R&R rounds is the norm). Decisions rest on the editors' read of the reviews.
- Detailed, developmental reviews. JPART describes its reviews as providing the basis for the
decision and advice on how to proceed — read them as a roadmap, not a verdict (see
jpart-rebuttal).
Shape the paper to pass
- Make the theoretical contribution explicit up front (avoids the "atheoretical" desk reject).
- Confirm JPART fit vs. siblings before submitting (avoids the wrong-venue desk reject).
- Engage the specific PA conversation you claim to advance (see
jpart-literature-positioning).
- Address the PA-specific threats (common-method bias, selection) in the design, not just in a footnote.
- Stage the public data-and-code package; it is a condition of publication (see
jpart-transparency-and-data).
Desk-screen ledger
Before submission, fill this ledger in one sitting. Empty cells predict desk rejection or a painful first
round.
| Screen | Evidence in manuscript | Failure signal |
|---|
| Theory contribution | Intro names the PA theory, mechanism, and contribution type | "Public sector setting" substitutes for theory |
| Venue fit | Literature review locates the paper inside a JPART conversation | Main payoff is a policy estimate, practice essay, or institutions paper |
| Design credibility | Identification, measurement, and scope conditions match the claim | Threats are deferred to limitations or appendix only |
| Mechanism evidence | Exhibits or qualitative/process evidence distinguish rival explanations | Results section reports only average treatment/correlation |
| Transparency readiness | Data/code release path and restrictions are staged | Replication plan begins after acceptance |
Treat the ledger as an editorial simulation: if a skeptical editor can summarize the paper as "interesting
result, unclear PA theory," route back to jpart-theory-building before submission.
Anti-patterns
- Submitting a strong-empirics, no-theory paper to a theory-and-research journal (theory desk reject)
- Mis-filing a PAR or JPAM paper as JPART (fit desk reject)
- Expecting acceptance without an R&R round — developmental R&R is the normal path
- Treating the detailed review as an attack rather than a revision roadmap
Output format
【Desk-rejection check】theory / fit / rigor — any red flags?
【Desk-screen ledger】theory / venue / design / mechanism / transparency all filled? [Y/N]
【Theory contribution explicit?】[Y/N]
【JPART fit vs PAR/JPAM/Governance】[Y/N]
【Realistic outcome】reject / R&R / (rare) accept
【Materials staged】public data + code package? [Y/N]
【Next】jpart-submission (or jpart-rebuttal if decided)
Supplementary resources
