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.
- Meeting Management
- Data model and import order
The tables behind Meeting Management
Meeting Management ships with 13 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
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Project context:
Organizations, Projects, team members. Keep organization and staff references stable across meeting work.
Meeting work:
Meetings, agenda items, action items. Meetings belong to a project; actions link to a meeting; agenda topics link to the project.
Hours and follow-through:
Attendance, follow ups, Risks. Submitted hours link to project and team member, while raised issues and risks keep their project owners.
Review evidence:
Decisions, operation receipts, record attachments. Review outcomes and operation results remain distinct from current source status.
Access:
Users. Map people to their permitted work during setup.
Every table, by feature
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Meetings
A meeting held for a project: when it starts and ends, the organizer, its status, and the action items and agenda items it produced.
Linked to Projects, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Agenda items
Agenda entries planned for a project, with the date they are due to be covered and whether they were met or missed.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Action items
Actions captured in a meeting, each with an owner, a due date and a status tracked through to completion.
Linked to Meetings, Team members, Projects - Meetings
A meeting held for a project: when it starts and ends, the organizer, its status, and the action items and agenda items it produced.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Attendance
Attendance recorded by a team member against a project or action item and submitted for approval.
Linked to Team members, Projects, Action items - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Action items
Actions captured in a meeting, each with an owner, a due date and a status tracked through to completion.
Linked to Meetings, Team members, Projects - Team members
Delivery staff with role, practice and weekly capacity.
- Decisions
Decisions recorded against a meeting or project subject, with the reviewer, the outcome and the date.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Follow ups
Follow-ups raised from meeting and project work that still need an owner, a decision or verification.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members
- Decisions
Decisions recorded against a meeting or project subject, with the reviewer, the outcome and the date.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Record attachments
Files attached to delivery records.
Linked to Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
Keys and references
Use project and team member identifiers consistently when importing records. An action items record needs its Meeting reference; agenda items and follow ups need their Project reference. Attendance needs its team member, Project and work date. Keep the Decisions subject reference and operation receipts reference consistent with the source identifiers so reviewers can reconcile an approval or triage attempt. Review the reference alongside each source record and its current status.
Migration order
- Load Organizations, team members and Users.
- Load Projects with their organization and owner references.
- Load Meetings and agenda items for the correct project.
- Load action items against Meetings; then load Attendance, follow ups and Risks against their existing references.
- Load Decisions, operation receipts and record attachments with their original source references, then reconcile the status lists.
Set up Meeting Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.