VoxDev Submission Guidelines: Publishing Development Economics Commentary

Key Takeaways

• VoxDev publishes short, policy-facing commentary built on development economics research, written for people who make or advise on policy rather than for other econometricians.
• A pitch of roughly 150 to 200 words works better than a finished draft, and it should lead with the finding and the decision it informs.
• The most common reason a pitch fails is that the paper answers a question no ministry, donor, or programme manager is asking.
• VoxDev sits alongside VoxEU, CGD, Ideas for India, and World Bank blogs, each with a different audience, review process, and appetite for early-career authors.
• Word limits and formatting requests change over time, so confirm the current version on the platform's own guidelines page before you cut a draft to length.

1. Introduction

A working paper on teacher absenteeism in Uganda appears in a working paper series. A few hundred people download it, most of them other researchers. The findings could change how a ministry designs its school monitoring system, and almost nobody in that ministry will ever open the PDF.

Development economists run into this gap constantly. The research is finished, the identification is credible, and the audience that could act on it never sees it. VoxDev exists to close part of that gap: it publishes short commentary that translates peer-reviewed and working-paper research into arguments a policy audience can use.

The practical obstacle is that VoxDev's editorial expectations are easier to infer from what it publishes than from a single page of instructions. Authors who write for the platform typically learn by trial: a first pitch goes nowhere, a second one gets commissioned, and the editing process reveals what the editors wanted all along.

This article explains what VoxDev publishes, how to pitch it, how to turn a paper into roughly 900 readable words, and how the outlet compares with other places development economists publish commentary. It is aimed at researchers, PhD students, and policy staff who have evidence worth sharing and limited time to learn a new genre.

2. What VoxDev publishes, and where it sits in the field

VoxDev launched in 2017 and operates in partnership with CEPR, the International Growth Centre, and the University of Oxford. It publishes written columns, hosts the VoxDevTalks podcast, and runs VoxDevLits, which are short literature reviews on themes such as cash transfers or energy access. Most written pieces rest on a published journal article or a working paper, and the platform expects the underlying research to be available for readers to check.

The audience shapes everything else. Readers include World Bank and bilateral donor staff, ministry economists, NGO programme managers, journalists covering development, and graduate students. They are numerate and sceptical, but they will not work through a structural model to find your point. A VoxDev column has to survive a reader who skims the first two paragraphs on a phone.

That means three things about fit:

• The research needs a policy lever. If the paper identifies an effect but no plausible action follows, the column has nothing to recommend.
• The finding needs to be new relative to what is already on the platform. Editors check whether the same result has been covered.
• The author needs standing. Contributors are usually researchers with a peer-reviewed publication record or a working paper that has circulated through a recognised series.

Some material belongs elsewhere. A methodological contribution with no policy application fits a methods-focused blog or a journal better. A purely descriptive country note without an evidence base rarely gets commissioned. Advocacy written without research behind it is not what the platform publishes.

3. How to pitch a VoxDev article

Editors commission from pitches, not from unsolicited manuscripts. A pitch that works is short, specific, and shows that you understand the audience. Around 150 to 200 words is enough.

A useful pitch contains five elements:

Timing matters more than most authors expect. A column tied to a programme rollout, a budget cycle, or a live policy debate gets read. A column on a topic that was widely covered two years ago competes with material already indexed on the site.

Two cautions come up repeatedly. First, do not send a full draft before an editor has expressed interest; it signals that you have not read how the platform works. Second, disclose overlap. If a version of the argument already ran on another blog, or if the paper has been covered elsewhere, say so in the pitch. Editors will find it, and undisclosed duplication costs you future commissions.

Funding disclosure also matters in development economics. If the programme you evaluated was implemented by an organisation that also funded the study, state that in the pitch and in the piece. Readers in donor agencies notice these relationships and will discount the column if they find out later.

4. Turning a paper into roughly 900 words

The paper's identification strategy is not the story. The policy lesson is. Most first drafts fail because the author compresses the paper instead of extracting the argument from it.

A workable structure runs about seven paragraphs:

1. State the finding and the country context in the first three sentences.
2. Describe the policy question that motivated the research.
3. Explain the research design in two sentences.
4. Give the main result with two or three numbers at most.
5. Address the obvious objection: who this does and does not apply to.
6. Note what remains uncertain.
7. Close on what a decision-maker could change, with the uncertainty stated.

The rewrite from academic prose into plain language is where most of the work happens. An illustrative comparison:

• Journal version: "The intent-to-treat estimate on the primary enrolment margin is 0.08 standard deviations, with a Lee bounds adjustment for differential attrition."
• Commentary version: "Offering the scholarship raised enrolment by about three percentage points. Attrition was low enough that the estimate held when we corrected for it."

Both sentences carry the same information. Only one of them survives a skim.

Jargon is not the only problem. Causal language applied to correlational evidence damages credibility with an audience that includes people who run randomised trials for a living. If the design cannot support a causal claim, say what the data can support and leave it there.

Length discipline helps too. Most VoxDev columns run well under 1,200 words, and a tight 900-word piece with one chart is easier for editors to place than a sprawling 1,500-word one. Cutting the third example, the second robustness check, and the literature review paragraph usually costs nothing.

5. Comparing development and policy commentary outlets

VoxDev is one option among several, and the right fit depends on your career stage, your region, and how quickly you need the piece to appear.

Three factors should drive the choice. Career stage matters, because institutional blogs tend to commission authors whose names already carry weight, while smaller platforms will work with first-time writers. Region matters, because a well-argued India column will travel further through Ideas for India than through a general development outlet. Time sensitivity matters most of all: if the policy window closes in six weeks, a slow review process defeats the purpose.

A practical approach is to treat these outlets as a sequence rather than a set of alternatives. Publish the technical version where the methods audience lives, then write a shorter policy version for a general development readership, with different framing and a different opening. Reusing a paragraph or two is normal; resending the same text is not.

6. FAQ

Q1. Does VoxDev accept pitches from PhD students?

Doctoral students do publish on the platform, usually as part of a team that includes a supervisor or a researcher with an established policy network. The stronger pitch from a student names a co-author with a publication record, and it puts the policy angle in the first sentence rather than the credential. If you have no co-author and no published work yet, a regional outlet or a university-affiliated policy blog is a more realistic first placement.

Q2. Is a working paper enough, or does the research need to be in a journal?

A working paper is common as the basis for a column. Journal publication adds credibility and takes years, and editors know this. What they will ask about is stability: if the paper is under review and the results could still change, tell them. A column that has to be corrected or withdrawn because the estimates moved creates a problem for the outlet and for you.

Q3. Can I publish the same piece on more than one platform?

Outlets differ on exclusivity, and sending identical text to two editors at once risks losing both. Publish in one place first. If you want a second version, re-aim it at a different audience with a new opening, a different set of examples, and a shorter length, and disclose the earlier piece in your pitch. Editors accept re-framing. They object to recycled text presented as new.

Q4. What should I do if a pitch is declined?

Ask the editor which part failed: the topic, the framing, or the timing. That answer is usually specific enough to act on. A rejected pitch about a schooling intervention might work at a regional outlet, a technology policy platform if the delivery mechanism was digital, or a methods blog if the contribution is measurement. Reframing for a different readership is more productive than rewriting the same pitch and sending it back.

7. Conclusion

VoxDev rewards authors who can state a policy lesson in one sentence, defend it with one credible study, and name what remains uncertain. The submission process is not complicated once you know the sequence: read recent columns to calibrate tone, write a short pitch that leads with the policy decision, wait for interest before drafting, then cut the paper down to the argument it was always making.

Before sending anything, test the pitch on a colleague outside your subfield. If they cannot repeat the finding back to you after one reading, an editor will not commission it either. That test costs twenty minutes and saves a submission cycle.