STM’s Innovation & Integrity Days (9-10 Dec 2025) in London were framed as a multi-stakeholder conversation, but a lot of what was discussed lands directly on editorial offices: managing editors, journal coordinators, assistant editors and publisher-side integrity staff. This isn’t just about high-level policy, it’s about how submissions are screened, how editors are supported, and how conversations with authors and reviewers are going to change.
Here’s what the two days signal for people working on the ground.
- Integrity tools are becoming part of core workflow, not an optional add-on
The Innovator Fair made one thing very clear: the tools are converging on the editorial desk.
Systems like the STM Integrity Hub, DataSeer, Smart Publish, PubShield, Enago Reports, ReviewerZero and others are all pushing toward the same pattern: one embedded view of multiple integrity signals, rather than five different logins and exports. For editorial offices this means:
- More signals on each manuscript (images, text, references, data, identity, networks).
- Fewer standalone dashboards, more integration into systems like Editorial Manager, ScholarOne and the like.
- A shift from “should we run this check?” to “how do we interpret this combined report?”
On the desk, this changes the job from doing checks to triaging them. You’ll need:
- Clear SOPs for what to do with specific patterns of flags.
- Thresholds for when to escalate to research-integrity specialists.
- Templates for neutral, factual queries to authors about technical findings.
The technology is the start; the real work is designing consistent responses around it.
- Checks will move earlier and go deeper
Several sessions – on the Integrity Hub, image/data authenticity, and the sleuths’ work – pointed in the same direction: pre-publication is where the real defence has to happen.
For editorial teams this likely means:
- More pre-submission or pre-review screening (plagiarism, duplication, image anomalies, strange references, “AI nonsense” language).
- More frequent requests for original images and underlying data, not just prettier figures.
- Stronger expectations that journals know what they will and will not accept as “provenance”.
You should expect author guidance to tighten. Instructions for authors will need to be clearer about:
- What editors and offices will ask for in problematic cases
- How images and data should be stored so that provenance can be shown
- What happens if authors cannot or will not supply originals
For support staff, the practical impact is more back-and-forth before peer review even starts, with more technical documentation attached to each case.
- Identity checks are coming – and may help more than they hurt
The digital identity discussions were blunt: publishing runs millions of articles a year with almost no “know your customer” equivalent.
Static affiliation is no longer enough. Shell institutions, exaggerated affiliations and identity spoofing are all in play. At the same time, there are serious experts working outside traditional academia who struggle to enter editorial workflows because they lack a neat university label.
For editorial teams, the likely direction is:
- More structured identity verification at certain points (e.g. new corresponding authors, guest editors, reviewers from unknown institutions).
- More use of ORCID, institutional attestations and simple ID checks to reduce spoofing.
- Possible TSA pre-check style “lanes” where higher-assurance identities enjoy fewer manual checks.
There was also a useful reality check: in daily life, people already accept identity checks everywhere – banking, smartphones, even renting an e-scooter. Relative to that landscape, asking for basic ID assurance around work that influences patient care, public policy and now AI training data is hardly extreme.
Your role will likely include:
- Explaining calmly why extra checks are being introduced.
- Ensuring any new ID workflows are documented and applied consistently.
- Watching for equity issues – for example, how new requirements affect authors without strong institutional backing.
- Provenance isn’t abstract – it will change how you handle images, data and supplements
The “authenticity of images and data” sessions were clear: we are not going to win an arms race against future image and data fakery by detection alone. As AI-generated content improves, some manipulation will be practically undetectable.
Editorially, this shifts focus from “spot the fake” to “prove the workflow”. That means:
- Treating original images, lab metadata and data files as normal parts of the submission ecosystem, not rare exceptions.
- Taking supplementary materials more seriously: they are where many critical data now live, and where LLMs will mine heavily.
- Being ready to ask, “Where did this image/data come from? Can we see the unedited version? Do we have enough to be confident?”.
Several ideas that may reach the desk:
- Journals asking for signed or registered originals in higher-risk fields.
- Data-focused reviewers (perhaps postdocs?) involved alongside traditional peer review.
- Badges or indicators in articles where provenance checks have gone beyond the minimum.
For staff, this means more file handling, more liaison with production and more judgement calls about when “enough provenance” has been demonstrated.
- Working with institutions and sleuths will need structure, not ad hoc goodwill
Panels on publisher–institution collaboration and the “session with the sleuths” exposed real friction:
- Institutions see publishers as slow or opaque.
- Publishers see institutions as unresponsive or defensive.
- Sleuths see both as under-resourced and often silent after detailed reports.
For people inside editorial workflows, there are three practical implications:
- Case handling needs clearer channels
- Know who handles serious integrity cases in your organisation.
- Know how and when to contact institutions (and what not to send).
- Keep a clean audit trail: dates, decisions, communications.
- Sleuth reports need visible triage
- Acknowledge receipt promptly.
- Log reports in a trackable system.
- Close the loop where possible (even if the outcome is “no action, here’s why”).
- Backlog management will move from “nice to have” to expectation
- Tools that find articles citing retracted work are here.
- Editorial offices may be asked to support back-catalogue sweeps, not just new submissions.
- You’ll need criteria for what gets investigated first.
The message from sleuths was straight-up: if publishers want their help, they need to show that it leads somewhere.
- Policy frameworks are under strain – you will feel that at case level
Guideline bodies and cross-publisher initiatives are updating retraction guidance, expressions-of-concern policies and support for editors under pressure. At the same time, we are seeing on the ground that the volume and sophistication of fraud is testing procedures designed for a now bygone era.
On the ground, this shows up as:
- Long, complex casework in resource-hungry conditions.
- Risk/reward of following industry best practice called into question.
- Grey areas where existing policies say little (paper mill adverts, recycled images).
- Pressure from multiple directions: authors, institutions, sleuths, media, internal leadership.
The emerging direction may well be:
- Keep due process and fairness, but
- Develop faster tracks for situations with clear, well-documented evidence.
- Be explicit about which pathway a case is on, and why.
Editorial staff may not write the policies, but you will enforce them, document them and explain them repeatedly. Expect more attention to internal training on this.
- What skills and behaviours will matter most?
Across both days, a pattern emerged of what the system increasingly needs from editorial teams:
- Triage, not just task execution
Ability to interpret multi-signal reports and make sensible calls about escalation. - Calm, precise communication
Neutral, factual language in difficult emails to authors, reviewers and institutions. - Comfort with tools and data
Not coding, but understanding what image, text and data checks can and cannot tell you. - Process literacy
Knowing your own policies, where they’re strong, and where they’re silent – and documenting decisions accordingly. - Resilience and boundaries
Integrity work carries emotional load: accusations, counter-accusations, legal threats. You’ll need support and realistic workloads, not heroics.
The upside: the work is becoming more visible and more valued. The downside: it is also becoming more complex.
In summary
The STM Innovation & Integrity Days didn’t just showcase new tools or restate familiar principles. They described a future where research integrity is baked into every stage of the editorial workflow: who you accept manuscripts from, what you ask for, how you route signals, and how you interact with institutions, funders and sleuths.
For editorial professionals, this is not a bolt-on extra; it is the next evolution of the role. Calls from the stage for substantially increased investment in research integrity teams were met with clear, audible approval from a senior audience. That’s a signal: organisations know they need more capacity at the coal face. For anyone looking to deepen or reorient their career around integrity, there is likely to be more demand, more responsibility and, over time, more formal roles in this space.



