My work orders
A facilities work order portal is where staff report a broken light or a leaking tap, the facilities manager assigns each order to a technician, and the technician works it to resolved. Whoever reported it follows progress on their own orders without calling the facilities office.
Pattern: RequestsDescribe it to Pory
“Staff across our two office buildings need to report facilities problems. Our facilities manager assigns each one to a technician, technicians see what's theirs, and whoever reported it can see progress.”
My work orders
In plain English
A facilities work order portal is where staff report a broken light or a leaking tap, the facilities manager assigns each order to a technician, and the technician works it to resolved. Whoever reported it follows progress on their own orders without calling the facilities office. 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 (staff member, facilities manager and technician) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
Faults reached facilities by email, a word in the lift and a sticky note on the broken printer, and a third never got written down. A staff member picks the building and floor, the kind of problem, describes it and adds a photo. The order lands as Reported with their name on it, ready for the facilities manager to hand out.
Work was handed out by shouting across the workshop, and nobody could say who had the Level 3 lights. The facilities manager opens an order and names the technician, and it lands on that technician's list; they move it to Resolved with a note on the fix. The board shows what's unassigned at a glance, so nothing sits in Reported for a week.
Technicians used to get a forwarded email chain and pick their jobs out from everyone else's. Each technician signs in to a list of only the orders assigned to them, with the location, category and photo on each. They stop scrolling past other people's work to find the leaking tap that's theirs.
The only way to find out about a broken heater was to email facilities again, which added one more message to the pile they were working through. Each order a staff member has reported shows as a progress bar from Reported to Resolved. They check their own page, and facilities spends the morning fixing things instead of answering "any update?"
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.