Today's checks
Daily checks
2 of 5 done- Add a task
Restaurant & franchise ops portal
A restaurant and franchise ops portal is where each location works through its opening and closing checklists and logs incidents, and head office sees every location while each location sees only its own.
Pattern: ChecklistsDescribe it to Pory
“We run 12 franchise locations. Each location needs its opening and closing checklists and a way to log incidents like food-safety issues, and each location should only see its own while head office sees all of them.”
Viewing as
In plain English
What is a restaurant & franchise ops portal?
A restaurant and franchise ops portal is where each location works through its opening and closing checklists and logs incidents, and head office sees every location while each location sees only its own. 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 (location manager and head office ops) that shows only what that role should see, and flat pricing with unlimited franchisees.
What it does
Each location ticks off its opening and closing checks on a phone
Opening checks were a paper sheet on a clipboard by the pass, and by Friday it had a coffee ring and three missing days. The manager on shift works through the day's checks (fridge temps, sanitiser, allergen board, fryer oil) ticking each one off, with progress shown at the top. Head office stops asking for photos of the clipboard.
ChecklistsDone by: Location manager
Kitchens log a food-safety scare or a late delivery as it happens
Incidents reached head office in a Monday email, if the manager remembered, with half the details gone. The location manager picks the type (food safety, equipment, a complaint, an injury), adds when it happened, what went on and a photo. Each incident shows where it's up to, so head office follows up with the facts instead of a phone call asking what happened.
Forms to submit a recordDone by: Location manager
Each location sees its own incidents, head office sees all twelve
A shared spreadsheet meant every franchisee could read every other store's complaints and injuries, which nobody enjoyed. Each location manager signs in to their own location's incidents and checks, and head office sees every location side by side. Franchisees stop scrolling past another store's cool-room problems to find their own.
Role & row accessDone by: Location manager
The parts every portal is built from
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
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
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.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
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.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
More field service portals
All field service portalsField-service dispatch portalJob → assign → completeInspection reports portalChecklist → photos → defects assignedEquipment maintenance logs portalSchedule & historySafety incident reporting portalReport → investigate → closeCleaning & janitorial portalJob checklists & photo proofLandscaping & pool service portalService visits & each client's history
Your restaurant & franchise ops portal, live today.
Describe it in a sentence and send the invite. Unlimited franchisees, flat price.