My applications
A scholarship program portal is where students apply for scholarships, a committee reviews each application, and the coordinator moves applications through review to an award or a decline. Each student sees where their own application stands.
Pattern: RequestsDescribe it to Pory
“Students apply for one of our three scholarships, a volunteer committee reviews every application, and our coordinator awards the winners.”
My applications
In plain English
A scholarship program portal is where students apply for scholarships, a committee reviews each application, and the coordinator moves applications through review to an award or a decline. Each student sees where their own application stands. 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 (student, committee member and coordinator) that shows only what that role should see, and flat pricing with unlimited students.
What it does
Applications used to arrive as a PDF form with the essay in a separate email, and the coordinator matched them up by surname. In Pory a student picks the scholarship, adds their school and what they plan to study, and writes their personal statement in the same form. Every application arrives whole, with the student's name already on it.
Knowing which applications the committee had finished meant a colour-coded spreadsheet only one person understood. The coordinator sees every application as a card under Committee review, Finalist, Awarded or Declined, and drags it along as the committee's reviews come in. Anyone on the team can see how far the round has got without asking.
Telling forty students the outcome used to take a mail merge and a nervous afternoon. The coordinator opens an application, reads the committee's reviews on it, and awards or declines, writing the reason on the record. A student who missed out gets a real answer, and the coordinator isn't rewriting it from memory in November.
Between the deadline and the results, the scholarships inbox used to be mostly "did you get my essay?" Each student signs in and sees only their own applications, and whether each one is with the committee, a finalist or decided. The office answers the question once, on the page, instead of forty times.
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
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
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.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
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.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited students, flat price.