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.
- Event Planning PM
- Data model
The tables behind Event Planning PM
Event Planning PM ships with 10 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
- 10
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Organization and projects
Organizations own Projects and team members. Users supply the platform identity linked from team members.
Delivery
Work packages connects to Projects through Counterparty and to team members through Owner. Tasks belong to a parent package.
Readiness and evidence
Event readiness, record attachments, review decisions and operation receipts each link to work packages.
Every table, by feature
- Projects and organizations4
- Work packages5
- Tasks and dependencies3
- Event readiness3
- Evidence and decisions5
- Operations overview6
- Organizations
Client and operating organizations that own event planning engagements.
- Projects
Client event projects that work packages are delivered against.
Linked to Organizations - Team members
Planners, coordinators and reviewers with their organization membership and platform identity.
Linked to Organizations, Users - Users
Users
Linked to Users
- Work packages
Planned units of event delivery work with lifecycle, budget hours and revision control.
Linked to Organizations, Team members, Projects - Projects
Client event projects that work packages are delivered against.
Linked to Organizations - Organizations
Client and operating organizations that own event planning engagements.
- Team members
Planners, coordinators and reviewers with their organization membership and platform identity.
Linked to Organizations, Users - Tasks
Task lines inside a work package with planned and actual hours.
Linked to Work packages
- Tasks
Task lines inside a work package with planned and actual hours.
Linked to Work packages - Work packages
Planned units of event delivery work with lifecycle, budget hours and revision control.
Linked to Organizations, Team members, Projects - Team members
Planners, coordinators and reviewers with their organization membership and platform identity.
Linked to Organizations, Users
- Event readiness
Event readiness submissions and approvals for a work package.
Linked to Work packages, Organizations - Work packages
Planned units of event delivery work with lifecycle, budget hours and revision control.
Linked to Organizations, Team members, Projects - Organizations
Client and operating organizations that own event planning engagements.
- Record attachments
Evidence files attached to a work package with visibility and evidence type.
Linked to Work packages, Team members - Review decisions
Independent reviewer decisions recorded against a work package revision.
Linked to Work packages, Team members - Work packages
Planned units of event delivery work with lifecycle, budget hours and revision control.
Linked to Organizations, Team members, Projects - Tasks
Task lines inside a work package with planned and actual hours.
Linked to Work packages - Team members
Planners, coordinators and reviewers with their organization membership and platform identity.
Linked to Organizations, Users
- Work packages
Planned units of event delivery work with lifecycle, budget hours and revision control.
Linked to Organizations, Team members, Projects - Tasks
Task lines inside a work package with planned and actual hours.
Linked to Work packages - Event readiness
Event readiness submissions and approvals for a work package.
Linked to Work packages, Organizations - Review decisions
Independent reviewer decisions recorded against a work package revision.
Linked to Work packages, Team members - Operation receipts
Durable receipts for guarded operations with stable operation keys and result state.
Linked to Work packages - Record attachments
Evidence files attached to a work package with visibility and evidence type.
Linked to Work packages, Team members
Keys and references
Use organization and project codes consistently before importing packages. Keep work packages.record number stable for human handoffs. Tasks.line number and Revision identify task lines within the parent revision; Tasks.depends on records the dependency identity. Review decisions.source revision identifies the package revision decided. Operation receipts.operation key distinguishes a guarded action so repeated requests can be reconciled.
Migration order
- Import Organizations and Users.
- Link team members to their Organizations and Users.
- Import Projects under the correct Organizations.
- Import work packages with Owner and Counterparty references.
- Add Tasks, event readiness, record attachments, review decisions and operation receipts against their parent packages.
Set up Event Planning PM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.