Center for Global Development (CGD) Submission Guidelines

Key Takeaways

• No universal unsolicited pitch inbox for the Center for Global Development has been verified. Writers searching for a "submit your article" page find research output instead.
• CGD publishes craft guidance, including "Notes on How to Write a Blog," but writing advice describes style. It is not an acceptance policy or a submission channel.
• One documented participation model exists: collaborative co-writing with a CGD researcher. Victoria Fan's writing note records this arrangement, which shows a route rather than an open call.
• CGD's research agenda centers on economic work that aims at poverty reduction and improved lives, covering development finance, health, education, migration, climate and technology. Topical fit decides more than pitch polish.
• Word limits, house style, review time, payment and exclusivity for outside contributors are unconfirmed in public sources. Any figure you find elsewhere should be treated as unverified.

1. Introduction

People who want to publish with a think tank usually begin the same way: they look for the submissions page. With the Center for Global Development, that search ends awkwardly. CGD publishes research and commentary, and it offers its contributors guidance on how to write, yet no universal unsolicited pitch inbox has been confirmed. A writer who pastes a finished 1,200-word op-ed into a general contact form is guessing at the process, and a wrong guess costs a week of work.

The confusion carries a second cost. Authors who assume CGD runs like a newspaper opinion desk write for a general audience and lead with outrage. Authors who assume it runs like an academic journal send abstracts with no policy hook. Both miss what the institution exists to do: economic research aimed at poverty reduction and improved lives, across development finance, health, education, migration, climate and technology.

This guide covers what is verified about publishing with CGD, what remains unknown, and how to build a credible approach when no formal submission channel is public. It also compares CGD with other outlets that accept outside commentary, so you can judge where a given draft belongs before you send it anywhere.

2. Start with the researcher, not the submission form

The practical entry point at CGD is a person's workstream, not a portal.

CGD's public writing guidance tells you something about how the organization thinks. "Notes on How to Write a Blog" exists as a publication, which means the blog is a live format and the institution has opinions about how it should read. A style note describes how finished pieces should look. It says nothing about who gets to write them.

The one participation model documented in the sources behind this article is collaborative co-writing. Victoria Fan's writing note records co-writing as a working arrangement. That is evidence that outside writers have contributed alongside CGD researchers. It is not a promise that a cold email will be accepted, and it is not a general submissions process.

Read that distinction carefully, because it changes tactics. If entry runs through collaboration, then the useful question is not "where do I submit" but "whose current project does my evidence advance." A shortlist of two or three researchers whose recent output overlaps your topic will outperform a mass mailing to every address on the site.

A workable routine:

• Pick three CGD researchers who have published on your subject in the past 18 months.
• Read their last four pieces and note the data sources they lean on and the policies they argue about.
• Check whether they have co-authored with people outside CGD. That pattern tells you whether collaboration is normal for them.
• Write one specific note that names the gap you can fill, not a general offer to contribute.

Do not send a completed 3,000-word manuscript to a general enquiries address and wait for an editor to reshape it. Nothing in the verified record suggests that review happens there.

3. What development editors weigh: implementer, payer, constraint, evidence

A development pitch succeeds or fails on four questions, and most rejected drafts answer none of them.

The research library that compiled this guide sets out an editorial assessment: a development proposal should identify who implements the policy, who pays for it, which constraint it addresses, and what evidence supports scale-up. This is compile-time advice rather than a published CGD rulebook, and it is worth taking seriously because it describes how policy economists read a proposal.

The last row causes the most damage. A compelling pilot result in one district is a long way from national effectiveness, and editors in this field know the distance. Write the pilot finding, then write what would need to be true for it to travel: administrative capacity, fiscal space, political durability, supply chains. If you cannot name the payer, say the financing is unresolved. An honest gap reads as competence; an invented funder reads as a fabrication risk and ends the conversation.

4. Handle the unverified parts directly

Word limits, house style, review time, payment and exclusivity remain unconfirmed for outside contributors. Do not import another outlet's rules.

This is where most writers create their own problems. They assume a 900-word cap because a newspaper opinion desk uses one. They assume rights transfer because a magazine contract said so. They assume a two-week decision because a blog they once wrote for replied quickly. None of that transfers to CGD, and acting on it produces a pitch that answers questions nobody asked.

Handle the gaps with questions rather than assumptions. In a first message, one line covering practical terms is enough: ask whether a contribution would be commissioned as a co-written piece, whether there is a preferred length, and whether the outlet expects exclusivity. Editors answer those questions easily. They cannot answer a 2,000-word draft that arrived without a request.

Two behaviours protect the relationship:

• Ask before you write at length. A 150-word note that describes your evidence and your fit takes five minutes to read and can be routed to the right person.
• Do not assume payment either way. Confirm it if the answer changes whether you can do the work. Plenty of think tank commentary is unpaid, and finding that out after three revision rounds is avoidable.

The same restraint applies to the style guide. "Notes on How to Write a Blog" is the closest thing to public craft guidance, and it is useful for tone: plain language, evidence-forward, short paragraphs. Treat it as orientation. Treating it as a submissions checklist will not help you.

5. Comparing where your draft could go

CGD suits some writers and frustrates others. The comparisons below are about fit, not prestige.

A practical reading of that table: if your evidence is economic and your audience is development professionals, CGD is worth the slower route. If your argument is about platform regulation, data governance or AI procurement, a technology-focused outlet will place it faster and reach readers who care. If you need a citation for a tenure file, none of these substitutes for a journal.

Career stage matters too. Early-career writers often get more from co-writing with a researcher than from a solo byline, because the collaboration teaches the house standard. Senior researchers with an established publication record can approach a specific workstream as peers and skip the introductory framing.

6. FAQ

Q1. Does CGD accept unsolicited submissions?

No universal unsolicited pitch inbox has been verified. What the record does show is collaborative co-writing between outside writers and CGD researchers, documented in Victoria Fan's writing note. That is one participation model, and it is not a general guarantee. Approach a specific researcher's workstream rather than a general submissions address.

Q2. What should a first message to a CGD researcher contain?

Keep it under 200 words. State the topic in one sentence, name the evidence you bring, explain how it connects to something the researcher has already published, and offer to share a short outline. Add one line asking about format, length and timing. Skip the attachment. A full draft signals that you have already decided the piece is finished, which removes the collaborative step that appears to be the actual entry point.

Q3. Is there a word limit or a house style I should follow?

Neither has been confirmed for outside contributors. CGD publishes "Notes on How to Write a Blog," and reading it will help you match the register: direct sentences, evidence in front, minimal jargon. That is craft guidance, not a submission rule. Confirm length and format directly with the person commissioning the piece.

Q4. Will I be paid, and can I publish the same piece elsewhere?

Both are unconfirmed. Ask before you invest substantial time, and ask in plain terms rather than hinting. If exclusivity matters to your own publication plan, raise it at the outset. Assuming either an honorarium or a right to republish can turn a working relationship into a dispute.

7. Conclusion

CGD is a reasonable target for writers whose evidence is economic, whose topic touches poverty reduction, and who can wait for a relationship to develop. It is a poor first stop for anyone who needs a fast byline, a fixed word count, or a guaranteed answer within two weeks. The institution's value to a policy writer comes from the audience it reaches and the research rigor it expects, and both of those raise the bar before you write a word.

The verified path is narrow and specific: identify a researcher working on your question, read their recent output, and describe the contribution you can make to work that already exists. Bring the four elements an editor will look for. Name the implementer, name the payer or admit the gap, isolate one binding constraint, and separate your pilot result from any claim about national effects. Confirm terms before drafting at length.

If your topic sits closer to technology policy than to development economics, a specialist outlet will serve you better and faster. If your goal is a citable academic record, a journal remains the right home. Fit decides placement more than the quality of a cold email.