Applicant
Sees only their own applications.
- Pages
- Home, My applications, Round dates, Guidelines
- Can start
- New application
- Doesn’t see
- Reviews
A grant round portal is where community groups apply for funding, each reviewer files their own score on every application, and the program officer awards or declines with a reason. Applicants follow their own application's status instead of emailing to ask.
Pattern: RequestsDescribe it to Pory
“We run a small-grants round for community groups. Groups apply online, three volunteer reviewers score every application, and our program officer awards or declines each one.”
My applications
A small foundation's grant round is a short, busy cycle: the call opens, applications arrive, reviewers score them, the committee awards or declines, and every applicant wants to know where they stand. Pory puts that cycle in one portal. Applicants apply and follow their status, each reviewer files their own score on the application, and every decision goes on the record with its reason.
In plain English
Pory gives every applicant, reviewer and program officer a sign-in of their own. Each applicant sees only their own applications. It covers applications & reviewer scoring. Applications, reviews, round dates, attachments 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 Word documents in three different templates, and someone retyped each budget figure into a spreadsheet. In Pory a group fills in the project, organization, focus area, amount and its case for funding, and the application goes straight to the review panel with their name on it. Nobody chases a missing budget line by email again.
Reviewers used to fill in copies of one scoring spreadsheet, and last round two of them saved over each other. In Pory each reviewer opens an application and files their own review: a score out of 5, a recommendation and notes, kept as a separate record on that application. The program officer opens it and reads each reviewer's view in turn.
Decisions used to live in board minutes and a follow-up email nobody could find by March. The program officer opens an application, reads the reviews, and awards or declines it with the reason written onto the record. When a group asks why they missed out, the answer takes one click, not an afternoon in the inbox.
Every round used to bring a week of "just checking you got our application" emails. Each applicant signs in and sees only their own applications and where each one stands: In review, Shortlisted, then Awarded or Declined. The program team gets that week back and spends it reading proposals.
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.
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 applicants.