Wedding client portal

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 hubs

Describe 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.”

Viewing as

Checklist

Planning checklist

1 of 4 done
  • Add a task
Powered by Pory

In plain English

What is a wedding client portal?

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

01

Couples tick off wedding to-dos and the planner sees what's outstanding

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.

ChecklistsDone by: Couple
02

The planner tracks every couple's vendors from shortlist to confirmed

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.

Tables to manage recordsDone by: Planner
03

Couples see each vendor payment on a calendar by its due date

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.

CalendarDone by: Couple
04

Each couple signs in to their own wedding, not the planner's diary

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.

Client-only accessDone by: Couple

The parts every portal is built from

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

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Record pop-up & linked records

A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the rows a viewer is allowed to read.

Control

Role & row access

Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.

No-Password Doors

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

On purpose

Four things Pory won’t do

A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.

Take payments

Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.

Book time slots

Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.

Host the conversation

No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.

Plan routes

Pory keeps the service record, not the map.

Frequently asked questions

Your wedding client portal, live today.

Describe it in a sentence and send the invite. Unlimited couples, flat price.