These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Wedding Planning Platform
- Data model and import order
The tables behind Wedding Planning Platform
Wedding Planning Platform ships with 11 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 11
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Events and Venues:
Events, Venues, Organizations, team members. Each event belongs to an organization, names a venue and an owning team member, and carries a version number.
Vendor Commitments:
Vendor commitments link a vendor booking to an event and organization with deadline, agreed fee and client approval.
Guest RSV ps:
Admissions hold reservation lines for an event with guest reference, party size, reserved and admitted times.
Payment Evidence:
Payment evidence keeps provider authorizations, captures, refunds and voids against an event.
Review Queue:
Review decisions record the decision, reason and reviewer against an event version.
Activity and Evidence:
Record attachments hold documents for an event; operation receipts record each guarded action and its outcome.
Access:
Users hold platform accounts; team members link each staff member to a user and organization.
Every table, by feature
- Events and Venues4
- Vendor Commitments4
- Guest RSVPs4
- Payment Evidence3
- Review Queue4
- Activity and Evidence4
- Shared and settings1
- Events
Wedding events with capacity, lifecycle and venue
Linked to Organizations, Team members, Venues - Venues
Wedding venues available to an organization
Linked to Organizations - Organizations
Wedding planning organizations operating the platform
- Team members
Staff members belonging to an organization
Linked to Organizations, Users
- Vendor commitments
Vendor commitment requests and approvals for an event
Linked to Events, Organizations - Events
Wedding events with capacity, lifecycle and venue
Linked to Organizations, Team members, Venues - Review decisions
Independent review decisions recorded against event revisions
Linked to Events, Team members - Record attachments
Supporting documents and evidence attached to events
Linked to Events, Team members
- Admissions
Guest admissions and RSVP reservations for an event
Linked to Events - Events
Wedding events with capacity, lifecycle and venue
Linked to Organizations, Team members, Venues - Payment evidence
Provider payment authorizations, captures, refunds and voids
Linked to Events - Operation receipts
Durable receipts for guarded operations executed on events
Linked to Events
- Payment evidence
Provider payment authorizations, captures, refunds and voids
Linked to Events - Events
Wedding events with capacity, lifecycle and venue
Linked to Organizations, Team members, Venues - Admissions
Guest admissions and RSVP reservations for an event
Linked to Events
- Review decisions
Independent review decisions recorded against event revisions
Linked to Events, Team members - Events
Wedding events with capacity, lifecycle and venue
Linked to Organizations, Team members, Venues - Vendor commitments
Vendor commitment requests and approvals for an event
Linked to Events, Organizations - Team members
Staff members belonging to an organization
Linked to Organizations, Users
- Record attachments
Supporting documents and evidence attached to events
Linked to Events, Team members - Operation receipts
Durable receipts for guarded operations executed on events
Linked to Events - Events
Wedding events with capacity, lifecycle and venue
Linked to Organizations, Team members, Venues - Team members
Staff members belonging to an organization
Linked to Organizations, Users
Keys and references
Every event keeps a stable record number, and every venue a code. Import reservations by event record number and guest reference, never by name. Keep the provider event identifier and reference on payment evidence so a repeated notification is recognized. Keep amounts in US dollars as recorded. Each operation receipt keeps a unique operation key.
The platform holds 11 tables and 16 relationships.
Migration order
- Load Organizations, Users and team members.
- Load Venues with codes, contacts and eligibility notes.
- Load open Events with record numbers, owners, venues and capacity.
- Load vendor commitments, then record attachments for each event.
- Load Admissions and verified payment evidence for paid events.
- Reconcile event counts, reservations against capacity and verified payments with the source before opening new reservations.
Set up Wedding Planning Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.