Wedding planner client portal with checklists

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

4 of 9 done
  • Add a task

Choices we've asked you to make

Ceremony readingsOct 21, 2026To choose—
First dance songOct 24, 2026To choose—
Wedding carOct 26, 2026To choose—
Late-night foodOct 28, 2026To choose—
Hors d'oeuvres for cocktail hourOct 6, 2026ChosenBeet blinis, mini crab cakes, goat cheese tartlets
ConfettiOct 1, 2026ChosenDried delphinium petals

Showing 1–6 of 6

Powered by Pory

In plain English

How Pory sets it up

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

01

Couples check 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 (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.

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, 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.

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

CalendarDone by: Couple
04

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

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

Who sees what in a wedding client portal

Every person signs in to their own view. This is what each role in the demo gets.

Couple

Sees only their own vendors.

Pages
Home, Checklist, Payment schedule, My vendors, Files, Day of

Planner

Sees every vendor in the portal.

Pages
Home, Vendors, Weddings, Calendar, Payments, Couples' to-dos

What’s in the wedding client portal template

The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.

Vendors

  • Vendor (text)
  • Category (choice: Venue, Catering, Photography, Music, Florist, Cake, Hair & makeup, Transport)
  • Couple (link)
  • Fee ($) (number)
  • Status (choice: Shortlisted, Booked, Confirmed, Canceled)
  • Contact (text)
  • Day of (text)
  • Notes (long text)

Payments

  • Payment (text)
  • Vendor (link)
  • Due date (date)
  • Amount ($) (number)
  • Status (choice: Upcoming, Paid, Overdue)
  • Couple (link)

Planning checklist

  • Task (text)
  • Due (date)
  • Couple (link)
  • Done (yes/no)

Choices

  • Choice (text)
  • Needed by (date)
  • What to choose between (text)
  • Status (choice: To choose, Chosen)
  • Your choice (text)
  • Couple (link)

Weddings

  • Wedding (text)
  • Date (date)
  • Venue (text)
  • Guests (number)
  • Status (choice: Inquiry, Planning, Final details, Married, Postponed)
  • Couple (link)
  • Planner (link)
  • Day of (text)
  • What happens next (text)

Shared files

  • Title (text)
  • Kind (choice: Run of show, Floor plan, Mood board, Menu, Planning agreement)
  • Shared on (date)
  • File (file)
  • Couple (link)

Planning team

  • Name (text)
  • Role (text)
  • Phone (text)

The parts behind this portal

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

Decide

1 part
  • Checklists

    A task list on each record, ticked off in its detail view, with progress shown. Use it for onboarding, inspections or opening duties.

Share

2 parts
  • Tables

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

  • Calendar

    Records on a month or week view, by date.

Control

3 parts
  • Who sees which records

    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.

  • Passwordless sign-in

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

  • Your brand

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

Frequently asked questions

A couple signs in with a link sent to their email and lands on Home. They see Home, Checklist, Payment schedule, My vendors, Files and Day of, and only the vendors that are theirs.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your wedding client portal with Pory

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.

See pricing · How Pory builds a portal