Event planning portal

An event planning portal is where each client sees their own events and ticks off the planning tasks that are theirs, while the planner keeps each event's vendors in one list.

Pattern: Client hubs

Describe it to Pory

“Our event planning company wants each client to see their own events and the tasks they owe us, and our planners to keep track of the vendors booked for each event.”

Viewing as

Vendors

Vendors

Add
VendorCategoryEventContactStatus
The FoundryVenueBrightwave Q4 sales kickoffHattie LoweConfirmed
Salt & Ember CateringCateringBrightwave Q4 sales kickoffDominic ReyesBooked
Lumen AVAVBrightwave Q4 sales kickoffKris NovakEnquired
Wild Stem FloralsFloristChen and Alvarez 25th anniversaryBeth AldridgeConfirmed
Harbour HouseVenueChen and Alvarez 25th anniversaryIvan PetrovConfirmed
Northside CoachesTransportHartley School galaPaula GrantCancelled

Showing 1–6 of 6

Powered by Pory

In plain English

What is an event planning portal?

An event planning portal is where each client sees their own events and ticks off the planning tasks that are theirs, while the planner keeps each event'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 (client and planner) that shows only what that role should see, and flat pricing with unlimited clients.

What it does

01

Planners keep each event's vendors in one searchable list

Vendor details are scattered across email chains, a spreadsheet tab per event and the planner's phone. Here each vendor is a row against its event, with the category, the contact, the load-in date and whether they're booked or confirmed, searchable and editable in place. Finding the florist for Saturday takes a search, not a scroll through last month's emails.

Tables to manage recordsDone by: Planner
02

Clients tick off the planning tasks that are theirs to do

The client's to-dos (final headcount, speaker bios, dietary requirements) get buried in a long email that ends "let me know if you have any questions." Each task sits on the client's list with a due date against its event, and they tick it off when it's done. The planner stops chasing the headcount by email.

ChecklistsDone by: Client
03

Each client signs in to their own events and no one else's

A shared folder means hoping nobody clicks into the wrong event, and every status update is another email. Each client signs in to see their events (the date, the venue, guest numbers and how far along planning is) and nothing belonging to another client. Rachel sees Brightwave's kickoff and customer dinner, not the anniversary party booked the same week.

Client-only accessDone by: Client

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 event planning portal, live today.

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