A nutrition and health coaching portal is where clients log their meals and weekly check-ins, and each coach reads the entries of their own clients and no one else's.
Pattern: TrackingDescribe it to Pory
“Our nutrition coaching practice wants clients to log meals and a weekly check-in, and each coach to see only the clients assigned to them.”
My log entries
| Entry | Date | Client | Type | Energy | |
|---|---|---|---|---|---|
| Overnight oats with berries | 23 Sep 2026 | Leila Farouk | Meal | Good | |
| Week 3 check-in | 21 Sep 2026 | Leila Farouk | Weekly check-in | OK | |
| Leftover dal and rice | 24 Sep 2026 | Leila Farouk | Meal | Good |
Showing 1–3 of 3
In plain English
A nutrition and health coaching portal is where clients log their meals and weekly check-ins, and each coach reads the entries of their own clients and no one else's. It follows the Tracking pattern: a person's or asset's history, built up over time. Pory generates it from a plain-English description, with a login for each role (client and coach) that shows only what that role should see, and flat pricing with unlimited clients.
What it does
Food diaries arrive as screenshots, WhatsApp photos of a sandwich, and a check-in email every other Sunday if the week went well. Clients log each meal and a short weekly check-in here, with the date, what they ate and how their energy held up. The coach reads a week of entries in one list instead of scrolling a camera roll.
In a shared spreadsheet every coach can scroll through every client's food diary, which is awkward for clients and a risk for the practice. Here each client is linked to one coach, and that coach's list shows only the people they work with, with each one's program, goal and stage. Adding a coach doesn't mean handing them the whole client list.
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 clients, flat price.
