Slate Future Tense Submission Guidelines

Key takeaways

• Future Tense, the technology and policy section that Slate runs with New America and Arizona State University, publishes short argument-driven work. A pitch has to carry a claim, a timely question, and evidence a reader cannot get from the news story itself.
• Contributor terms at general-interest outlets change without announcement. Confirm length limits, rights, payment, AI policy, and response times on the outlet's own page, and record the date you checked.
• Pitches that name a specific reader, a specific decision, and a specific piece of original evidence get read past the first paragraph. Topic summaries do not.
• Track the same twelve fields for every outlet you approach. That record lets you compare fit honestly instead of rewriting the same pitch five times.

1. Introduction

Technology policy writing has an unusual problem. There are more places to publish than there were a decade ago, and fewer of them explain what they want in terms a working analyst can act on. A researcher with a strong argument about AI procurement or undersea cable security often ends up guessing: is this a 900-word commentary, a 4,000-word report, or a pitch email first?

Future Tense sits in that gap. It is a partnership project between Slate, New America, and Arizona State University, which means editorial decisions run through a commercial magazine's process rather than an academic review system. Writers who understand that difference get responses. Writers who send a paper abstract to a magazine editor usually do not.

The guidelines below cover what the section looks for, how to build a pitch that survives a first read, and which details you must verify yourself before you send anything. Outlet pages change, sometimes quietly, and no third-party summary can replace the version on the publisher's own site. Treat this article as the preparation work you do before you open that page.

2. What Future Tense publishes, and who fits

Future Tense covers emerging technology and its policy consequences for a general but informed readership. Pieces are short by policy-writing standards, which leaves room for one argument and a limited amount of supporting evidence. The audience includes people who follow technology policy closely but do not work inside a specific technical subfield.

A useful test before you write a word: can you state your argument in one sentence that a congressional staffer would repeat to a colleague without adding context? If the sentence needs three clauses to stay accurate, the material is probably a report or a paper, and a different outlet will serve it better.

Authors who land pieces in this section usually have a direct claim on the topic. They built the system, ran the program, litigated the case, audited the deployment, or hold data nobody else has assembled. That claim does not need to come from a famous institution. A city privacy officer describing what a procurement clause actually did in practice is more useful to an editor than a professor restating a published paper.

Three practical moves help before pitching:

1. Read the last two months of Future Tense output and note which pieces came from outside contributors. Look at how quickly each piece opens with its claim.
2. Check whether the topic has already been covered in the same section. If it has, pitch the angle that changes the terms of the discussion, such as new data, a court ruling, or a failed implementation.
3. Decide whether your piece is time-sensitive. If it depends on a bill markup or a product launch, say so in the first line of your pitch and give the editor a date by which the argument goes stale.

Writers whose work is primarily archival, methodological, or addressed to a specialist discipline will find a better home elsewhere. That is not a judgment about quality. It is a question of what a magazine section can do with a piece in a news cycle.

3. How to prepare a pitch that survives the first read

A pitch is a compressed version of the finished argument. It is not a description of the topic, and it is not a summary of your credentials.

Editors in this space respond to five elements, and each one does separate work. The claim states what you will argue. The timely question explains why this week matters. The evidence shows what you know that the reader does not. The reader names who benefits from the argument. The biography establishes why you are the person to make it. Drop any one of them and the pitch gets weaker in a specific, predictable way.

A short pitch template that fits most editors' patience:

Claim: [Your argument in one sentence.] Why now: [The decision, deadline, or event that makes this urgent.] Evidence: [Data, documents, interviews, or direct experience you alone can bring.] Reader: [The person or office whose decision this informs.] Author: [Two sentences on your direct connection to the subject.]

Two habits improve the odds. Write the pitch before you draft the piece, because a claim you cannot compress usually signals a claim you have not settled. Then send the pitch only after reading the outlet's own instructions. Where a publication's guidance conflicts with general advice, including the advice in this article, follow the publication. It knows its own process.

Expect a first response that asks for a tighter frame. That request is normal and usually means the editor sees something workable. Reply with a revised claim and a proposed word count rather than a defense of the original pitch.

4. The verification checklist

The checklist below is a recording template compiled for this article. It is not Slate's official form, and it is not any institution's official form. Its purpose is to force you to write down what you actually confirmed, so you do not discover a term after you have filed.

Four rows carry the most risk for a first-time contributor.

Exclusivity. Many outlets in this space accept simultaneous pitches but expect the finished piece to be exclusive at the point of acceptance. Ask directly whether a version of the argument already posted on your institutional blog disqualifies the piece.

AI. Policies differ by outlet and change faster than almost any other term. Some publishers permit AI for transcription, translation drafts, and copy-editing while prohibiting generated text, and some require disclosure of any use at all. Slate has published rules for AI use in its own journalism; contributor-facing expectations may not match those exactly, so confirm the rule with the editor and keep your notes.

Money. Distinguish an honorarium from a submission fee and from an open-access charge. They run in different directions, and a page that mentions one does not imply the others.

Verification. Save the guidelines page or take a dated screenshot. If an editor later quotes terms that differ from what you read, a dated record settles the question without an argument.

5. Where a technology policy piece can go: outlet comparison

Slate Future Tense is one route among several, and the right choice depends on your evidence, your timeline, and where you are in your career.

A practical sequence for most writers: publish the technical version where the evidence fits, then pitch the policy argument to a general-interest section once the underlying work has been reviewed or reported. The two pieces do different jobs, and the second one cites the first.

6. FAQ

Q1. Does Slate Future Tense pay contributors?

Payment terms are set by the publisher and change over time. General-interest magazines with advertising and subscription revenue commonly pay for accepted freelance work, while many think tank blogs do not. The only reliable answer comes from the outlet's current contributor page or from the editor handling your pitch. Ask before you file if the terms affect whether you can take the assignment.

Q2. Can I pitch the same idea to Future Tense and another outlet at the same time?

Simultaneous pitches are widely tolerated because they cost editors little. Simultaneous submission of a finished draft is a different matter, and many outlets treat it as a breach once they accept. Say in your pitch that you are approaching more than one outlet, and withdraw immediately when you accept an offer elsewhere.

Q3. How should I handle AI disclosure?

Read the outlet's policy before you draft, note which uses are permitted, and record what tools you used and for which tasks. If the policy is unclear, ask the editor in writing and keep the reply. A short disclosure line costs you nothing. Discovering a disclosure requirement after acceptance can cost you the placement.

Q4. What if the guidelines page contradicts what an editor tells me?

Follow the editor's most recent written instruction, and confirm it by email if the conversation happened on a call. Guidelines pages go stale, and an editor's email is the operative instruction. Keep both records so the timeline is clear if the piece runs into a rights or length dispute later.

7. Conclusion

Future Tense rewards writers who can compress a policy argument into a short, timely piece and defend it with evidence only they hold. The submission process around that work is administrative, and administrators notice when a pitch arrives with the right shape: a claim, a reason this week matters, named evidence, and a reason you are the author.

Before you send anything, spend thirty minutes on three tasks. Read the last two months of the section's output. Open the outlet's own contributor page and record the twelve fields in the checklist above, including the date you checked. Then write your claim in one sentence and read it aloud. If it holds up, the pitch is ready. If it falls apart, the piece was not ready either.

For writers whose work is more technical than editorial, the sequence matters more than the venue. Publish the evidence where it can be checked, then bring the argument to a section that reaches decision makers. Slate Future Tense is a strong second stop for that path, and a weak first one.