Calendar
A tutoring service portal is where tutors schedule each session on one calendar and set assignments against it, and students tick off their homework before the next lesson.
Pattern: TrackingDescribe it to Pory
“I run a small tutoring business. I want to schedule sessions with each student and set assignments they can tick off between lessons.”
Calendar
In plain English
A tutoring service portal is where tutors schedule each session on one calendar and set assignments against it, and students tick off their homework before the next lesson. 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 (student and tutor) that shows only what that role should see, and flat pricing with unlimited students.
What it does
A tutoring week used to be a chain of texts: is Thursday still on, was it four or half past? In Pory the tutor adds each session with the student, subject and time, and it lands on a calendar marked scheduled, done or cancelled. Students stop scrolling back through messages to find out when chemistry is.
Homework set at the end of a lesson tended to survive as a scribble in the back of an exercise book. In Pory the tutor adds each assignment to the session it came from, and the student ticks items off their own list as they go. The next lesson opens with what's done, not "so, did you get to it?"
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 students, flat price.