Location manager
Sees only their own incidents.
- Pages
- Home, Today's checks, My incidents, Documents, From corporate
- Can start
- Log an incident, New incident, Upload a document
A restaurant and franchise ops portal is where each location works through its opening and closing checklists and logs incidents, and corporate 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 corporate sees all of them.”
Today's checks
In plain English
Pory gives every location manager and corporate ops a sign-in of their own. Each location manager sees only their own incidents. It covers checklists & incident logs. Incidents, daily checks, documents, corporate visits, bulletins, locations and corporate team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
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, sanitizer, allergen board, fryer oil) checking each one off, with progress shown at the top. Corporate stops asking for photos of the clipboard.
Incidents reached corporate 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 stands, so corporate follows up with the facts instead of a phone call asking what happened.
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, checks and documents, and corporate sees every location side by side. Franchisees stop scrolling past another store's walk-in cooler problems to find their own.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own incidents.
Sees every incident in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
A task list on each record, ticked off in its detail view, with progress shown. Use it for onboarding, inspections or opening duties.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited franchisees.