Speaker
Sees only their own talk proposals.
- Pages
- Home, My talk proposals, My materials, Key dates, Speaker guide
- Can start
- New talk proposal, Upload a file
- Doesn’t see
- Committee scores
A conference CFP portal is where speakers submit talk proposals, each program committee member files their own score on every proposal, and the program chair accepts or rejects each talk with a reason. Speakers see only their own proposals.
Pattern: RequestsDescribe it to Pory
“Our conference's call for papers takes talk proposals from speakers. Five committee members score each one, and the program chair accepts or rejects.”
My talk proposals
A call for papers lives or dies in the review: hundreds of talk proposals, a program committee scoring them in parallel, and speakers waiting to hear back. Pory gives speakers a form to submit to and a page to check, and gives each committee member their own place to score.
In plain English
Pory gives every speaker, committee member and program chair a sign-in of their own. Each speaker sees only their own talk proposals. It covers talk submissions & program committee. Talk proposals, committee scores, speaker materials, key dates and team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Proposals used to arrive as emails with abstracts pasted in three fonts, and the format was whatever the speaker forgot to mention. In Pory a speaker titles the talk, picks a track, a format and a level, and writes the abstract, then sees only their own proposals and where each stands. The chair stops copying abstracts into a spreadsheet at midnight.
Committee scoring used to be a shared spreadsheet with a column per reviewer and a lot of blank cells. In Pory each committee member opens a proposal and files a score out of 5, a recommendation and a note for the chair, as their own record on that talk. The chair opens any proposal and reads each reviewer's score in turn.
Rejections used to be a bcc'd form email that told speakers nothing about why. The program chair opens a proposal, reads each committee score on it, and accepts or rejects it, adding the reason to the record. Speakers who ask for feedback get the chair's actual words instead of a shrug.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own talk proposals.
Sees every talk proposal in the portal.
Sees every talk proposal in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
A reviewer's score, a coach's feedback, a clinician's note, kept on the record it belongs to.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited speakers.