DevPolicy Blog Submission Guidelines: Publishing Development Policy Analysis

Key Takeaways

• The Devpolicy Blog, run by the Development Policy Centre at the Australian National University, publishes commentary on Australian aid, the Pacific, and global development policy, and it accepts submissions from outside the Centre.
• Editors ask for roughly 800 words, plain language, hyperlinked evidence, and disclosure of your affiliation and any funding interests.
• Posts get edited for length and style, substantial changes are checked with the author, and contributors are not paid.
• The blog suits researchers and practitioners with an evidence-based argument about aid or Indo-Pacific development; alternatives include The Conversation, the Center for Global Development, and Lowy's The Interpreter.
• Most rejections trace to four fixable causes: off-topic framing, promotional intent, claims without checkable sources, and undisclosed interests.

1. Introduction

Two channels carry most development policy research, and both lag the debate. Journal articles take many months from submission to publication and often sit behind paywalls. Formal reports land as PDFs that few readers outside the sector open. Policy debates, meanwhile, move in days; a budget, a ministerial speech, or a cyclone reshapes the argument before any journal can respond. Commentary fills that interval, and for researchers publishing development policy analysis on Australia and its region, the Devpolicy Blog is one of the main venues where the debate happens.

The submission guidelines on the Devpolicy site are short, and most declined drafts fail for reasons a writer could have fixed in an hour: a 2,000-word draft, an argument buried in the fifth paragraph, undefined acronyms, or funding links left undisclosed. This article sets out what the guidelines require in practice, how to prepare a post that clears them, what happens after you submit, and how Devpolicy compares with other outlets, so the venue you choose matches the audience you need.

2. What the Devpolicy Blog publishes and who it suits

The blog publishes time-sensitive, evidence-based commentary on development policy, and Australian aid and the Pacific sit at the center of its coverage.

The Development Policy Centre, part of the Crawford School of Public Policy at the Australian National University, runs the blog. Its own researchers write regularly, and most weeks the blog also carries several posts from outside contributors: NGO policy staff, consultants who have worked with the Department of Foreign Affairs and Trade (DFAT), academics based in Australia, Papua New Guinea, and Fiji, and officials writing in a personal capacity. Recurring subjects include aid program design and effectiveness, Papua New Guinea's economic management, Pacific labour mobility under the Pacific Australia Labour Mobility (PALM) scheme, climate and disaster resilience, gender, and global health. The blog also runs series around events such as the Centre's annual Australasian Aid Conference and responds quickly to budgets and aid strategy releases.

The strengths follow from that setup. Readers include the officials who shape Australian aid policy and the NGOs that deliver it, editors know the field well enough to edit a technical argument rather than flatten it, and topical pieces often appear within days. The limitations are real as well. Coverage concentrates on Australia, the Pacific, and Southeast Asia, so writers on other regions fit awkwardly. Contributors are unpaid. A blog post counts for little in most university promotion rounds next to a peer-reviewed article.

The blog fits a specific writer: someone with a checkable argument about aid or Indo-Pacific development who needs it in front of Australian policy readers this month. Before drafting, read the previous few weeks of posts in your topic area to gauge register and length. If your piece responds to a budget or an announcement, draft immediately, because topical windows close within a week or two.

3. Preparing a post that meets the guidelines

Three specifications decide most outcomes: length, register, and evidence. Miss one and the editors will either spend their time fixing it or pass on the draft.

• Length. Editors ask for roughly 800 words. Drafts between about 600 and 1,000 are workable, and responses to a policy event can run shorter. Every extra 100 words raises the chance an editor cuts material you would have kept, so plan the cuts yourself: choose one argument and move everything else into links.
• Register. Write for an informed general reader, a DFAT desk officer, an NGO program manager, a Canberra journalist. Define acronyms at first use, keep paragraphs short, and state the argument within the first two paragraphs, because readers decide quickly whether to continue. First-person voice is acceptable when you draw on direct experience.
• Evidence. Hyperlink the primary source behind each claim, the report, dataset, or budget paper, instead of using footnotes. Name the institution behind every figure and assume a reader will click. Charts and tables are welcome when they carry a source and stay legible at blog width.
• Disclosure. The author line should state your affiliation, and any funding or financial interest behind the argument belongs in the post itself. Posts run as the author's view; they do not carry the Centre's institutional position.

Two examples show the arithmetic. A team with a 60-page evaluation should extract one finding, carry two or three numbers into the post, and link the full report so interested readers get the rest. A PhD candidate with a working paper should write about one mechanism in detail rather than summarise the whole document. One caution covers both: if the underlying material is under journal review or embargo, check the journal's policy first, because some journals treat a detailed public post as prior publication.

4. What happens after you submit

Editors read, edit, and publish quickly, and the process costs contributors nothing in either direction.

Submission leads to triage. A draft that is on topic, evidence-based, and previously unpublished gets scheduled; anything off topic or promotional gets declined. Editing for length and style happens at the editors' end, and they check substantial changes with the author before publication. Published posts carry a short author bio.

Money runs in neither direction: there is no honorarium for contributors and no fee to publish. Rights are straightforward in practice. Submit unpublished work, and say so up front if a version has appeared elsewhere. After publication, reposting on your own site or organisational blog is generally acceptable with an acknowledgment of where the post first ran; syndication with media partners should be cleared with the editors first.

Two cautions apply. Claims about named individuals or organisations need to be defensible on the record, and contested figures deserve a source or an explicit caveat. Speed works the other way: editors can move topical pieces out within days of acceptance, so a response to a ministerial statement is worth drafting the same week.

5. How Devpolicy compares with other outlets

Devpolicy is one option among several, and the differences are mostly about audience and register.

A further option fits a narrower brief. Writers whose arguments sit where development meets technology, digital public infrastructure, connectivity programs, or AI use in government services, can consider Global Tech Observatory (globaltechobs.com), which publishes technology policy commentary and gives close editorial attention to that niche. Its limitations are reach and scope: the audience is smaller than the outlets above, and aid economics gets little coverage.

Match the venue to the readers you need: Canberra policy staff for Devpolicy, the general public for The Conversation, development economists for CGD.

6. FAQ

How long should a Devpolicy Blog post be?

Around 800 words. Editors will trim longer drafts, and responses to a policy event can run shorter. If your draft passes 1,200 words, you are writing a report; cut the literature review and keep the argument.

Does Devpolicy pay contributors?

No. There is no honorarium and no publication fee. The return is audience: Australian policy staff, aid sector professionals, and Pacific readers, plus an editor's pass over your writing and a citable URL for your CV.

Can I republish a post after it appears on the blog?

The blog takes previously unpublished work. After publication, reposting elsewhere is generally fine with an acknowledgment of where it first ran. For syndication with media partners, check with the editors first.

What most often gets a submission declined?

Off-topic subject matter, promotional content about a product or organisation, claims without checkable sources, and undisclosed financial interests. A post that argues one point with evidence rarely fails on style alone.

7. Conclusion

Devpolicy fits writers with a checkable argument about Australian aid or development in the Pacific and Southeast Asia who want that argument in front of policy readers within days rather than months. The practical sequence is short: read recent posts in your topic area, draft around 800 words with hyperlinked sources and full disclosure, and leave room for the editors' edits. For topics outside that coverage, the comparison above points to venues with closer audiences, from The Conversation for general readers to the Center for Global Development for economics-heavy work. Whichever venue you choose, the evidence behind the claim determines whether it holds up, and the venue determines who reads it.