Devex Opinion Submission Guidelines: Publishing Development Commentary

Key Takeaways

• Devex publishes argument-led commentary from people with firsthand development experience. A contestable claim backed by evidence the author can verify matters more than a senior title.
• A complete draft of roughly 700 to 900 words, a two-sentence bio, and disclosure of any funding conflicts make up a strong submission package.
• Most rejections trace to three fixable problems: promotional framing, missing evidence, and stale timing.
• Devex suits operational arguments aimed at NGO managers, donor staff, and contractors. Dataset-driven analysis fits the Center for Global Development blog better, and regional arguments fit Devpolicy or African Arguments.

1. Introduction

People who work in global development generate arguments every day. An evaluation shows a funding mechanism failing. Procurement stalls for months on rules nobody defends. A staffing model burns out national colleagues while expatriates rotate through. Devex, founded in 2000, reports on this industry for the people inside it, and its opinion section lets practitioners and former officials argue about how aid should work. Publication reaches the readers who allocate grants, write procurement rules, and design programs.

Most submissions, though, read like project reports or press releases, and editors decline them with little feedback. Writers lose the chance to shape debate because they followed the wrong template. This article explains what the desk looks for, how submission works, why pieces get rejected, and where else development writers can publish when Devex is the wrong fit.

2. What Devex opinion editors look for

The desk accepts pieces that make one contestable claim about how development is done, argued by someone with direct experience. Contestable means a reasonable colleague could disagree. "Clean water matters" fails that test. "Pooled funds delay rural water systems because disbursement rules require headquarters sign-off that field staff cannot obtain within a budget cycle" passes it.

The audience explains the standard. Devex readers are NGO managers, donor staff, contractor employees, and multilateral officials. They already know what the SDGs are and how a proposal works. Explaining basics wastes their time. The useful piece gives them an argument to raise in the next budget meeting, backed by evidence the author can verify: program data, evaluation findings, procurement records, or a detailed account of how a decision got made.

Anonymity kills credibility, so publish under your real name with your affiliation stated. Readers judge an argument about procurement differently when the author ran the process. A program officer who spent three years managing a water portfolio writes with more authority on disbursement rules than a consultant who visited twice.

Before drafting, write your claim in one sentence. If that sentence could appear in your organization's annual report without anyone objecting, it is marketing, and editors will treat it that way. Revise until a skeptical colleague would push back.

3. Submission mechanics that speed up acceptance

A complete draft moves through review faster than a query letter, because the editor can judge the whole argument immediately. Devex publishes its opinion submission guidelines on the site's opinions page, and the checklist below reflects that guidance and standard opinion-desk practice.

A submission package contains:

• A suggested headline and the full text, roughly 700 to 900 words, which matches the length of most commentaries the outlet runs.
• A bio of one or two sentences naming your role, organization, and relevant experience.
• Disclosure of any funding tied to your argument. If your employer finances the program you criticize, say so plainly.
• A subject line that states the deadline if the piece connects to a dated event, such as a summit or a budget vote.

Originality rules are strict across opinion sections. The draft should be unpublished anywhere, including LinkedIn and your organization's blog, and you should expect an exclusivity period before reposting the text elsewhere. Ask the editor to confirm the window in writing on acceptance. Editors trim for length and house style, and you can flag objections to specific edits before publication.

Send the piece to the opinions desk by email. Devex lists the current submissions route on its opinions page, and writers have long reached the desk at [email protected]. Response times vary with the news cycle. Wait about two weeks, then follow up once on the same thread. Before sending, get consent from anyone you plan to name, and check whether your data sits under a donor agreement or embargo.

4. Why submissions get rejected, and the fixes

Three fixable problems account for most declines.

Promotional framing comes first. "How our NGO empowers women farmers" advertises a program, and editors decline it because readers gain nothing they can argue with. The fix is to reframe around a contested choice. A piece titled "Matching grants keep women's cooperatives dependent on funders" takes a position and admits costs, which is the kind of argument practitioners debate. Candor about failure works with this audience, because managers who have run programs know the brochure version already.

Missing evidence comes second. A claim without a number, a named mechanism, or a dated event reads as personal taste. One verified figure from your own monitoring data, with its source stated, outweighs five general assertions. If the underlying records are confidential, describe the pattern and name the source category, for example monitoring data from municipal contracts across two countries.

Stale timing comes third. Commentary rides news, and each aid budget vote, summit communique, leadership appointment, and funding-cut announcement opens a window of days. A piece on procurement reform lands when a procurement controversy dominates headlines, and it fails when read six months later. Keep two or three drafted pieces on hand and trigger them by events. A piece that missed its window can return at the next related event once the facts are updated.

5. Where else development writers can publish

Match the outlet to the argument, the evidence type, and your career stage. The table below sets out the tradeoffs.

Career stage shapes the sequence. Early-career writers with field experience tend to start at Devex, Devpolicy, or African Arguments, where editors weigh direct experience heavily and a first byline is attainable. Mid-career analysts with original datasets can aim at the Center for Global Development, and established figures with a public track record can try Foreign Policy, which runs outside op-eds in a competitive field.

Placements compound across outlets. A piece in a smaller publication gives a later editor a byline to check, which shortens the credibility question for the next submission.

6. FAQ

Q1. How long should a Devex opinion piece be?

Plan for 700 to 900 words. Editors trim longer drafts, and heavy cutting removes evidence first, so cut the draft yourself before submitting.

Q2. Do I need a senior title to get published?

No. Editors weigh firsthand experience and a contestable claim above rank. A program officer who ran a procurement process writes with more authority on that process than a director who signed it. State your role clearly so readers can judge your vantage point.

Q3. Can I republish the piece afterwards?

Expect an exclusivity period, and ask the editor to confirm its length on acceptance. Once the period closes, request permission before reposting the full text. Most outlets allow sharing the Devex link and short quoted passages with attribution, so your organization's newsletter can summarize the piece and link to it.

Q4. What should I do if I hear nothing?

Wait about two weeks, then send one polite follow-up on the original thread. Weeks with heavy news push opinion review back. If your piece ties to a dated event, the subject line should say so from the start.

7. Conclusion

Treat a Devex submission as an argument aimed at people who allocate money and run programs. Write one claim you can defend with evidence from your own work, check the opinions page for the current submission route, send the complete draft with your bio and disclosures, and follow up once after two weeks. Writers whose arguments lean technical or regional have workable alternatives: the Center for Global Development blog for datasets, Devpolicy for Asia-Pacific questions, and African Arguments for African politics. At every one of these outlets, the claim and the evidence decide the outcome, so spend your drafting time there.