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.
- Gantt Chart Planner
- Data model
The tables behind Gantt Chart Planner
Gantt Chart Planner ships with 14 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
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Project schedules
Projects links Organization and Owner to project dates, Budget and delivery method. Work packages belongs to Project and carries start date, end date, estimated hours and Owner.
Task dependencies
Tasks belongs to work package and can also reference Project and Assignee. Start date, due date, estimate hours, actual hours and percent complete describe work; depends on stores predecessor references as text.
Schedule baselines
Schedule baselines links work package and Organization to Revision, Status, planned hours, locked at, decision at and technical revision. Review decisions records subject type, subject reference, Decision, Reviewer and related project.
Capacity and time
Team members stores weekly capacity hours, role and practice. Time entries connects team member, Project and optional Task with work date, Hours, Billable and Status.
Milestones and risks
Milestones belongs to Project and records due date, Status and Owner. Risks holds probability, impact, mitigation and ownership, with recorded score and rating fields.
Issues and evidence
Issues links Project, raised by and Owner to severity and resolution state. Record attachments identifies its parent using parent table name and parent record ID. Operation receipts records operation type, Reference, Result and Actor.
Every table, by feature
- Project schedules6
- Task dependencies6
- Schedule baselines7
- Capacity and time7
- Milestones and risks7
- Issues and evidence7
- Shared and settings1
- 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 - Organizations
Client and internal business organizations that projects are delivered for.
- 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 - 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.
- Schedule baselines
Frozen schedule revisions submitted for approval against a work package, with dependency feasibility checks.
Linked to Work packages, Organizations - Issues
Defects and change items raised against project work.
Linked to Projects, Team members
- Schedule baselines
Frozen schedule revisions submitted for approval against a work package, with dependency feasibility checks.
Linked to Work packages, Organizations - Work packages
Groupings of work inside a project.
Linked to Projects, Team members - 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 - Organizations
Client and internal business organizations that projects are delivered for.
- 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
- 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 - Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - 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 - 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
- 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.
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - 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 - 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 - Record attachments
Files attached to delivery records.
Linked to Team members - 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 - Team members
Delivery staff with role, practice and weekly capacity.
Keys and references
The model contains 14 tables. Use actual record identifiers for reference fields and preserve source keys during migration. Tasks.depends on is text, so its task-key notation must be resolved consistently before building the dependency graph.
Issues, Risks and Milestones reference Projects but have no direct references to each other or to Tasks. Use the shared project context and agreed record keys in notes or descriptions to identify related concerns.
Projects and work packages expose hour and count rollups. Tasks and Risks also include calculated text fields. Verify their expressions and contributing records before treating a displayed value as a numeric input to another calculation.
Record attachments.parent table name uses display labels such as Work Packages and Time Entries; map those labels to the intended table before resolving parent record ID. Review decisions.subject reference and operation receipts.Reference also require an agreed reference convention. Team members and Users hold distinct identity records; configure the authenticated-person mapping used by assigned-work views.
Migration order
- Prepare identity and organizations. Establish platform Users and the delivery team members roster, then Organizations for the project context.
- Create project commitments. Import Projects with the correct organization and owner, followed by work packages with Project references.
- Load task work. Import Tasks, resolve package and assignee references, then validate depends on against the intended task graph.
- Preserve schedule revisions. Import schedule baselines with its package, organization and actual revision evidence. Retain genuine decision and lock times.
- Bring delivery tracking. Import Milestones, Issues, Risks and time entries with their correct project, task and team references.
- Retain evidence. Import review decisions, record attachments and operation receipts without changing original subject, parent or actor meaning.
Set up Gantt Chart Planner your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.