Manuscript Submission System Development: Submissions, Reviewers, and Decisions

What this project is

Manuscript submission is the front door of publishing, and email is a poor front door. Manuscripts arrive in inboxes, attachments are renamed, reviewers are invited by memory, and decisions are communicated in threads that nobody can reconstruct later. Authors ask for updates that take hours to answer, and editors cannot tell which manuscripts are awaiting review.

A submission system gives every manuscript one record, with its files, reviews, revisions, and decisions linked to it. Submission forms enforce the publication's rules at upload, reviewers are matched from a database with workload and expertise, and decisions are recorded with reasons and sent from the system.

Core features

The features below focus on submission control and decision history, not on generic file uploads.

• Submission forms with required fields, file types, and publication rules
• Submission records with manuscript versions, authors, and correspondence
• Reviewer database with expertise, workload, and response history
• Reviewer invitation and tracking with deadlines and reminders
• Editorial decision records with reasons, sent to authors from the system
• Revision workflow linking revised manuscripts to the original submission
• Author views showing submission status and decisions for their manuscripts
• Reporting on submission volume, review times, and decision outcomes

How it is built

Start with one publication and its real submission rules, before adding further publications.

1. Build submission forms and records for one publication
2. Add reviewer database and invitation tracking
3. Build editorial decision workflow with author communication
4. Add revision handling linked to original submissions
5. Add author views and reporting
6. Add more publications once the first workflow is steady

Technology considerations

Keep one submission record per manuscript, with versions, reviews, and decisions linked to it. If manuscripts live in email and reviews in separate files, the submission history cannot be reconstructed, and an author query becomes a search through inboxes. Submission-linked records make the history complete.

Enforce submission rules at upload, not at review. A manuscript missing required fields or in the wrong format wastes reviewer time and delays decisions. Form checks at submission return incomplete manuscripts immediately, with clear reasons, so authors can correct them before review starts.

Challenges and how to handle them

• Submissions are lost in email — solve it by holding one submission record per manuscript, with files and correspondence linked.
• Submission rules are not enforced — solve it with submission forms that check required fields and file types before acceptance.
• Reviewers are hard to find — solve it with a reviewer database showing expertise, workload, and past performance.
• Decisions are not communicated clearly — solve it by recording decisions with reasons and sending them from the system.
• Revised manuscripts are confused with originals — solve it by versioning submissions, with revisions linked to the original.

Who it is for, and honest limits

This project fits publishers, journals, and conference organisers receiving many manuscripts. It also fits firms whose submission handling is done by email and loses track of manuscripts. Start with one publication and its real submission rules.

It does not fit a publisher receiving a handful of manuscripts a year by direct contact, or a firm that does not run a submission process. It also does not replace editorial judgement. Cost depends on submission volume, publication types, and workflow complexity, so confirm with a quote. A useful first version can be judged by a simple test: can an editor see, for any manuscript, its status, its reviewers, and its decision history, from one record? Submission workflows should also be reviewed after each volume, so form fields that confuse authors are simplified before the next intake. Editors should also monitor submission completeness rates, since a high return rate usually signals unclear submission guidance rather than careless authors.

Frequently asked questions