My applications
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
In plain English
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. 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 (applicant, reviewer and program officer) that shows only what that role should see, and flat pricing with unlimited applicants.
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, organisation, 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.
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 applicants, flat price.