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.
- Capacity Planning Dashboard
- Data model
The tables behind Capacity Planning Dashboard
Capacity Planning Dashboard 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
Portfolio and scope
Organizations holds client and internal business identities. Projects links Organization and Owner, with start date, end date, Budget, delivery method and Status.
Team capacity
Team members records Role, Practice, weekly capacity hours, Region, practice lead and Active. Assignment and effort summaries include assigned estimate hours, assigned actual hours and logged hours.
Work packages
Work packages belongs to Project and names Owner, start date, end date and budget hours. Task estimate hours and task actual hours support the package comparison.
Task workload
Tasks requires work package and can link Assignee and Project. Start date, due date, estimate hours, actual hours, percent complete and Status describe the assignment.
Time and effort
Time entries requires work date, Hours, team member and Project; Task is optional. Billable and Status keep time classifications distinguishable.
Delivery exceptions
Issues, Milestones and Risks each link Project and can name an Owner. Issues tracks Severity and Status; Milestones tracks due date and Status; Risks retains Category, Probability, Impact and Mitigation.
Decisions and evidence
Review decisions uses subject type, subject reference, Reviewer and related project. Operation receipts stores operation type, Reference, Result and Actor. Record attachments uses parent table name and parent record ID with file metadata.
User identity
Users holds platform-user information. Reconcile Users.Email and team members.Email during access setup, and test the configured identity mapping used for personal assignments.
Every table, by feature
- Portfolio and scope6
- Team capacity6
- Work packages5
- Task workload7
- Time and effort6
- Delivery exceptions8
- Shared and settings1
- Organizations
Client and internal business organizations that projects are delivered for.
- 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.
- Work packages
Groupings of work inside a project.
Linked to Projects, Team members - Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Record attachments
Files attached to delivery records.
Linked to Team members
- Team members
Delivery staff with role, practice and weekly capacity.
- Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Work packages
Groupings of work inside a project.
Linked to Projects, Team members - Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members
- Work packages
Groupings of work inside a project.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Team members
Delivery staff with role, practice and weekly capacity.
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects
- Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Work packages
Groupings of work inside a project.
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.
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - Record attachments
Files attached to delivery records.
Linked to Team members - Issues
Defects and change items raised against project work.
Linked to Projects, Team members
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - Team members
Delivery staff with role, practice and weekly capacity.
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Issues
Defects and change items raised against project work.
Linked to Projects, Team members - Milestones
Dated checkpoints a project must meet.
Linked to Projects, Team members - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Work packages, Team members, Projects - Team members
Delivery staff with role, practice and weekly capacity.
- Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Record attachments
Files attached to delivery records.
Linked to Team members
Keys and references
Preserve each record identity and reference target during migration. Do not replace work packages.Project or Tasks.work package with a display-name match. Check that an optional Tasks.Project link agrees with the intended package project.
Textual evidence references need explicit resolution. Record attachments.parent table name uses display labels such as Work Packages and Time Entries; map them to work packages and time entries when resolving parent record ID. Review decisions.subject type supports Project, Work Package, Task, Milestone and Deliverable. Resolve subject reference under the chosen type and keep related project consistent.
Operation receipts.Reference is text, so verify the target for each operation type. Review calculated and rollup fields against source records during setup, including hours variance, delivery progress percent, risk score and risk rating.
Migration order
- Access and people. Establish Users and team members, then configure and test identity mapping and access.
- Organizations and portfolio. Import Organizations and Projects with the intended organization and owner links.
- Delivery structure. Import work packages before Tasks, preserving their project and assignee references.
- Delivery concerns. Import Milestones, Issues and Risks with valid project and owner links.
- Time and evidence. Import time entries, then review decisions, record attachments and operation receipts with resolved references. Reconcile historical states before enabling live actions.
- Summary checks. Compare task and time detail with the project, package and person summaries used in the pilot.
Set up Capacity Planning Dashboard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.