Student
Sees only their own applications.
- Pages
- Home, My applications, My documents, Key dates, Scholarships
- Can start
- New application, Upload a document
- Doesn’t see
- Reviews
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
A scholarship program asks a lot of students: an application, a personal statement, then weeks of waiting. It asks a lot of the committee too, with every application moving through review at once. Pory gives students one place to apply and see where they stand, and gives the committee a board of applications to move from review to award.
In plain English
Pory gives every student, committee member and coordinator a sign-in of their own. Each student sees only their own applications. It covers apply → review → award. Applications, reviews, documents, round dates and team live in Pory's own database, so there's no spreadsheet to keep in sync.
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 last name. 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 color-coded spreadsheet only one person understood. The coordinator sees every application as a card under Submitted, Committee review, Finalist, Awarded or Declined, and drags it along as the committee's scores come in. Anyone on the team can see how far along the round is 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.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own applications.
Sees every application in the portal.
Sees every application 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.
“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.
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 students.