# What counts as published? **Who this is for:** an academic with a paper, thesis, talk, poster, or funder report connected to one piece of work, wondering whether any of it matters for what can be protected — and the TTO caseworker who eventually receives that question. What counts as published? A patent attorney or your TTO answers that, working from your actual documents and the rules that apply to your specific case — not this guide, and not you, however carefully you read your own calendar. **What this draws on:** the same pattern behind the Publish/Protect Clock prompt kit — that what threatens a piece of work is usually not a decision anyone made, but a calendar nobody was watching. This guide names no scheme, programme, institution, or jurisdiction, and cites no external rule or figure. The absence of a source list here is deliberate: the question this guide is built around is answered by professional judgement working from your documents, not by a public rule a guide could repeat safely. --- ## The question, and who answers it Ask an academic what counts as published and most start sorting: this one obviously counts, that one obviously doesn't, and a third sits somewhere they can't quite place. Ask a patent attorney the same question and the answer does not start with a list at all — it starts with the actual documents, the actual field, and rules that apply to one case, not a general one. That mismatch is the difficulty. Sorting activity into categories is a reasonable instinct, and it is also not how this question gets answered. It is answered by someone qualified, working from what is actually in front of them — not by an academic working through a guide, however carefully written. This guide does not sort anything, and it will not tell you which category anything you've done falls into. What it can do is name what is worth bringing to that conversation, and say plainly who holds the rest of the answer. **Ask your TTO:** who actually receives a question like this at your institution — a named caseworker, a general inbox, or a specific process for something time-sensitive — and how you'd find out if you don't already know. ## The ordinary things worth naming Most of what belongs in this conversation does not feel like publishing while it is happening. A seminar to a handful of people. A thesis heading for deposit, carrying results forward under a different name. A funder report that went nowhere public. None of these announce themselves as relevant, which is exactly why they get left off the list people eventually bring to a patent attorney or a TTO. | Kind of activity | Why it's worth naming, even if it feels ordinary | |---|---| | A paper, preprint, abstract, or manuscript, in any state | It carries a date, and a date is the first thing whoever you ask will want. | | A thesis, at deposit or with a viva scheduled | Deposit is one of the items people forget most often, because it doesn't feel like publishing. | | A talk, seminar, or poster, inside your department or anywhere else | Who was in the room is worth having on record, even as your best estimate. | | A funder or progress report, even one that went only to the funder | Where it went, not how many people read it, is the fact that matters here. | | A patent application, already filed or not | It tells whoever reads this next whether a process has already started. | None of this is a checklist for you to score. It is the same list a patent attorney or your TTO would ask you for anyway, gathered before you ask rather than reconstructed under pressure after you already have. **Ask your TTO:** whether your institution keeps a standing list of what it wants flagged early, or expects you to raise anything connected to a piece of work yourself, unprompted. ## Why speed beats certainty The instinct is to work out the answer before asking the question — to read enough, or think hard enough, to arrive at the conversation already knowing whether something matters. That instinct runs the wrong way here. Nobody reading this guide is positioned to reach that answer alone, so time spent trying is not time spent getting closer to it. What actually moves things is speed: getting the facts in front of someone qualified while an answer from them can still be useful. This guide will not tell you how much time that gives you, or whether you have any time left at all — that is a fact about your specific case, and it comes from documents and rules this guide cannot see. The asymmetry is the only part that holds in general: asking early costs a short message and someone else's attention. Waiting until you feel certain does not carry a cost this guide can put a number on, which is a reason to ask sooner, not a reason to keep reading until you feel ready. **Ask your TTO:** whether there's a faster route than the general inbox for something time-sensitive, and how you'd recognise you're in that situation before it has already happened. ## What this guide will not tell you This guide does not say whether anything you've done or have scheduled affects what can be protected, and it does not say that it doesn't. It does not say whether anything like a grace period exists anywhere, in any form, and it does not say that one doesn't. It does not tell you whether to file, delay, publish, or withdraw anything, and it does not tell you how much time you have, or whether a date on your calendar functions as a deadline. Those come from a patent attorney or your TTO, working from documents and rules this guide is not built to apply — not from a guide, however carefully written, and not from working it out yourself first. ## Turn this into your own case The [Publish/Protect Clock](/toolkit/publish-protect-clock/index.html) prompt kit turns this into two working documents: a dated calendar of everything connected to one piece of work that has already happened or is scheduled, built without scoring or ranking any of it, and then a short message that puts that calendar in front of your TTO or a patent attorney today. It runs as two prompts, one built on the other, in a single sitting. ## Related reading - [Is there a company here?](/guides/is-there-a-company-here.html) is the other guide on the shelf — a different decision, near this one on the same timeline, owned by a different body. - [Rights and Contribution](/toolkit/rights-and-contribution/index.html) is the companion kit for the question that often sits next to this one: who else touched the work, and what paperwork already attaches to it. --- ## Guide note - **Last verified:** 2026-08-31, by SpinUp Forge (Faraz Rizvi). - **Declared interest:** SpinUp Forge is a single-operator practice that does UK university spinout company-building, work that regularly begins at the point this guide describes. - **Corrections:** this guide is dated, not definitive, and it will be wrong somewhere before it is wrong everywhere. If something has changed, or was never right, tell us: [hello@spinupforge.com](mailto:hello@spinupforge.com). ## Changelog - **2026-08-31** — Moved the last-verified line, the declared interest and the changelog out of the guide's body and into these end notes. They are about the guide, not part of reading it. - **2026-08-31** — First version.