Apply
Applications & interview stages
An applicant tracking portal is where candidates apply through a public form, recruiters move each one through interview stages on a board, and interviewers file their scores on the candidate's record.
Pattern: RequestsDescribe it to Pory
“We're hiring for a few roles. Candidates should apply on a public page, recruiters move them through screening and interviews, and each interviewer adds a score and notes.”
Apply
Applications & interview stages
In plain English
An applicant tracking portal is where candidates apply through a public form, recruiters move each one through interview stages on a board, and interviewers file their scores on the candidate's record. 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 (recruiter and interviewer) that shows only what that role should see, and flat pricing with unlimited candidates.
What it does
Applications came in through a jobs inbox, LinkedIn messages and the occasional CV handed to reception. In Pory candidates fill in one public form — the role, their email, why they want it, and their CV — without making an account. Each application lands in the Applied column, and nobody forwards CVs around with "thoughts?" any more.
Knowing who was at which stage meant a spreadsheet with colour-coded rows and a recruiter's memory for the rest. In Pory each candidate is a card in Applied, Phone screen, Interview, Offer or Rejected, and the recruiter drags it along after each conversation. Hiring managers stop asking where their shortlist has got to.
Interview feedback trickled in by Slack message days later, if at all, and half of it was "seemed good". In Pory each interviewer sees the candidates assigned to them and files a scorecard with a 1–5 score, a recommendation and notes, linked to the candidate. The recruiter opens the candidate and reads each scorecard in one place.
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 candidates, flat price.