Platform integrations

Works inside the systems your editorial team already uses.

EditorialPilot doesn't ask editorial teams to learn a new system or toggle between platforms. Manuscript screening runs directly inside leading editorial systems such as Editorial Manager and ScholarOne — where decisions happen. Every check, every flag, every routing action stays within the workflow your team built its expertise in.

No retraining required
Results in the manuscript record
Configurable per journal title
One consolidated view

Every signal. One report. One decision point.

Editors don't switch between tools or reconcile separate reports. Every check — technical, language, integrity, rigor — flows into a single structured view. Editors see the evidence, weigh it, and route the manuscript. That's it.

  • Findings surface inside EM or ScholarOne — not in a separate portal
  • Every flag shows its source, the rule behind it and the recommended action
  • Editorial override available on every flagged item
Manuscript 2847 — consolidated screening report Live

ML in Clinical Diagnostics

Submitted via ScholarOne • 104 checks • Processed in 2m 14s
Pre-flight All files present, declarations complete Cleared
Language Score 68 — methods high edit density Author query
Integrity Image panel — duplication check recommended Review
Rigor Sample size justified, blinding absent Flag
Policy Ethics and COI statements present Cleared
Now embedded in these editorial workflow systems

Screening runs where editorial decisions already happen.

EditorialPilot is embedded directly inside Editorial manager and editorial manager , Scholar one and other leading platforms. — the same steps, the same manuscript record, the same workflow your team already runs.

em Editorial Manager®

Submission system — screening runs at point of intake

SCHOLARONE MANUSCRIPTS

Via Silverchair Relay API — automated screening at submission

HOW IT WORKS — SAME IN BOTH SYSTEMS

01

Manuscript submitted

Author submits through EM or ScholarOne as normal. No new portal, no separate upload step.

02

EditorialPilot activates

100+ checks run automatically against the journal's configured policy — technical, language and integrity.

03

Results in the manuscript record

Findings appear inside the submission system record — where editors already review submission details.

04

Editor routes the decision

Peer review, author query or desk decision — the routing call always stays with the editorial team.

Integration specifics

em Editorial Manager®

Checks run from initial submission through every revision and at post-acceptance. Results are visible inside the EM manuscript record at each stage. Configurable per journal title within the same EM instance — different thresholds, policies and required statements per title.

PARTNERSHIP
  • Live integration · Integra × Aries Systems
  • Covers submission, revision and post-acceptance stages
  • Per-journal configuration within a shared EM instance
SCHOLARONE MANUSCRIPTS

Built on ScholarOne's Relay API framework — EditorialPilot operates natively inside the platform, not alongside it. Results write back directly into the ScholarOne manuscript record. No file exports, no second login, no copying between systems.

PARTNERSHIP
Manuscript submitted Relay API triggers EP Results in S1 record
  • Live integration · Integra × Silverchair Universe
Built into the screening queue

Integrity, identity and quality partners.

Every partner integration feeds directly into the consolidated editor view — signals appear alongside pre-flight, language and policy checks in one place.

ORC iD

Author identity

Author identity and affiliation verification

Author declarations are verified against persistent ORCID identifiers. Inconsistencies in authorship, affiliation or contribution statements are flagged before the manuscript enters the editorial queue.

  • Persistent author identifier verification
  • Disambiguation of authors with similar names
  • Affiliation and contribution consistency check
Retracti n Watch

Publication integrity

Retracted citations surfaced at intake

Citations to retracted papers are cross-referenced against the Retraction Watch database during screening. Retraction signals appear in the manuscript record before reviewer assignment — not after a reviewer or reader spots them.

  • Real-time retraction database cross-referencing
  • Source and retraction reason shown with each flag
  • Signals appear inside the consolidated editor view
ORC iD

Image integrity

Image duplication detected before review

Automated image analysis runs against a global cross-manuscript database. Potential duplication or panel manipulation surfaces in the screening report before reviewer time is spent on a manuscript with unresolved image concerns.

  • Figure duplication and panel manipulation detection
  • Cross-manuscript image database matching
  • Visual evidence provided alongside the flag
iThenticate

Text similarity

Cross-manuscript image database matching

Publisher-grade text similarity analysis runs at submission. Similarity score and source-level match breakdown appear inside the consolidated editor view — alongside all other manuscript signals, not in a separate report editors have to retrieve separately.

  • Similarity score against global academic database
  • Source-level match breakdown for editorial review
  • Threshold configurable per journal policy
SciScore

Rigor and reproducibility

Research rigor gaps flagged before peer review

SciScore assesses whether a manuscript's methods reporting is sufficient for a reviewer to evaluate and reproduce the work. Randomization, blinding, sample size justification and resource identification are checked and surfaced in the consolidated editor view.

  • Randomization, blinding and sample size reporting
  • RRID verification for materials and resources
  • NIH, MDAR and ARRIVE framework assessment
winston ai

AI-generated content

AI-text indicators, section by section

Section-level AI-text probability scores appear in the consolidated view. Editorial teams get structured evidence to act on and document — applied consistently across every submission, regardless of who handles it.

  • Section-level AI probability scoring
  • Evidence for editorial review, not an automated
  • flag Same standard applied across every submission
Custom APIs

Custom APIs

Journal-specific checks configured per title

Reporting checklist compliance — CONSORT, PRISMA, ARRIVE — house metadata rules, portfolio-specific submission requirements. Custom checks feed results into the same consolidated view as every other integration.

  • Publisher-specific policy rules and metadata checks
  • Reporting checklist integrations per article type
  • Results in the same consolidated editor view
Ready to go further?

See how Editorial Pilot handles your submission queue.

Bring a sample workflow, journal policy or intake problem. The demo can focus on your editorial office, production handoff or portfolio model.

What a session covers

  • Map checks to one journal policy you bring
  • Review a live manuscript flag report
  • Walk through the Editorial Manager and Scholar One integration
  • Discuss governance, override rights and audit setup
Request demo