Checklist
Planning checklist
1 of 4 done- Add a task
A wedding client portal is where each couple works through their planning checklist, sees their vendors and a calendar of payment due dates, and the planner keeps every couple's vendors in one list.
Pattern: Client hubsDescribe it to Pory
“Our wedding planning business wants each couple to have their own checklist, vendor list and a calendar of when each vendor payment is due, with our planners seeing all couples.”
Checklist
In plain English
A wedding client portal is where each couple works through their planning checklist, sees their vendors and a calendar of payment due dates, and the planner keeps every couple's vendors in one list. It follows the Client hubs pattern: one shared space per client: deliverables, documents, milestones. Pory generates it from a plain-English description, with a login for each role (couple and planner) that shows only what that role should see, and flat pricing with unlimited couples.
What it does
The wedding checklist starts as a printout on the fridge and ends up split across three notes apps. The couple sees their own to-dos with due dates (guest numbers, readings, the band's do-not-play list) and ticks each one off. The planner sees what's outstanding without sending another "just checking in" email.
A wedding means six or more vendors, each in its own email chain that the planner searches at midnight. The planner keeps one list across couples, with each vendor's category, contact and whether they're shortlisted, booked or confirmed, and edits it in place. Checking which vendors are still unconfirmed for October takes one filter.
Due dates hide in PDF contracts, so couples learn the catering instalment is due when the caterer rings. Each payment the couple owes a vendor sits on a calendar by its due date, marked upcoming, due this week, paid or overdue. They still pay each vendor as the contract says; they just stop finding out late.
A shared planning spreadsheet shows one couple another couple's vendors and prices, which nobody agreed to. Each couple signs in and sees only their own vendors, payments and checklist, while the planner sees them all. Nadia can check her caterer's details without scrolling past someone else's quote.
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 couples, flat price.