Leaving tasks
Leaving tasks
1 of 4 done- Add a task
An offboarding portal is where IT and managers work through each leaver's checklist — revoking access, wiping laptops, handing over accounts — and every piece of company equipment stays on a list until it's back.
Pattern: ChecklistsDescribe it to Pory
“When someone leaves, IT and their manager each have tasks to finish, like revoking access and collecting the laptop. We need a checklist per leaver and a list of the equipment still to come back.”
Leaving tasks
In plain English
An offboarding portal is where IT and managers work through each leaver's checklist — revoking access, wiping laptops, handing over accounts — and every piece of company equipment stays on a list until it's back. It follows the Checklists pattern: the same task list, worked through again and again. Pory generates it from a plain-English description, with a login for each role (IT and people team) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
Offboarding lived in an email chain that opened with "Sofia's last day is Friday" and ended with her still in Salesforce a month later. In Pory each leaver gets their own copy of the leaving checklist, and IT sees the tasks assigned to them — revoke access, wipe the laptop — and ticks each one as it's done. Nobody finds a former colleague still signed in to the CRM.
Getting kit back from leavers relied on someone remembering what was issued two years ago. In Pory each item sits against the leaver with its asset tag, a return-by date and a status — Due back, Returned, Wiped or Lost — and IT updates it as the courier bag arrives. The phone that walked out the door is spotted before the leaving drinks.
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, in its detail view, 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.
Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the records a viewer is allowed to see.
Control
Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up 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.
Describe it in a sentence and send the invite. Unlimited employees, flat price.