Plenaria is a full peer-review and conference-operations platform — built for the moment a "submit a paper, assign a reviewer" spreadsheet stops being enough. Every workflow below is shipped, working, and running in production today — not a roadmap slide.
Legacy conference tools treat submissions, reviewer matching, integrity checks, and auditability as separate problems — often separate vendors. Plenaria treats them as one system.
Long Paper, Short Paper, Extended Abstract, Journal Paper, Concept Note, Presentation Only, and Poster Submission — seven types most platforms don't offer, so early-stage work and poster-only participants aren't forced into a full-paper template that doesn't fit them.
Automatic Assignment scores every reviewer's declared expertise against a paper's keywords, skips anyone with a detected conflict of interest, and spreads load across the committee — then shows you the full proposal to confirm before anything's created. Nothing is assigned blind.
Double-blind review is the starting state for every new submission, not a checkbox a chair has to remember to tick. Conflicts of interest — shared affiliation, shared email domain — are flagged automatically before an assignment ever happens.
Publication cross-check against Crossref, Semantic Scholar, and OpenAlex; an internal similarity pass across every submission in the conference; optional Copyleaks plagiarism scanning; and AI-content detection heuristics — all from the submission itself, no separate subscription to wire up.
Every conference gets its own permanent author and reviewer registration links — post them on your CFP page and people land straight in your conference, no invitation required. Already-registered reviewers get added instantly on invite, no accept/decline round-trip.
Every submission, edit, assignment, and recorded review lands in a single searchable Events table — actor, email, country, IP address, all timestamped in GMT0. When someone asks "who did this and when," the answer is a filter, not a database query.
Not every conference platform still on the market has kept pace with what a modern editorial workflow needs. Here's the gap.
| Capability | Plenaria by C-MRiC | Typical legacy CMT-style tool |
|---|---|---|
| Paper types | 7, incl. Concept Note & Poster-only | Usually 2–3, full-paper-centric |
| Reviewer assignment | Manual + automatic keyword/expertise matching with a confirm step | Manual only, or "bulk assign" with no matching logic |
| Conflict-of-interest detection | Automatic, flagged before assignment | Self-declared only, easy to miss |
| Blind review | On by default for every submission | Manual per-paper toggle |
| Originality checks | Cross-check + internal similarity + optional plagiarism + AI detection, built in | Usually none, or a separate paid add-on |
| Reviewer/author onboarding | Per-conference self-service links + instant direct-add for existing users | Chair invites one at a time |
| Audit trail | Full Events log — actor, email, location, IP, timestamped GMT0 | Little to none beyond a status field |
| Two-factor authentication | Required for admins, self-service optional for everyone else | Rarely offered at all |
| Multi-role accounts | Author, reviewer, and chair on one login, switch with one click | Often one role per account |
| Ownership | Self-hosted, source you control | Closed SaaS, vendor-dependent |
Every permission boundary in Plenaria is scoped to the specific conference a request touches — not "logged in as chair of something." That closes the class of bug that lets a bad actor create a throwaway conference and quietly inherit access to every other one on the platform.
Concept notes and posters alongside full papers. Reviewers matched by what they actually know. An audit trail that answers questions before they're asked. That's not a feature list — that's what running a conference on Plenaria looks like by default.