Wber Writing Style

Writing Style (wber-writing-style)

When to trigger

• The abstract states a topic, not a result, and never names the policy stake
• The introduction takes three pages to reach the question
• The paper reads either as a dry econometrics exercise or as an advocacy brief — not the WBER middle
• The bridge from "we estimate X" to "so development policy should consider Y" is missing
• A coauthor says the writing does not sound like a WBER paper

The WBER voice

WBER writing serves a dual audience: economists who demand precision and policymakers/practitioners who demand relevance. The house voice is rigorous but legible — technically exact, jargon-controlled, and always closing the loop to a development-policy implication. Two failure modes bracket it: prose so technical that a finance-ministry reader gives up, and prose so policy-breathless that an economist distrusts it. Aim for the middle: state the credible result plainly, then say what it means for a development decision without overclaiming and without implying alignment with any World Bank position (editorial independence is explicit). Write the body first; write the abstract and introduction last, once the result is final.

The introduction recipe (WBER variant)

A WBER introduction should, in order:

1. The development problem and its policy stakes — one paragraph: why this matters for poverty/growth/welfare in developing countries.
2. The question, sharply — the specific causal or measurement question.
3. The setting and data — country/region, the data spine (LSMS/DHS/admin/survey), the source of variation.
4. The headline result in policy units — the magnitude a practitioner would quote (a pp change, a dollar figure, a cost-effectiveness number), with its precision.
5. Identification in one paragraph — the design and the one assumption it rests on, stated honestly.
6. The contribution and the boundary — what is new vs. the frontier, and why this is a WBER (not JDE/World Development/Research Observer) paper.
7. The policy takeaway — what a development decision-maker should do differently, scoped to what the evidence supports.

The abstract

• ~100–150 words (confirm the current limit on the OUP page; 待核实).
• Sentence 1: the development question and why it matters.
• Sentence 2–3: the setting, data, and identification in plain terms.
• Sentence 4: the headline result in policy units, with magnitude.
• Sentence 5: the policy implication, scoped honestly.
• No undefined acronyms; no "we study"; lead with what you find.

Prose discipline

• Magnitudes over significance. "Enrollment rose 4 percentage points" beats "the effect is significant at 1%."
• Define development jargon once. Spell out program names, local institutions, and acronyms (PMT, CCT, LSMS) on first use — practitioners and economists from other fields read WBER.
• Active, claim-first sentences. Topic-sentence each paragraph with its point.
• Reference style is Chicago-style author-date as applied by OUP (verify current style on the author guidelines; 待核实). Keep citations engaging the best version of prior work, not a strawman.
• Honest hedging. Scope every policy claim to the estimand and external-validity argument; do not let the conclusion outrun the design.

Checklist

• Abstract states a result in policy units, not a topic, and names the policy stake
• Introduction reaches the question within the first page and the headline result soon after
• Identification stated honestly in one paragraph in the intro
• The "why WBER, not a sibling" boundary is visible
• Effects reported as magnitudes (with precision), not asterisk significance
• Development jargon/acronyms defined on first use
• Policy takeaway scoped to what the design supports; no implied Bank-policy alignment
• Abstract and intro written last, after results are final