Describe the problem you would like to solve
Our editors need a way to return a submission to the author for technical corrections before peer review, without starting a review round.
Many journals run a technical or desk check before review: keyword count, reporting checklists such as PRISMA or CONSORT, table and figure order, ORCID, anonymisation of files and metadata. Often the outcome is simply “return to author for corrections.” In the Submission stage, however, OJS only offers three decisions: Send for Review, Accept and Skip Review, and Decline Submission. “Request Revisions” and the author’s Revisions upload area exist only inside a review round.
The current workarounds both have drawbacks:
- Pre-review discussion. The author can attach corrected files, but they are not formal revisions. The submission status doesn’t show that it is waiting for the author, and the editor has to pick the discussion files manually when sending for review.
- Send for Review with no reviewers, then Request Revisions. This creates a proper revision upload, but the record then shows a review round that never involved reviewers, and the status reads “In Review” although review hasn’t started. This misleads authors and distorts statistics.
Describe the solution you’d like
- A “Request Revisions” (or “Return to Author” or ‘‘send back to author’’) decision in the Submission stage, with its own editable email template for technical corrections.
- A revision upload area for the author in the Submission stage, with a distinct status such as “Awaiting author revisions (pre-review)”.
- A notification to the assigned editor when revised files are uploaded, with those files pre-selected in the Send for Review dialog.
- Optionally, pre-review returns reported separately from review-based revision requests in editorial statistics.
Who is asking for this feature?
Journal Editors and Section Editors, who handle the desk check; Journal Managers and editorial office staff, who run technical screening; and Authors, who need a clear status and a proper place to upload corrected files.
Additional information
Pre-review technical screening is standard practice at many journals and is increasingly done with automated pre-screening tools, whose typical outcome is “return to author.” A native decision would make the process transparent for authors and keep the review history accurate. We use OJS 3.5.0.1. If this has already been discussed or is on the roadmap, a link to the relevant thread or GitHub issue would be appreciated.