JEMS handles submission, peer review, decisions, production and your public archive — deployed as a dedicated instance for your journal, on your domain, with your branding and your mail.
In production across four peer-reviewed journalsSeven editorial rolesEditor-in-Chief approval gate
Most journals outgrow email long before they replace it. JEMS takes over the three places it usually breaks.
Manuscripts arrive as email attachments and live in one person’s inbox.
Authors submit through a dashboard. Co-authors confirm by email before the paper moves, files land in your storage numbered and routed, and the editorial office sees it the moment it arrives.
Nobody is quite sure who agreed to review, or when it was due.
Reviewers accept or decline from an emailed link, report against a structure you can compare, and stay in a pool that gets more useful with every issue you publish.
Decisions are assembled in a spreadsheet and sent by hand.
An associate editor’s recommendation waits in the Editor-in-Chief’s queue until it is approved, overridden or sent back. Every state change is a timestamped event on the manuscript.
Not a submission form bolted to a website. The whole editorial operation, including the unglamorous half.
Site name, journal name, domain and every outgoing email template are yours, editable from the admin desk without a deploy. Nothing on the page sells our software to your authors.
Assignments, reports, decisions, overrides and withdrawals are written to a timestamped event log against the manuscript. Months later you can still show who did what, and when.
Each revision pushes the previous manuscript into an append-only history before the new one takes its place — so the file a reviewer actually read is still the file you can open.
Camera-ready files, signed copyright forms, volume and issue assignment, DOI and a public, searchable archive of everything you have published — on your own domain.
Two-factor sign-in with an emailed-code fallback, enforced after five logins. Permissions are checked at the route, at the session and at the query — all three have to agree.
Scheduled backups, an automated health report and an uptime heartbeat on a quarter-hour cycle — so if something needs attention, you hear it from us before you hear it from an author.
Every paper occupies exactly one state at a time, and each move between states is an event with an actor, a timestamp and a reason.
Author submits; co-authors confirm by email before the paper moves.
The editorial office checks scope and can desk-reject before review starts.
An associate editor assigns reviewers; reports return scored and on a clock.
Minor or major, with a response letter — earlier versions are kept.
The recommendation waits for the Editor-in-Chief to approve or override.
Camera-ready file, copyright form, volume, issue and DOI.
Open in your public archive, searchable by title, author, keyword or DOI.
No per-seat surprises and no bolt-on modules. A person can hold several roles and switch between them; the system grants only what the active role may see.
The desk that holds the pen. Every recommendation an associate editor makes lands in one queue to be approved, overridden or sent back — so nothing reaches an author in your journal’s name until you have signed it.
JEMS is deployed once per journal. That is not a pricing tier — it is how the system is built, and it is why your authors never see anyone else’s brand, and your records never sit in a table beside another journal’s.
We set the instance up with you rather than handing over a login and wishing you luck.
We walk your current workflow: who screens, who assigns, who signs a decision, and what your authors see.
Domain, database, file storage and mail are provisioned for your journal alone and connected end to end.
Journal name, site name and every outgoing email — invitation, reminder, decision — set in your own words.
Open submissions. Your editors work the queue while the first manuscripts arrive, with us on hand.
Yes. Each journal is deployed as its own instance with its own domain, journal name and site name. Those names appear through the interface and in every email that goes to your authors and reviewers.
Completely. Every journal gets its own database, its own object-storage bucket and its own mail credentials. There is no shared tenancy and no other journal’s records sitting next to yours.
Yes. Invitations, reminders, consent requests and decision letters are all templates you can edit from the admin desk — no deploy, no developer, no waiting on us.
No. A reviewer can accept or decline straight from the emailed link. They only create an account when they go on to file a report, and their expertise and CV then stay on file for future issues.
Yes. A user holds a set of roles and switches between them, and the system only ever grants what the role they are currently acting as is entitled to see.
Tell us what you are holding and in what shape — spreadsheets, another system, an inbox — and we will agree an import route with you before you switch over, rather than leaving you to re-key it.
Tell us how your journal runs today and we will show you the same workflow inside JEMS — with your name on it.
new.technology@hotmail.com · jems.my