My talk proposals
Conference CFP portal
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.”
Viewing as
In plain English
What is a conference CFP portal?
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. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (speaker, committee member and program chair) that shows only what that role should see, and flat pricing with unlimited speakers.
What it does
Speakers pitch a talk in one form with track, format and level
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.
Forms to submit a recordDone by: Speaker
Every committee score is filed on the proposal, reviewer by reviewer
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.
Notes & scores on a recordDone by: Committee member
The program chair accepts or rejects each talk with a reason attached
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.
Approve / reject with a reasonDone by: Program chair
The parts every portal is built from
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
More applications portals
All applications portalsGrant round portalApplications & reviewer scoringScholarship program portalApply → review → awardAccelerator & incubator portalStartup applications & cohortsResearch & IRB review portalProtocol submission & approvalPermit & license applications portalSubmit → review → issueRFP & bid responses portalSubmission & evaluationGrantee reporting portalMilestone reports & disbursementsMunicipal service requests portalReport → assign → fixed
Your conference CFP portal, live today.
Describe it in a sentence and send the invite. Unlimited speakers, flat price.