Module
Abstracts & Review.
Collect submissions, run rubric-based reviews, and publish decisions — without email chaos or spreadsheets.
Pricing key
module:mod_abstracts
Modules are priced independently — enable only what you need.
Abstracts pipeline
Submission → rubric → decision
Submission
A randomized trial of outcome‑based scheduling for day‑of ops
418 words2 attachmentsTrack: Ops
We propose an end‑to‑end workflow for building schedules, verifying attendance, and publishing updates in real time — without PDF exports or spreadsheet merges.
Author message
“Happy to revise. We can also provide source data for reproducibility.”
Reviewer portal
Rubric scoring
Novelty
4/5
Clarity
5/5
Methodology
4/5
Impact
5/5
Reviewer note
“Strong operational contribution, clear methodology, nice practical framing.”
Interactive demo — hover or tap.
Quick win
A real submission portal
Collect abstracts properly (not by email): forms, attachments, deadlines, and clear status.
Quick win
Review without spreadsheets
Give reviewers a focused portal with rubrics and scoring.
Quick win
Fair and consistent evaluation
Rubric-based scoring keeps reviews structured and comparable.
Quick win
Decisions you can trust
Keep committee work organized and communicate outcomes confidently.
What it helps you do
Capabilities in plain steps
- Open a call-for-abstracts with clear rules and deadlines.
- Collect submissions in a consistent format, with optional attachments.
- Let submitters track status without emailing your team.
- Support reviewer assignments and keep the workload manageable.
- Score with rubrics so decisions are consistent and auditable.
- Turn accepted work into the program later (when you’re ready).
Who it’s for
Built for humans
Scientific/program committee
You need a structured way to collect, review, and decide on submissions.
Reviewers
You want a clean interface to score and comment, without juggling documents.
Presenters
They need a simple portal to submit, upload, and track progress.
How it works
Configure → run → publish (optional)
Step 1
Configure the call
Set deadlines, guidelines, and what information submitters must provide.
Step 2
Collect submissions
Presenters submit through the portal and can see their status.
Step 3
Review and decide
Reviewers score using rubrics and the committee finalizes decisions.
Standalone
Use this module by itself
- Run abstracts end-to-end even if you don’t enable scheduling yet.
- Perfect for conferences that finalize decisions before building the program.
- Keep reviewer work organized with structured rubrics.
Integrated
Or connect it to the stack
- Legacy Website installs can link “Submit Abstract” and host guidelines PDFs.
- Event turns accepted abstracts into sessions and tracks.
- Badges/Attendance support on-site identity and verification for presenters.
Scenarios
What this unlocks
University research symposium
Students and faculty submit abstracts, reviewers score, committee publishes outcomes.
Multi-track scientific conference
Structured rubrics help keep review fair across different study types.
Late-breaking submissions
Run a separate window and keep everything organized and consistent.
Integrations
Built to compose
Website (Legacy)
Existing legacy sites can put “Submit Abstract” in navigation and host guidelines on the event domain.
Explore →
Event & Logistics
Use accepted abstracts as inputs to build the schedule.
Explore →
Badges & Check-in
Support presenter identity and on-site access when you’re ready.
Explore →
Attendance & Verification
Support verified participation flows when attendance evidence matters.
Explore →
FAQ
Common questions
Can presenters edit after submitting?
You can run a submission window so edits are allowed during that period and then locked after closing.
Do reviewers get a separate portal?
Yes. Reviewers work in a dedicated review experience focused on rubric-based evaluation.
Can we start with Abstracts and add scheduling later?
Yes. Many teams finalize decisions first, then enable Event to build the program from accepted work.
Do we still need guideline PDFs?
If your community expects them, you can host them alongside your submission flow so everything stays in one place.