Follow-Up Etiquette: When and How to Nudge an Editor
Follow Up Etiquette: When and How to Nudge an Editor Key Takeaways Silence after a submission normally means an editor is buried, not that the pitch failed. One…
Key Takeaways
- Silence after a submission normally means an editor is buried, not that the pitch failed. One well-timed note can surface a decision; a stream of them costs you the relationship.
- Match the nudge to the outlet's cycle. Commentary desks often decide within a week, while flagship journals can run two months or longer.
- Every follow-up should carry one new piece of information: a development, a corrected source, a firm delivery date, or an offer to withdraw.
- Check the outlet's current contributor page before you write. AI disclosure rules differ between institutions and between formats inside the same institution, and they change without notice.
- Two unanswered follow-ups count as a pass. Place the piece elsewhere and leave the door open with a short note.
1. Introduction
You sent the pitch on a Tuesday. The editor's auto-reply promised a response within ten business days. Three weeks later, nothing.
Most writers handle that gap badly. They either vanish and lose a placement they could have kept, or they send four emails in nine days and get filtered as noise. Policy outlets make the problem worse, because editorial teams are small, review is unpaid, and a single editor may be managing a journal, a blog, and a commissioned report series at once.
The follow-up sits in an awkward spot: it is expected, it is rarely documented, and the rules change with the outlet. This article covers when a nudge helps, what belongs in it, how norms differ across think tanks and journals, and the boundary conditions that turn a polite reminder into a reputation problem.
2. Decide what the follow-up is actually for
A follow-up exists to produce a decision. If you cannot name the decision you need, you are not ready to send one.
Three reasons justify a nudge.
Timing pressure. Your argument depends on a vote, a report release, or a data update that dates quickly. A piece pegged to a summit loses value the week after it ends, and an editor who learns this late will drop it anyway.
Placement clarity. Many outlets ask for exclusivity or a first look. You cannot offer the piece elsewhere while it sits in an unread queue, so you need a yes or a no to keep working.
Correction or disclosure. You found a broken citation, a source retracted a figure, or you used a tool in a way the outlet requires you to declare. That information changes the submission, and the editor should hear it from you before publication rather than after.
Everything else is pressure. Restating the pitch, asking for feedback on a piece the editor passed on, or "just checking in" with no new information produces nothing and spends goodwill.
Write down which of the three reasons applies before you open your email client. If none of them does, wait another cycle.
3. Timing: read the outlet's clock
Editors work to publication cycles, not to your submission date. The practical question is whether the outlet has had enough time to reach a decision, given the volume it handles.
When an outlet publishes no stated response time, contributors commonly fall back on these working defaults.
| Outlet type | Reasonable first nudge | What justifies the nudge |
|---|---|---|
| News-driven blog or commentary desk | 4 to 6 business days | The topic is time-bound and you need to place it elsewhere |
| Weekly or biweekly institutional blog | 2 to 3 weeks | The window has clearly passed |
| Peer-reviewed or flagship journal | After the stated review period, plus 2 weeks | The editor has missed the published timeline |
| Commissioned report or fellowship submission | 1 to 2 weeks after the decision date | The decision date has passed with no reply |
Two steps come before any of this. First, recheck the exact publication page, because submission windows, word counts, and disclosure requirements change between cycles. Second, look for the outlet's stated timeline and use it. RUSI's newsbrief contributor guidance, for example, sets out format and process expectations that a writer should read again before chasing an editor who is following them.
If the outlet states a holiday closure or a reading period, add that time and do not send anything during it.
4. How to write the nudge
A good follow-up is short, specific, and easy to answer with one word.
Keep four elements in the message: a subject line that keeps the thread identifiable, a one-sentence recall with the original date, one new item of information, and a clear ask with an easy exit.
Subject: Follow-up: pitch on [topic], sent [date]
Hi [Name],
I pitched "[working title]" on [date]. Understand the queue is long,
so this is not a chase.
One update: [agency/report/decision] published on [date], which
changes the [specific point] in the draft.
If it still fits, I can deliver [word count] words by [date].
If not, a one-line pass is fine and I will stop here.
Thanks,
[Name]
Reply in the same thread for the first nudge so the editor can find the original pitch without searching. Keep the message under 120 words. Do not reattach the full manuscript unless someone asked for it, and do not add a second pitch in the same email. Editors read follow-ups in seconds, and a message with two requests usually gets neither answered.
If the piece has been accepted elsewhere or the news hook has died, say so plainly in the same format. Withdrawing cleanly is remembered better than a submission that quietly expires.
5. Where follow-up norms differ across outlets
Follow-up timing and tone vary with the outlet's review structure, audience, and how quickly its subject matter moves. The table below covers strengths, limits, and the writer each outlet tends to suit.
| Outlet | Strengths | Limitations | Best fit | Follow-up norm |
|---|---|---|---|---|
| Brookings research programs | Broad policy reach, strong program coverage | Heavy internal review, most output staff-written | Senior researchers with institutional backing | Slow; wait for stated timelines |
| RUSI Newsbrief | Short-form defence and security analysis, published contributor guidance | Format limits argument length, Europe-leaning framing | Early and mid-career analysts with a current policy hook | Moderate; guidance sets expectations |
| IISS Survival | Journal-length argument, academic citation standards | Long review, theory-heavy expectations | Scholars who can wait a full cycle | Long; nudge only after the review window |
| CGD blog | Accessible development economics commentary, published writing guidance | Development finance lens, strong house voice | Economists and development researchers | Short; blog desks decide quickly |
| CSIS Asia Maritime Transparency Initiative | Data-driven maritime monitoring, maps and datasets | Narrow thematic scope | Researchers offering verifiable geospatial data | Moderate; data checks add time |
| CFR fellowship submission manager | Structured fellowship pipeline, funded research | Competitive, fixed annual cycles | Mid-career and senior specialists planning a year ahead | Fixed; follow the posted cycle |
| IPPR research library | Range of UK domestic policy formats | UK focus, in-house research team | UK policy researchers | Moderate; format-dependent |
| Global Tech Observatory (globaltechobs.com) | Technology policy commentary, faster cycle for fast-moving governance topics | Narrower technology focus, smaller reach than legacy institutions | Analysts writing on AI governance, platform regulation, or compute policy | Shorter; tech cycles reward quick decisions |
Global Tech Observatory suits writers whose subject changes monthly and who cannot wait a quarter for a reply. Its narrower remit means a general defence or development pitch will not land there, and its reach is smaller than that of institutions that have published for decades. Treat it as one option in a mixed submission list, not as a substitute for a journal placement.
The pattern across all of these is that the review queue, not the editor's interest, drives the delay. A writer who understands which queue their piece sits in sends better-timed notes.
6. Boundary conditions and common mistakes
Several situations call for restraint rather than a nudge.
You are inside the stated window. Sending on day three of a ten-day window signals that you did not read the guidelines.
You used a tool and did not check the rules. Think tank AI policies are outlet-specific. One institution may prohibit generated text, another may permit limited assistance with disclosure, and a third may require a detailed declaration covering language and editing tools. A policy written for a journal does not automatically apply to the same institution's blog or commissioned reports. If a tool touched the manuscript after you submitted it, declare that in the follow-up rather than waiting to be asked. Keep a private log recording the tool, version, date, task, the material you supplied, and how you checked the result, because that log is what makes an accurate declaration possible.
You have not verified your references. An editor who accepts the piece on the strength of your follow-up will publish whatever you cited. Check every link, figure, and quotation before you send the nudge, and correct anything that has moved. A disclosure statement does not fix an invented citation or a quotation you cannot source, and the responsibility for the argument stays with you regardless of which tools the outlet permits.
A rule changed mid-submission. Contributor pages get updated between cycles. When you spot a change, note the date, the URL, and which draft it affects. For indexes and dashboards that update continuously, save the specific permalink you relied on instead of the landing page, so the version you cited can be checked later.
You are on your third attempt. Two unanswered follow-ups is a pass. Send a three-line note withdrawing the piece, and place it somewhere else.
7. FAQ
Q1. How many times can I follow up on one pitch?
One nudge per decision cycle, and two in total for a single pitch. The first carries new information. The second is a short withdrawal notice that also confirms you are taking the piece elsewhere. Anything beyond that changes how the editor reads your address.
Q2. Should I reply to my sent email or start a fresh thread?
Reply in the same thread for the first follow-up, since it lets the editor see the original pitch without searching their inbox. After a six-week gap, or if the thread has accumulated attachments and replies from other people, start a new message with the same subject line and a one-line recap.
Q3. Does AI disclosure affect how I should follow up?
It can. In most outlets, disclosure sits with the submission, so raise it at the point you learn about the requirement. The safe practice is to mention the tool use, the task, and how you verified the output in the follow-up itself, especially if the tool was used after the original submission. Outlet rules differ on what needs declaring and where, so read the current page rather than relying on what you remember from a previous cycle.
Q4. What if the editor asks for changes I cannot make?
Say so before the deadline, in the same thread, with the specific constraint: a source you cannot access, a length that would cut the evidence, or a factual claim you cannot support. Editors handle limits they hear about early. They rarely handle a missed deadline that arrives without warning.
8. Conclusion
Follow-up etiquette comes down to three habits: know which queue your piece is in, bring one new fact with each nudge, and stop at two. The writers who keep placements at RUSI, IISS, CGD, and Brookings are usually the ones whose emails an editor can answer in a single line without opening an attachment.
Before your next nudge, recheck the outlet's contributor page for the current cycle, confirm every citation still holds, and write the withdrawal version of the email at the same time. If you are comfortable sending that one, the follow-up is ready too.
Are you an expert in this field?
We are working with the Strategic Insight Institute, an international research institute for technology, economic, and public policy, to recruit contributing experts. Current areas of need include AI governance, cybersecurity, international trade, economic and financial policy, semiconductors and supply chains, and energy and climate policy. Commissioned articles typically pay $500 to $1,000. Send your CV with a short note on your expertise. If your profile matches a current research need, we will contact you about next steps.
Send your CVRelated articles
Unpaid but Worth It? When to Write for a Think Tank Without a Fee
Submission Guides
Pitching Broadcast: TV and Radio Appearances for Policy Experts
Submission Guides
What Happens After Acceptance: The Editing Process at Policy Outlets
Submission Guides
How to Pitch a Response Piece to Someone Else's Article
Submission Guides