Couple
Sees only their own vendors.
- Pages
- Home, Checklist, Payment schedule, My vendors, Files, Day of
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
| Ceremony readings | Oct 21, 2026 | To choose | — | |
| First dance song | Oct 24, 2026 | To choose | — | |
| Wedding car | Oct 26, 2026 | To choose | — | |
| Late-night food | Oct 28, 2026 | To choose | — | |
| Hors d'oeuvres for cocktail hour | Oct 6, 2026 | Chosen | Beet blinis, mini crab cakes, goat cheese tartlets | |
| Confetti | Oct 1, 2026 | Chosen | Dried delphinium petals |
Showing 1–6 of 6
In plain English
Pory gives every couple and planner a sign-in of their own. Each couple sees only their own vendors. It covers planning, vendors and payment schedule. Vendors, payments, planning checklist, choices, weddings, shared files and planning team live in Pory's own database, so there's no spreadsheet to keep in sync.
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 (final headcount, their vows for the officiant, the band's do-not-play list) and checks 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, fee 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 installment is due when the caterer calls. Each payment the couple owes a vendor sits on a calendar by its due date, marked upcoming, 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.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own vendors.
Sees every vendor 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
A task list on each record, ticked off in its detail view, with progress shown. Use it for onboarding, inspections or opening duties.
Search, filters, sorting, inline add and edit. The spreadsheet, minus the sharing accident.
Records on a month or week view, by date.
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 couples.