A policy acknowledgment portal is where the people team publishes each policy as a file, every employee confirms they've read it by a deadline, and the team can see who hasn't yet. Anyone still outstanding gets a reminder as the deadline nears.
Pattern: RequestsDescribe it to Pory
“When we roll out a policy, every employee has to read it and confirm by a deadline. The people team needs to see who hasn't done it yet and remind them.”
Policies
| Policy | Category | Policy document | Effective from | Status | |
|---|---|---|---|---|---|
| Information security policy | Security | 1 file | 1 Oct 2026 | Published | |
| Code of conduct | Conduct | 1 file | 15 Sep 2026 | Published | |
| Hybrid working policy | Ways of working | 1 file | 15 Oct 2026 | Draft | |
| Workplace health and safety | Health and safety | 2 files | 1 Sep 2026 | Published | |
| Travel and expenses (old) | Finance | 1 file | 1 Sep 2026 | Retired |
Showing 1–5 of 5
In plain English
A policy acknowledgment portal is where the people team publishes each policy as a file, every employee confirms they've read it by a deadline, and the team can see who hasn't yet. Anyone still outstanding gets a reminder as the deadline nears. 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 (people team and employee) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
Policies lived as attachments on an all-staff email, so which copy people actually read depended on how far back they scrolled. In Pory the people team adds each policy with its category, effective date and the document itself, and marks it Published when it's live. Employees open the file in the portal instead of searching their inbox for "final".
Finding out who had read the new security policy meant cross-checking email read receipts against the staff list. In Pory each employee has a row per policy with a deadline and a status, so the people team filters to Outstanding and has the list in seconds. No more "reply all to confirm you've read this".
Chasing stragglers meant a string of increasingly polite all-staff emails. Each acknowledgment in Pory carries a deadline, and anyone who hasn't acknowledged yet gets a reminder in the portal and by email as the date approaches. The people team stops writing "gentle reminder" subject lines.
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 employees, flat price.
