Built in A verified double-blind review, with the conflicts checked for you
Your congress runs on four systems that don't speak to each other.
Registration, payment, submissions and a verified double-blind review, in one place — with a single record for the person who is author, reviewer and committee member all at once.
- No contract
- You keep the merchant account
- 8% all-in, card processing included
The whole invoice. Card processing is inside it.
Record per person, whatever roles they hold.
Conflicted pairings offered to a reviewer.
To clone last year into the next edition.
How a paper moves
From the author's upload to the committee's decision
Nothing below asks you to move a file between two systems. That is the entire product.
- 1Author
Registers, pays and submits
In the same sitting, declaring every co-author on submission.
- 2Engine
Crosses the declarations
A conflicted pairing is never offered — and neither side learns who the other is.
- 3Reviewer
Reads blinded, scores the rubric
Only their assigned papers, with the authors' names searched out of the text before it reaches them.
- 4Committee
Decides, on the record
Every step is a plain sentence in the trail, and the decisions reach authors when you send them.
Built for committees with no administrator
Everything a scientific committee does, in one system
The platform checks conflicts, so the jury never has to
Reviewers declare their conflicts once. Authors declare every co-author on submission. The assignment engine intersects the two and simply never offers a conflicted pairing — without either side learning who the other is.
One person. One record. Every role.
Dr. Ferreira submits to session B, reviews for session C and sits on the organizing committee. She is one row in your database, not three in three systems.
The fifteenth edition takes an afternoon
Clone last year: sessions, fee tiers and periods, rubrics, certificate templates, and the reviewer pool you spent three months assembling.
When nobody is left, it says so — and why
A small jury and honest declarations will do this. Borrow from another session or invite a new reviewer; both keep the exclusions intact.
Pricing
Eight percent. That is the whole invoice.
Card processing is inside the eight, not on top of it. A registrant paying from Tokyo with a converted currency costs you exactly what one paying from Lisbon costs you.
- Free registrations — your jury, your invited speakers, your own committee — cost nothing at all.
- No contract. You keep the merchant account.
- The example beside this is computed by the same code that settles a real charge.
A registration paid with a domestic card
Set it up once, in an evening. Clone it every year after that.
Nothing to install, no contract, and your existing payment account.