How to Read a Masthead: Finding the Editor Who Can Say Yes

Key Takeaways

• A masthead lists roles, not permissions. The editor who can accept your piece is the one who owns the product type you are writing.
• Identify the product label first (report, policy brief, working paper, commentary, journal article), then find the desk that commissions it.
• Mastheads go stale. Confirm the editor still holds the role and still commissions before you send anything.
• A pitch that works names one decision maker your argument serves and states the claim in a single sentence.
• AI disclosure rules differ by outlet and by product line. Record the policy date and the required disclosure detail for every place you submit.

1. Introduction

A researcher finishes a 2,000-word policy argument, sends it to the address on the contact page, and waits. Six weeks later a reply arrives from an events coordinator who forwards it to someone in communications. The piece was publishable. It landed on a desk that handles transcripts and event pages.

Mastheads exist to prevent that outcome. The block of names and titles on a publication's about page maps who owns which part of the editorial process. Most writers read it as a ranking of importance and pitch the most senior name they can find. That name usually has the least time and the fewest reasons to answer a cold email.

This article treats the masthead as an operational document. It covers which titles carry the authority to accept a submission, how to check that the authority is current, how to read a publication's recent output to confirm which desk your idea belongs to, and what a commissioning editor needs before replying. The goal is simple: help you find the right editor on the first attempt instead of the fourth.

2. A masthead lists roles, not permissions

A title describes a function, and the function tells you what that person can decide. Six roles appear on most policy outlet mastheads, and only one or two of them will accept your manuscript.

• Editor-in-chief or director of publications. Sets the editorial line and signs off on pieces that carry institutional or political risk. This person can stop a submission, though cold pitches rarely reach them.
• Managing editor. Runs the production calendar, assigns copy editors, and tracks deadlines. Useful for confirming that a slot exists and who owns it.
• Commissioning editor, section editor, or product editor. Owns one product line such as commentary, policy briefs, or a regional desk. This is the role that accepts submissions.
• Production or copy editor. Applies house style and reference formatting to approved pieces. Cannot accept or reject work.
• Editorial board or advisory board. Meets a few times a year to set direction. Board membership is not a submissions channel, and a well-known name on that list is not a route in.
• Contributing editor or columnist. Holds a title as a writer. Publishes under the masthead and does not commission.

The practical move is to name the product you are writing, then find its owner. A data-heavy analysis sent to an opinion editor gets rejected because it is not an opinion piece, even when the same outlet publishes analyses every week. If the masthead does not name a product editor, the submission guidelines usually do. Read those before drafting the email, not after.

3. Read the feed before you pitch a name

Think-tank publication feeds mix products with different purposes, and each product passes through a different desk. A report develops an extended analysis. A policy brief concentrates on a decision and the options around it. A working paper presents research that may be revised. A commentary advances a timely argument. A journal article enters an academic or professional debate. A transcript records a conversation rather than an edited research finding.

That taxonomy is the fastest way to work out which editor you need. Read the three most recent pieces closest to your topic and sort them by function, not by length or by how impressive the layout looks.

Length alone is an unreliable classifier. A long commentary can stay an opinion essay from the first line to the last, while a short note can report a substantial empirical result. A publication's visual design or a prestigious institutional logo does not establish its review process either.

For each sample you read, record six things:

1. The opening move, meaning how the piece earns attention in its first two paragraphs.
2. The central claim, stated in one sentence.
3. The evidence pattern, meaning what kinds of sources carry the argument.
4. How the author handles uncertainty.
5. The conclusion and what it asks the reader to do.
6. The reference format and how sources are cited.

Those six fields produce an analytical reading card rather than a copied article. A writer can learn structure without imitating wording, and the cards become a record of what each outlet actually buys.

The card answers the desk question directly. If two of three recent pieces are commentaries written in the first person, the outlet buys argument and you should write to the commentary editor. If two are working papers with methodological appendices, your idea belongs with a research program, and you should expect a revision cycle rather than a publication date.

4. Confirm the editor still has the authority

Mastheads drift. People change jobs, product lines get merged, and a page that lists a commissioning editor may not have been touched in two years. Verification takes about ten minutes and prevents the most common failure in pitching.

Three signals are worth checking together:

• The date on the submission guidelines or contributor page. An outlet that publishes its AI policy with a preparation date is maintaining that page; one with no date at all may not be.
• Recent bylines, editor's notes, or introductions that name the person in an editorial role.
• A mismatch between the masthead and the current staff page. When they disagree, trust the staff page and the guidelines page.

Then check the outlet's rules for how you prepared the draft, because they differ by product as well as by institution. There is no universal think-tank AI policy. Some outlets prohibit AI-generated work outright, some permit limited assistance provided you disclose it, and some require a detailed declaration of any language or editing tools you used. A rule that applies to a journal may not apply to the same institution's blog or commissioned reports.

For each prospective submission, record five things: prohibited uses, permitted uses, where the disclosure goes, what detail the disclosure must contain, and the date of the policy. Distinguish generating analysis from translating, editing, or checking language. A tool's marketing label does not determine how an editor classifies its use, so describe the task rather than the product.

Keep a private process log while you write: tool, version where available, date, task, the material you supplied, and how you checked the result. That log makes an accurate declaration possible when an outlet requires one, and it establishes who is responsible for each factual claim and citation. Verify your references and keep control of the argument regardless of which tools are permitted. A disclosure does not cure invented evidence or an unsupported quotation.

5. Comparing outlet types: strengths, limits, and who fits

Different kinds of outlets suit different writers, and knowing the fit saves months. The table below compares common categories. Specific rules vary, so read each outlet's own guidelines before submitting.

Two patterns hold across the table. First, the more formal the review, the longer the wait and the more durable the result. Second, an outlet's prestige says nothing about which desk will read your email. A short newsbrief run by a single editor can accept a piece in a week, while a large institute's flagship report may take a quarter to clear internal review.

6. FAQ

Q1. Who is the editor who can say yes at a think tank?

The person who owns the product line you are writing for, which is usually a commentary editor, a briefs editor, or a research program director. The editor-in-chief can stop a piece but rarely starts one from a cold pitch. Start with the product owner, and copy the managing editor only if the guidelines name one for submissions.

Q2. Does a well-known institutional name mean my piece will be peer reviewed?

No. Products inside one institution go through different review. A commentary may get a single editor's read, a working paper may get internal review, and a journal article gets external referees. The publisher's label does not tell you which process applies. The submission guidelines and the recent pieces tell you.

Q3. How do I confirm an editor still commissions?

Check the date on the submission guidelines, look for the person's recent editor's notes or bylines, and compare the masthead against the current staff page. If the guidelines name a different editor, use that name. When nothing on the site is dated within the past year, send one short message to the general address asking who handles your product type.

Q4. Can I pitch the same idea to two editors at the same outlet?

No. Editors at one outlet share a submission tracker, and a simultaneous pitch to a director and a section editor reads as carelessness. Pitch one desk, wait for the response window the guidelines state, and only then approach a different editor with a revised angle.

7. Conclusion

The editor who can say yes is the one whose name sits next to the product label you are writing for. Everyone else on the masthead is context: the editor-in-chief who can block the piece, the managing editor who holds the calendar, the board that meets twice a year, and the copy editor who formats whatever survives. Read the masthead for roles, read the recent feed for product lines, and verify both against the dated guidelines page before you write a word of the pitch.

A workable next step takes an afternoon. Choose one outlet, read four recent pieces, and fill in a reading card for each. Note the product label, the editor named in the guidelines, and the date on the AI policy. Then send a pitch with five parts: a one-sentence claim, the timely question it answers, the original evidence behind it, the reader or decision maker who benefits, and a short biography relevant to the argument. If any of those five parts is missing, the pitch is not ready, and no masthead will fix that.