Revise
All of Revise

Revise[Submit]

submit.revise.id

Complete manuscript submission and peer review management.

Handle the entire editorial workflow from initial submission through peer review to final decision. Designed for journal editors who need a reliable, transparent system for managing scholarly manuscripts.

How a manuscript moves through Revise[Submit] A flow in two rows. Top row, peer review: the manuscript is submitted, reviewers are assigned, and reviews are returned. An editorial decision — accept, revise, or reject — then leads to the bottom row, the revision round: revisions are requested, the author returns a new version, and the manuscript is accepted. DECISION accept · revise · reject 01 02 03 04 05 06 PEER REVIEW REVISION ROUND Submission Reviewers assigned Reviews returned Revisions requested New version Accepted
Rounds repeat until the manuscript is accepted or declined, and nothing leaves the system between stages. Acceptance hands the article straight to Revise[Production].

Key features

Everything you need for manuscript management.

Guided Submission Portal

Authors submit manuscripts through an intuitive multi-step form with file uploads, metadata extraction, and co-author management.

Peer Review Management

Assign reviewers, set deadlines, track responses, and manage multiple review rounds with full audit trails.

Editorial Decision Tracking

Editors can accept, reject, or request revisions with structured decision letters and automatic notifications.

Multi-Round Revisions

Support unlimited revision rounds with clear tracking of changes between manuscript versions.

Role-Based Access

Configurable roles for editors-in-chief, section editors, reviewers, and authors with granular permissions.

Journal Configuration

Manage multiple journals with independent settings, submission types, and review workflows.

Contacts & communication

The people behind the workflow, in the same system.

Peer review is only as good as the reviewer pool behind it. Contact management, segmentation, and outreach are built into Revise[Submit] rather than living in a separate tool you have to keep in sync.

Contact & Reviewer Database

One record per person — affiliations, subject areas, and review history — held in the same system that assigns them.

Smart Segments

Group the pool by subject area, activity, or any recorded field, and reuse those groups when inviting reviewers.

Email Campaigns

Send calls for papers and reviewer invitations from the journal's own address, with every send recorded against the contact.

Engagement Scoring

See who accepts, who declines, and who has gone quiet, before sending another invitation.

A real record

One manuscript, from submission to acceptance.

Submitted

The manuscript arrives through the portal with its metadata and files, and enters the editorial queue.

Revised

The author returns a new version after peer review, tracked against the version it replaces.

Accepted

The decision closes the round, and the article crosses to Revise[Production] with its metadata intact.

Editorial history of Laila et al., Green and Sustainable Environments 1(1), 2026 — printed on the published article and verifiable at 10.62755/gsenv.2026.01. One article's record, not a service-level claim — review length depends on the manuscript and the reviewers, not on the software.

Workflow

From submission to decision.

01

Submission received

The manuscript arrives through the guided portal with metadata, files, and co-authors captured up front.

02

Reviewers assigned

Editors triage, invite reviewers from the contact database, and set deadlines for each invitation.

03

Review

Reviewers work to a structured form; responses, declines, and silence are all visible in one place.

04

Decision

Accept, reject, or request revisions, with a structured decision letter and automatic notification to the author.

05

Revisions

The author returns a new version. Changes are tracked against the previous round rather than replacing it.

06

Final decision

Rounds repeat as the manuscript needs. Acceptance hands the article to Revise[Production] with its metadata intact.

After acceptance

Revise[Production]

JATS XML production, author proofreading, and publication-ready output — picking up exactly where Revise[Submit] leaves off.

See Revise[Production]

Ready to try Revise[Submit]?

An email that reaches someone who works on this. If Revise is not the right fit for your journal, we would rather tell you that early.

hello@revise.id
usually answered within one working day