---
name: pubar-writing-style
description: Use when drafting or polishing a Public Administration Review (PAR) manuscript so it reads for scholars AND practitioners, carries strong Evidence for Practice, and fits the limits (≤ 8,000 words incl. abstract/endnotes/references; abstract ≤ 150 words). Tightens prose and format; it does not invent content.
---

# Writing Style (pubar-writing-style)

A PAR paper must be readable by a public-management scholar outside its niche **and** speak to a
reflective practitioner. The journal's defining feature is the **research-and-practice bridge**: every
article carries **Evidence for Practice** points. This skill is about reaching both audiences and
respecting the format — not about generating claims.

## When to trigger

- Drafting the introduction, framing the contribution, or final polish
- Writing or tightening the **Evidence for Practice** takeaways
- Over the word cap and needing to cut without losing the argument
- Writing the **≤ 150-word abstract** or aligning citations to APA style

## Reach scholars and practitioners

1. **Front-load the contribution and the stake.** By the end of the introduction the reader knows the
   question, the argument, the evidence, and **why a public manager should care.** Don't make either
   audience dig for the "so what."
2. **Write the Evidence for Practice honestly.** 3–5 sentence-length takeaways that distill what the
   findings mean for practice — specific enough to inform a managerial decision, never over-claimed
   beyond what the analysis supports. (Encouraged at submission, required at revision — 检索于 2026-06.)
3. **Minimize jargon** or define it on first use; a budgeting scholar should follow a personnel paper,
   and a practitioner should follow both. Spell out acronyms.
4. **Argument-first prose.** Lead with claims; use evidence to support them. Avoid "the data show…"
   without saying what they show and why it matters for administration.

## Evidence for Practice calibration

Evidence for Practice points should be useful to a reflective practitioner, but each point must stay
inside the evidence. Draft them with a claim-evidence-action chain.

| Takeaway layer | Strong version | Weak version |
|----------------|----------------|--------------|
| Finding | names the empirical or conceptual result in plain language | "This study has implications" |
| Action implication | says what a manager, agency, or public leader should reconsider | generic "policymakers should pay attention" |
| Boundary | states where the advice applies and where it may not | universal recommendation from one setting |
| Evidence anchor | points to the table, model, case, or review logic that supports it | no trace back to manuscript evidence |
| Caution | names risk, equity concern, implementation constraint, or uncertainty | hides limitations to sound practical |

If a point cannot name its evidence anchor, rewrite it as a question for practice or remove it.

## Dual-reader paragraph test

PAR prose has to survive two readers at once. Use this check on the introduction, discussion, and
Evidence for Practice box.

| Reader | What they need in the paragraph |
|--------|--------------------------------|
| Public administration scholar | construct, literature stake, method/design warrant, and contribution to the field |
| Practitioner | administrative problem, decision relevance, implementation context, and limit of the advice |

Most paragraphs can lead with one reader's need, but the introduction and discussion should not leave
the other reader waiting more than a paragraph. When prose becomes theory-heavy, add the administrative
decision it informs. When prose becomes managerial, add the evidence or concept that keeps it scholarly.

## Format (APA author–date; confirm current edition)

- **Citations**: APA author–date style (manage with Zotero/BibTeX); keep one consistent style.
- **Abstract**: **≤ 150 words**, stating question, approach, and finding, on a page preceding the text.
- **Anonymize**: PAR is **double-blind** — no author names on the title page, refer to your own prior
  work in the third person, remove acknowledgments, institution names, and identifying URLs; strip
  identifying file metadata (see `pubar-submission`).

## Fit the word cap (≤ 8,000 words incl. abstract, endnotes, references; excl. tables/figures/appendices)

- Move balance tables, full specs, and extended robustness to the **online supplement** (excluded).
- Cut throat-clearing and literature dumps; engage the debate, not every paper (see
  `pubar-literature-positioning`).
- Tighten endnotes and references — they count toward the 8,000-word limit at PAR.
- Prefer one decisive figure to three redundant tables.

## Word-budget triage for PAR

Cut to protect the research-practice bridge, not just to hit a number.

| Overlong part | Keep | Cut or move |
|---------------|------|-------------|
| Introduction | question, contribution, public-management stake, practice relevance | long problem history or generic reform rhetoric |
| Literature | debate that creates the public administration gap | adjacent theory not used in the claim |
| Methods | design warrant and transparency essentials | implementation detail better suited to supplement |
| Results | evidence that supports the contribution and practice points | redundant models or robustness exhibits |
| Discussion | what changes for scholarship and practice | vague lessons, unsupported recommendations |
| Evidence for Practice | 3-5 bounded, evidence-anchored takeaways | slogans, mandates, or future-research ideas |

After every cut, re-check that each Evidence for Practice point still has a visible manuscript anchor.

## Abstract and title-page pass

The abstract is short, so make each sentence do a job:

1. public administration problem and audience;
2. method or evidence base;
3. central finding or argument;
4. implication for research and practice.

Do not spend the abstract on motivation alone. Also re-run the double-blind pass after final edits:
self-citations, acknowledgments, file metadata, funder names, and identifying institutions tend to
creep back in during late polishing.

## Anti-patterns

- A niche-insider intro that never states field-level significance or a practitioner stake
- Evidence for Practice that over-claims beyond the analysis, or is vague boilerplate
- An abstract over 150 words or one that hides the finding
- Mixed citation styles; acknowledgments or self-references that break double-blind anonymity
- Forgetting that **references and endnotes count** toward PAR's word limit

## Output format

```
【Contribution + practitioner stake stated by end of intro?】[Y/N]
【Evidence for Practice】3-5 honest takeaways drafted? [Y/N]
【Reads past the niche?】jargon defined / acronyms spelled? [Y/N]
【Abstract】word count (≤150)
【Word count】≤8,000 incl. abstract/endnotes/references?
【Practice calibration】each takeaway has finding / action / boundary / evidence anchor? [Y/N]
【Dual-reader pass】scholar + practitioner both served by intro/discussion? [Y/N]
【APA style + anonymized (double-blind)】[Y/N]
【Next】pubar-transparency-and-data
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — word/abstract caps, Evidence for Practice, APA style, double-blind anonymity