Checklist
Checklist items
3 of 5 done- Add a task
An inspection report portal is where inspectors work through each site's checklist item by item, log the defects they find with photos, and the site manager assigns every defect to a contractor. Contractors see only the defects assigned to them.
Pattern: ChecklistsDescribe it to Pory
“Our safety inspectors walk 12 sites a month. They need to work through a checklist on each inspection and log defects with photos, and the site manager assigns each defect to a contractor to fix.”
Checklist
In plain English
An inspection report portal is where inspectors work through each site's checklist item by item, log the defects they find with photos, and the site manager assigns every defect to a contractor. Contractors see only the defects assigned to them. 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 (inspector, site manager and contractor) that shows only what that role should see, and flat pricing with unlimited inspectors.
What it does
Inspections ran off a laminated sheet on a clipboard, and someone typed the ticks into a report back at the office. On site, the inspector works down the checklist (extinguishers in date, exits lit, racking undamaged) ticking each item as they go, with progress shown at the top. Nobody retypes a clipboard at 5pm, and a skipped item is obvious.
Defect photos sat in the inspector's camera roll, and matching them to the right site a week later was guesswork. The inspector logs each defect with its photos, the inspection it came from and how severe it is. The site manager and the contractor open the defect and see exactly what the inspector saw, down to which bay has the dented upright.
Defects went into a PDF report, and the site manager then emailed each contractor their share and hoped they read page nine. The site manager opens a defect, names the contractor, and it lands on that contractor's list with the photos and severity. Contractors see only what's theirs, and the critical ones stop waiting at the bottom of a PDF.
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 inspectors, flat price.