War on the Rocks Submission Guidelines: Pitching Defense Commentary

Key Takeaways

• War on the Rocks publishes argument-driven national security commentary, and most accepted pieces carry one claim an editor can restate in a single sentence.
• A working pitch runs 200 to 400 words and covers four things: the argument, the reason it matters this month, what the writer adds, and the proposed length.
• Rejections usually trace to a missing claim, a piece that repeats published reporting, or a draft sized like a journal article.
• Outlet selection shapes acceptance as much as pitch quality. Lawfare rewards legal reasoning, Defense One and Breaking Defense reward acquisition and budget knowledge, and technology policy venues reward technical depth.
• Check the outlet's live submission page before sending anything. Word ranges and editor contacts change without announcement.

1. Introduction

Defense commentary has more outlets than it did a decade ago, and the number of people who want to publish in them has grown faster. Officers, civilian analysts, contractors, graduate students, and former officials all send pitches to the same handful of editors each week. War on the Rocks sits near the top of that list for anyone writing about military affairs, and its editors read more pitches than they can answer.

The friction is rarely talent. It is format. A writer who can brief a general in ten minutes will send a 900-word pitch that buries the argument in paragraph four, attaches a finished draft, and addresses it to a generic inbox. The editor moves on.

This article covers what War on the Rocks looks for, how to structure a pitch an editor can accept or reject quickly, the mistakes that produce silence, and how the outlet compares with Lawfare, Defense One, Breaking Defense, and technology policy venues, so you can send the right piece to the right place.

2. What War on the Rocks publishes

Editors at War on the Rocks buy arguments. A topic on its own does not get accepted.

The outlet launched in 2013 and built its readership among Pentagon staff, uniformed officers, think tank researchers, congressional aides, and defense journalists. Pieces run short by academic standards, usually somewhere between 900 and 1,500 words, and they open with the claim. Background arrives after the reader knows what is at stake. Sources appear as inline links rather than footnotes or endnotes. The site also runs a podcast network and a members program, both of which take pitches on a separate track from written commentary.

Subjects that fit include force design, alliance management, defense industrial base problems, recruitment and retention, civil-military relations, irregular warfare, and regional security questions with a US policy angle. A piece arguing that the Navy should buy fewer destroyers and more unmanned surface vessels, supported by a cost curve, fits. A piece arguing that unmanned systems are the future of naval warfare does not, because there is nothing for a reader to test.

What gets turned down:

• Summaries of a report the outlet's readers already have.
• Book reviews, with occasional exceptions for books that speak to a live policy debate.
• Opinion columns that assert a position without evidence.
• Pieces that promote a company, a product, or the author's consulting practice.
• Drafts written as if for a peer-reviewed journal, with literature review and methodology sections intact.

Pull up the last ten articles in your subject area on the site and diagram their first three paragraphs. Paragraph one states the claim. Paragraph two explains what changed. Paragraph three says what follows if the reader accepts the claim. Match that shape in the pitch.

3. How to build a pitch editors can act on

A pitch is a decision document. Editors decide in under a minute, and the pitch either gives them enough to say yes or leaves a question they do not have time to resolve.

Every pitch needs five elements:

1. The claim. One sentence, falsifiable. "The Army's new fitness test will not survive contact with the reserve component" gives an editor something to publish or reject. "The Army's fitness policy needs another look" does not.
2. The hook. Why this month. A budget release, a deployment decision, a hearing, an inspector general report, or an anniversary with a live policy parallel.
3. The evidence. Name the data, documents, interviews, or first-hand experience you bring. Editors cannot verify access from a pitch, so describe it precisely.
4. The format. Proposed word count and whether you plan a single piece or a two-part series.
5. The standing. Two or three sentences on why you can write this: current role, relevant deployment, research, or prior publications with links.

A template you can adapt:

Subject: Pitch: [claim in six words]

Dear [editor's name],

I would like to propose a piece of about 1,200 words arguing that [claim].

The hook: [specific event, document, or decision, with a date].

What I add: [data you collected, unit you served in, document you obtained, model you built].

My background: [two sentences]. Recent writing: [two links].

I can deliver a draft within [X] days. This idea is not under consideration elsewhere. 

[Name]

Keep the message under 400 words, put the claim in the subject line, and send it to one editor. Attaching a finished draft to a cold pitch rarely helps; editors who want the draft will ask for it. If you are pitching several outlets at once, say so in one line, and expect that some editors will pass on that basis. Many outlets in this space do not reply to pitches they decline, so a single follow-up after a week is standard practice, and after that you move on.

4. Rejection patterns and the fix for each

Editors reject pitches when the cost of saying yes is unclear. A pitch that states the claim, the evidence, the length, and the deadline lets an editor picture the finished article before opening a calendar.

5. Key comparison: defense and security outlets and who fits where

Start from the argument's center of gravity. A claim about legal authority belongs at Lawfare or Just Security. A claim about a program's cost belongs where acquisition readers live. A claim about model evaluation or export controls may fit a technology policy outlet better than a defense commentary page, even when the application is military. One pitch to the outlet that matches the claim beats five pitches to outlets that do not.

6. FAQ

Q1. Does War on the Rocks take unsolicited pitches from writers without a public profile?

Yes, and the outlet has published first-time authors. Standing still matters, and you establish it inside the pitch rather than on a résumé: a deployment, a staff assignment, a dataset, or a document you obtained. If your only credential is interest in the subject, expect a longer path. Publishing in smaller venues first gives an editor something to click.

Q2. How long should the pitch be?

Roughly 200 to 400 words. Long enough to state the claim, the hook, your evidence, and your background, and short enough to read in a minute. Anything over a page invites skimming, and skimming is how pitches get lost.

Q3. Should I send a finished draft or a pitch first?

Send the pitch, then the draft if asked. Some outlets accept complete submissions, others want a pitch, and a few want both in the same email. Check the current submission guidelines on the outlet's site before sending. If the guidelines call for complete drafts, send one at the target length with a short cover note.

Q4. Can I pitch the same idea to several outlets at once?

You can, provided you disclose it. Editors accept simultaneous pitches and object to discovering after a yes that the piece is also under review elsewhere. One line at the bottom of the pitch handles this. Once an outlet commits, withdraw from the rest.

7. Conclusion

Pitching defense commentary is a matching problem. War on the Rocks rewards a single claim, a current hook, visible evidence, and a draft the editor can picture at 1,200 words. Lawfare rewards legal reasoning. Acquisition outlets reward program-level detail. Technology policy venues reward technical specificity that generalist defense pages cannot use.

Write the pitch as a decision memo: claim in the subject line, evidence in three sentences, standing in two, proposed length at the end. Keep the draft ready so a yes does not wait on you. The writers who publish in these outlets tend to be the ones who made the editor's decision easy.