Co-Authoring with a Senior Fellow: How Partnerships Get You Published

Key takeaways

• A senior fellow contributes institutional standing, editorial judgment, and a route into an outlet's commissioning process. The junior partner contributes drafting capacity, literature work, and specialist knowledge the fellow has no time to assemble.
• Output type decides format, evidence bar, and review timeline. Reports, policy briefs, working papers, commentaries, journal articles, and transcripts operate under different rules.
• AI assistance rules belong to the outlet, not the institution. A journal's policy can differ from the same organization's blog, and guidelines change after publication.
• Verify the exact publication and its date before you cite or submit. A live page with no date is undated, and a recent crawl does not prove a recent revision.
• Settle authorship order, data access, and disclosure wording before the first draft.

1. Introduction

Think tank bylines rarely come from cold pitches. Editors commission people they have worked with before, and an unsolicited email from an unknown author competes with a full inbox. Co-authoring with a senior fellow shortens that distance, because the fellow already sits inside the outlet's commissioning conversations and can defend a draft through review.

The arrangement breaks down in predictable ways. Roles stay undefined, so one partner drafts 4,000 words and the published brief runs to 2,200. An AI disclosure rule the fellow remembered from a journal does not govern the same institution's blog. A cited figure carries a year but no permalink, and fact-checking stalls.

This article covers the division of labor behind a shared byline, how to choose an output type before writing, how AI and disclosure rules vary across outlets, and how to keep a source record that survives review. It closes with a comparison of several outlets by strength, limitation, and the kind of expert each one suits.

2. The division of labor behind a shared byline

A co-authored piece works when both partners agree on who owns the argument, who owns the prose, and who absorbs the revision rounds. Vague goodwill produces a stalled draft.

A fellow's contribution is rarely writing speed. It is judgment about what an editor will accept, which recommendation survives trimming, and how to phrase a finding so a policy reader can act on it. Fellows also carry reputational exposure: their name sits on the argument for years, and a retracted claim costs more than a missing byline. That asymmetry explains why an experienced fellow pushes back harder on speculative numbers than a junior co-author expects.

The junior partner usually supplies the literature review, the data assembly, the first full draft, and the stamina for three revision rounds. Those are the tasks a fellow is least likely to have time for.

Put five items on the table in the first call:

1. Which sentence states the argument.
2. Target length and the outlet's house format.
3. Who speaks to the editor, and who gets copied.
4. Authorship order and how the byline reads.
5. What happens if the outlet asks for a shorter version or a different angle.

Consider a research assistant who spent six weeks assembling a 4,000-word draft on public procurement rules. The fellow cut the background section in half, rewrote the recommendation as three options with trade-offs, and submitted 2,200 words. The piece ran. The assistant's contribution was the evidence base the fellow could not have assembled in the same window.

Authorship conventions vary. Some outlets list the senior figure first regardless of drafting contribution. Ask for the outlet's convention before you agree. Data rights deserve a sentence too: who keeps the dataset, and who can reuse the figures in a later journal article.

3. Choose the output type before you write a sentence

Publication type decides structure, length, evidence bar, and review timeline. A 2026 comparative research note on think tank outputs separates them clearly: a report develops an extended analysis; a policy brief concentrates on a decision and options; 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 a fully edited research finding.

Match ambition to the window you have. If a minister's announcement lands next Tuesday, write a commentary. If your evidence needs six months of data collection, run it as a working paper first, gather feedback, then submit a journal article. A 200-word commentary that wants journal-level proof gets rejected quickly.

Transcripts carry less evidentiary weight than edited findings. Cite them as records of a conversation, and do not lean on them to support a claim that needs data.

4. AI assistance and disclosure rules sit with the outlet

There is no universal think-tank AI policy. Contributor guidelines follow three broad patterns: AI-generated work prohibited, limited assistance permitted with disclosure, and detailed declarations of which language or editing tools were used. A rule written for a journal may not apply to the same institution's blogs or commissioned reports.

Check the guidelines for the exact outlet you submit to rather than the institution's general page. RUSI's contributor guidelines, for instance, are written for that outlet's newsbrief format. Save a dated copy of the rule text alongside your submission, because instructions can change after your cutoff.

If you used a tool for translation, transcription, or copy-editing, keep the disclosure short and specific: which tool, at which stage, and what it changed. An editor can work with "translated from French with [tool], then edited by both authors." Vague statements such as "AI was used in drafting" invite a rejection.

Fellows usually carry lower risk tolerance than junior co-authors. Their name and their institution's brand sit on the piece, so a disclosure dispute becomes a reputational problem rather than a formatting one.

5. Verification: dates, permalinks, and the source log

Both bylines depend on a citation trail that survives fact-checking.

The methodology behind this research sets out the rules. A live page without a date is labeled undated. Older reports and standards are retained where useful and identified by year. A forthcoming sector report is not treated as already published. A recent crawl is not evidence of a recent revision.

The update procedure is equally specific. Recheck the exact publication before submitting. When a rule changes, record the date, the URL, and the affected dossier. Preserve historical figures with their period. For dynamic reading indexes, follow and save the specific publication permalink before relying on it in a formal bibliography.

Keep one page per piece with columns for claim, source, publication date, retrieval date, permalink, and reviewer. Hand it to the fellow before the editor asks. This takes twenty minutes and prevents the most common reason a co-authored draft loses a week in review.

6. Outlet comparison: strengths, limits, and expert fit

Choosing two or three targets beats sending the same draft to ten. A commentary written for a fast newsbrief reads wrong in a peer-reviewed journal, and the rewrite costs more than a fresh pitch.

A short checklist before drafting:

• Confirm the outlet's current contributor guidelines and save a dated copy.
• Confirm whether the piece will be commissioned, peer reviewed, or edited in-house.
• Fix target length and format with the fellow, in writing.
• Agree authorship order and disclosure wording.
• Build the source log while you research, not after acceptance.

7. FAQ

Q1. Can an unaffiliated researcher co-author with a think tank fellow?

Yes, provided the fellow carries the institutional relationship. Outlets care about the fellow's affiliation, not yours. Your role still has to be legible to the editor: data work, regional expertise, or a method the fellow needs. Some outlets require external co-authors to sign a contributor agreement or declare funding, so check the requirements before you start writing.

Q2. Who should be first author on a co-authored think tank piece?

Outlet convention and actual contribution both matter. Some outlets list the commissioning fellow first regardless of who drafted the text. Confirm the convention with the editor's office early. Renegotiating byline order after acceptance creates friction you do not need.

Q3. Does using AI for editing disqualify a submission?

Only the specific outlet's rules answer that. Prohibition, permitted assistance with disclosure, and detailed tool declarations all appear across institutions, and a journal's rule may not apply to the same organization's blog. Disclose narrowly and precisely, then let the editor decide.

Q4. How long does a co-authored policy brief take?

Timeline follows the review process rather than the word count. A commissioned commentary can appear within days, a policy brief waits on internal review, and a peer-reviewed journal article can take many months. Budget the fellow's calendar, since their review time is the bottleneck in most partnerships.

8. Conclusion

The partnership works when three things are settled before drafting: the output type, the outlet's current rules, and the verification record. The fellow supplies access and editorial judgment; you supply evidence and drafting capacity. Neither half substitutes for the other.

Start with a format that matches the evidence you already hold. A working paper or a commentary built on completed research clears review faster than a report that promises data still being collected.

Keep the dated guideline copy and the source log from that first piece. The second submission moves faster because the record already exists.