For conference organisers, chairs and programme committees
Submissions, double-blind peer review, decisions, camera-ready and registration in one system built for academic operations — not generic forms.
Move an existing conference across in a day.
Proceedings export formats
Publisher names identify the proceedings export formats CMS supports. They are not partnerships, endorsements or indexing guarantees.
Organisers and authors work from opposite ends of the same record — one CFP, one submission, one review trail. Pick the end you are on.
Organiser · Chair
Propose it, open the call, build the programme, publish the proceedings.
Author · Reviewer
Find an open call, submit, track the decision, upload camera-ready.
Four connected stages, one platform. Scroll to move through them.
Multi-step submission wizard with PDF validation, co-author management, and track selection.
Switching systems part-way through a conference sounds like a way to lose a review round. It is not. Below is what an export actually carries across, which parts we do for you, and what the two days after approval look like.
You do not have to wait for the current round to close. Whichever phase you are in — bidding, reviewing, decisions, camera-ready — is the phase your workspace opens in, and authors keep the submission they have already made.
Exports we work from
Assisted, not automatic
There is no one-click connector. You send the export your current system produces — CSV, Excel, or an archive of submissions — and we map it onto CMS fields, load it into your conference while it is still private, then hand you the counts to check against your old dashboard: papers, reviewers, assignments, decisions. Whatever the export leaves out is named before you commit, not discovered afterwards.
Committee and reviewer lists
Names, emails, affiliations and topic interests. You approve the roster before a single invitation is sent.
Tracks and topic taxonomy
Track names, their chairs, and the keyword list authors choose from when they submit.
Submissions and their metadata
Title, abstract, authors, affiliations, keywords, track and the paper file — one record per submission.
Review assignments and conflicts
Who is reviewing what, plus declared conflicts of interest, so bidding does not start over.
Completed reviews and scores
Scores, recommendations and reviewer comments stay attached to the paper they were written for.
Decisions already issued
Accept, reject and revise keep their date and their decider. A round you have closed stays closed.
Branding, CFP text and deadlines
Entered once in the conference request. These are the fields no export gives you in a usable shape.
What happens once a conference request is approved. Only the first step waits on us — platform admins review requests within one business day. Everything after it is self-serve and moves at your pace.
Step 1 — performed by Platform
Workspace created
Approval assigns you the Organiser role and opens the conference workspace. Organiser, track chair, reviewer and author views all point at it.
Step 2 — performed by You
Tracks and deadlines set
Add tracks and their chairs, then set abstract, full-paper, review and camera-ready dates. Those dates drive the submission form and the author reminders.
Step 3 — performed by You
Committee invited
Upload or paste your programme committee. Every invitation carries its role, so nobody signs up into the wrong permission set.
Step 4 — performed by Automatic
Call for papers live
Your CFP publishes at a shareable link anyone can read, and which opens the submission form directly for signed-in authors.
Step 5 — performed by Authors
Submissions open
Papers arrive in the right track with their metadata already structured. Assignment and bidding begin whenever you open them.
The call for papers publishes at /c/<id> — one link for the mailing list, the society site and the poster. Visitors read the conference page; signed-in authors land straight in the submission form.
Running a conference here means unpublished manuscripts and unblinded reviewer identities sit on our infrastructure. These are the controls that govern them — written as what the platform does, not as badges.
Author identities are withheld from reviewers and reviewer identities from authors for the whole review round. Conflicts of interest are checked at the moment an assignment is made, not after a review has already landed.
Researcher, Reviewer, Meta Reviewer, Track Chair, TPC, Organiser and Super Admin, each scoped to a single conference. Permissions are checked by the API on every request — hiding a control in the interface is never the access decision.
Actions on submissions, reviews and decisions are written to an audit log with the actor, the target and the time. A contested acceptance can be reconstructed from the record instead of argued from memory.
Export submissions, reviews, decisions and registrations whenever you want them — there is no exit fee and no export request queue. Manuscripts are held in private object storage and are never served from a public URL.
Reviewers answer a structured form rather than writing loose prose, meta-review lets a chair reconcile disagreement into one recommendation, and assignment shows current load so no reviewer silently carries the round.
Health checks and error tracking run against the API continuously, and the database is on a scheduled backup. We quote the current backup and recovery policy in writing rather than printing an uptime figure on a marketing page.
Certifications
This page makes no compliance claim. ResnDevs CMS is not certified against SOC 2 or ISO 27001, and we would rather say so here than let you find out during procurement. Institutional security questionnaires and data processing agreements are handled directly with your team.
Hand-picked conferences from the platform showcase.
International Conference on Electrical, Computer & Communication Engineering
International Conference on Machine Learning and Large Language Models
International Conference on Networking & Communication Engineering
IEEE Region 10 Humanitarian Technology Conference
National Conference on Innovations in Management
Bangladesh Engineering Student Conference
One price covers the whole run — call for papers through to proceedings. Not per seat, not per month, and not renewed while your conference is dormant. Tell us the shape of your programme and you get a written quote back.
A single-track symposium or society meeting run by a small committee.
Quoted per cycle
Scoped on programme size and how long the cycle runs.
A full multi-track conference with parallel sessions and paid registration.
Quoted per cycle
Scoped on tracks, submission volume and registration handling.
Everything in Society, plus
A university or society running several conferences under one account.
Quoted per cycle
Scoped on how many conferences run in a year.
Everything in Conference, plus
Send your dates, track count and expected submission volume. Migrating an existing conference from another system is part of the same conversation, not a separate project.
How the platform behaves today — pricing, data ownership, review integrity and what survives after the last session. Nothing below is a roadmap item.
Something specific to your venue, committee or publisher? Send the detail and you get a direct answer, not a demo booking.
Start here
Organisers send a structured proposal — title, tracks, dates, deadlines and CFP — and the conference workspace opens once it is approved. Authors and reviewers only need an account.
For organisers and programme chairs. You will be asked to sign in first.
For authors and reviewers submitting to a call that is already open.