Tech Policy Press Submission Guidelines

Key Takeaways

• Current guidance on a publication's own site outranks any third-party summary of that publication's rules.
• Five details decide whether your AI declaration is accurate: prohibited uses, permitted uses, disclosure location, required detail, and the date of the policy.
• A private process log covering tool, version, date, task, material supplied, and verification step makes a truthful declaration possible and fixes responsibility for facts.
• Disclosure does not repair an invented citation or a quotation that cannot be traced to a primary document.
• Format and timeline eliminate more submissions than topic does, so match the outlet to the evidence you already hold.

1. Introduction

Technology policy is one of the more accessible corners of policy publishing. Outlets actively look for practitioners who can explain how a procurement rule, a model evaluation regime, or a spectrum auction works in practice. That openness creates a problem of its own. Writers spend a week on a draft and then learn the publication wanted a 900-word pitch, or that it excludes pieces already posted to a personal newsletter, or that its AI policy requires a declaration nobody thought to record while writing.

Tech Policy Press sits in that space, publishing commentary and reporting for people who work on technology policy rather than for a general news audience. Its submission rules, like those of every outlet in the field, live on its own pages and change without notice. This article covers how to read those guidelines, which details to capture before drafting, and how the main policy outlets differ in format and audience fit. Treat any summary, including this one, as a starting point that needs checking against the live page.

2. What submission guidelines actually control

Submission guidelines do three jobs: eligibility, format, and process. Each can end a piece on its own, so read them in that order.

Eligibility covers who may submit and what counts as prior publication. A post on a personal blog, a LinkedIn essay, or a conference paper can disqualify a draft at one outlet and be irrelevant at another. Find the sentence describing exclusivity and read the surrounding paragraph, not the sentence alone.

Format covers length, structure, citation practice, and supporting material. Some outlets want footnotes pointing to primary documents. Others want inline links. Data-heavy submissions may need a methods note or a dataset readers can inspect.

Process covers first contact, response times, rights, and payment. This is the layer writers guess at most often, and guessing is where the damage happens. Three habits keep the reading honest:

• Do not infer an email address from a staff-name pattern. Use the contact route the publication lists, or ask someone you already correspond with there.
• Do not carry a word count, deadline, or rights position across from a different publication.
• Note the date you read the page. Disclosure forms often ask for the policy date, and you will not remember it three months later.

Where a rule is worded ambiguously, ask the editor for an interpretation before writing. An editor can usually resolve that in one reply, and the reply is worth keeping.

3. AI disclosure rules are set outlet by outlet

Editorial AI policies differ enough that copying one outlet's approach into another produces a false declaration. Capture five things for every publication on your list: prohibited uses, permitted uses, where the disclosure goes, how much detail it needs, and the date of the policy. A policy dated eight months ago may already have been revised.

The distinction that trips up most authors separates generating text from translating, editing, or checking language. An outlet that bans drafted prose may still permit a spelling check, and a tool's marketing label does not settle how an editor classifies its use. A product sold as a research assistant counts as generation when it writes your analysis section and as a verification aid when you use it to query a spreadsheet. If you run a French-language source through a translation tool to read it, that sits in a different category from asking a model to summarise the source for a citation you never opened.

Keep a private log while you work. Five or six fields are enough:

The log does two jobs. It lets you answer a disclosure form precisely instead of estimating, and it assigns responsibility for each factual claim. The second job matters more. Verification stays with the author whether or not a tool is permitted. Disclosure does not cure invented evidence or an unsupported quotation. If a reference cannot be traced to a primary document, remove it and the sentence that leans on it.

Guidance drawn from RUSI's contributor pages makes the same point from the editor's side. Authors should work from the official rules attached to each title before submitting, including the RUSI Journal, Survival, Orbis, Responsible Statecraft and Security Dialogue, and should request a specific editorial interpretation when the wording is ambiguous. Assuming that the most permissive policy in the field applies to your target outlet is the mistake that gets accepted pieces pulled.

4. How to rank sources when you research a publisher

When two sources disagree about a submission rule, rank them by proximity to the publisher. The order holds across tech policy outlets:

1. Current publication-specific guidance, written by the outlet for its own contributors.
2. Institutional pages stating the organisation's mission, programmes, and policies.
3. Financial documents, read against the accounting period they cover.
4. External sector resources, useful for comparison and context.

A comparison table, a newsletter roundup, or a cached copy of a guidelines page sits in the fourth tier. Those sources help you build a shortlist. They cannot settle a word count, and they should never be quoted back to an editor as the rule.

The same ranking applies when you research the organisation behind an outlet. Programme pages show what an institution works on, which shapes what its editors commission. Annual reports and funding disclosures explain institutional priorities, and they have to be read against the year they describe. A funding note from two years ago says nothing reliable about editorial capacity today.

5. Comparing tech policy outlets: format, timeline, and expert fit

Choosing an outlet is a matching exercise. The evidence you hold, the length you can sustain, and the speed you need narrow the list before topic enters the picture.

Two examples show how the matching works. If you hold satellite imagery and shipping data on a contested reef, the maritime data outlet will publish the visuals that make the piece credible. An opinion outlet would strip out the evidence and leave a claim. If you have a fast take on a bill moving through committee this month, a quarterly journal's timeline destroys the argument's value, while a quick commentary outlet keeps it live.

Global Tech Observatory (globaltechobs.com) is one option in this space for technology policy commentary. Its readership is smaller than the established journals and its editorial staff is thinner, so authors carry more of the fact-checking burden themselves. It compensates by taking specialist pieces that larger outlets pass on and by returning decisions quickly, which suits technical writers producing a first policy byline.

Treat the table as a shortlist rather than a rulebook. Word limits, response times, and AI policies change, and each outlet's own page is the only version that counts.

6. FAQ

Q1. Should I pitch Tech Policy Press first or send a finished draft?

Check the current guidelines page, because outlets split on this and a mismatch wastes work either way. Where a pitch is requested, send the argument in two sentences, the evidence you hold, why the topic is timely now, and your relevant background. Where full drafts are accepted, follow the stated length and citation format exactly. Note the date you read the page in both cases.

Q2. Can I use an AI tool to prepare a submission?

It depends on the target outlet's policy, and those policies change. Record the five details, keep a process log, and declare accurately rather than broadly. No disclosure makes a fabricated citation or an unverifiable quotation acceptable.

Q3. What counts as prior publication?

The answer varies. Some outlets treat a personal newsletter post as publication; others care only about professional outlets. Search the guidelines for "previously published", "exclusive", and "simultaneous", then read the full paragraph each term appears in.

Q4. How long should I wait before following up?

Follow whatever the guidelines state. Where they state nothing, one polite query after two to three weeks is a reasonable default for commentary outlets, and longer for journals that run formal review.

7. Conclusion

Build one short page listing, for each outlet on your shortlist, the format limits, the contact route, and the five AI policy details, with a date beside every entry. That page prevents most of the failures described here: a declaration you cannot complete accurately, a word count imported from the wrong publication, a query sent to an address you assembled from a name pattern. Verify the rules on the publisher's own site before drafting, keep the process log as you write, and treat every reference as your responsibility regardless of which tools helped produce the surrounding prose.