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
- Frequently asked questions
Questions, answered
Understand dependency feasibility, baseline decisions and the evidence used to review delivery work.
Gantt Chart Planner
10 questions
Can't find it? Write to support@erp.ai.
How do I get started?
Click Get started, then use Proto to configure Gantt Chart Planner for your business. Begin with a bounded project and work package whose owners can rehearse dependency checks, a delivery decision and an unresolved exception.
How are projects and work packages connected?
The project records the wider commitment and organization. Work packages belong to that project and carry their own owner, dates and estimated hours. Tasks connect the package plan to assigned delivery work.
What does the baseline check examine?
It checks the submitted task graph for circular dependencies, missing predecessor references and impossible finish-to-start dates. A feasible submission becomes Approved and is frozen; an infeasible submission becomes Rejected.
Who decides whether the team should use the checked plan?
Agree during setup when the team needs a recorded work-package decision. Delivery Lead reviews scope and staffing and records that decision. Keep the human commitment separate from the automated dependency-feasibility result.
How should we read team capacity?
Compare weekly capacity with tasks dated for the relevant planning period. A person’s total assigned estimate may span several weeks, so inspect the underlying assignments before deciding where work needs adjustment.
What happens to submitted time entries?
The time-entry workflow checks that hours are positive and the entry is still Submitted. Eligible entries are approved with decision and operation evidence; a failed condition blocks approval and records the failed attempt.
What makes an issue ready for triage?
The existing issue must be Open and have a severity. The workflow moves eligible work to Triaged and records the result. A changed state or missing severity stops the action.
How do we keep reported fixes visible?
Use Unverified Fixes and Exception Triage to find issues marked Fixed that still need a verification result. QA Engineer checks the actual outcome and supporting evidence before recording Verified.
What happens when a milestone is missed?
Record the actual outcome and notes, retain the original checkpoint and inspect its effect on the work package. Review risk mitigation and prepare a revised baseline when the task plan changes.
What should we prepare before rollout?
Gather project commitments, stable task identities, predecessor conventions, team capacity and evidence examples. Use Implementation to rehearse identity mapping, feasible and rejected schedules, time-entry guards and issue verification.
Set up Gantt Chart Planner your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.