All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Gantt Chart Planner · Available now

Keep project dates, dependencies and delivery decisions together.

Gantt Chart Planner connects project commitments to dated work packages and assigned tasks. Project Manager records the project organization, schedule, budget and delivery method, then breaks the work into packages with owners and task dates.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewActive Projects
Gantt Chart Planner · Projects

Active Projects

Projects in one list

New project
Projects in view
6
Active
3
At risk
2
On hold
1
Active3
RCR-26Riverside clinic renovation
01 Nov
CPL-26Community portal launch
12 Oct
TDS-26Transit depot safety program
30 Oct
Add
At risk2
EWM-26Eastport warehouse move
14 Oct
NCL-26North campus lighting upgrade
29 Oct
Add
On hold1
HBR-26Harbor branch refit
21 Oct
Add
RCR-26Projects · PRJ-61378
Active
Project nameRiverside clinic renovation
Start date01 Nov
End date10 Nov
OwnerNora Chen
OrganizationCitybend Transit Cooperative
Authorize the work packagePRJ-61378 · RCR-26

Delivery Lead reviews scope and staffing, then manually records an Approved, Rejected or Returned work-package decision; the baseline feasibility result remains separate.

Waiting for Delivery Lead
ApproveReturn
Example screen with sample data
Tables, ready to use
14
Saved views
16
Roles with set permissions
5
Reports and dashboards
10
Features

See the plan and the work behind it

Every feature works on the same records. Pick one to see the screen your team works in.

Project schedules

Turn a project commitment into dated work packages with named owners and visible delivery progress.

  • Project commitment
  • Package ownership
  • Delivery review
  • Projects
  • Work packages
  • Organizations
  • Team members
  • Tasks
  • Review decisions
Explore project schedules
OverviewCapacity by Member
Gantt Chart Planner · Project schedules

Capacity by Member

Team members

New
Full nameRolePracticeWeekly capacity hoursAssigned task countAssigned estimate hours
Iris NavarroDelivery LeadDelivery Management43012
Mateo OkaforProject ManagerEngineering16336
Asha PatelBusiness AnalystQuality Assurance12312
Lukas BergDeveloperDesign15292
Nora ChenQA EngineerData & Analytics768
6 of 6 records
Iris NavarroTeam members · TM-81249
Delivery Lead
PracticeDelivery Management
Weekly capacity hours4
Assigned task count30
Assigned estimate hours12
Assigned actual hours9
Example screen with sample data
Process

From project scope to controlled delivery

Project scope to controlled delivery ships ready to use. One step needs a named approval before the work moves on: Authorize the work package (Delivery Lead).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Scope the project

    Set the project commitment, organization and responsible owners.

    RCR-26PRJ-61378 · Project Manager
    Scope the projectBy Project Manager
  2. Plan task dependencies

    Connect assigned task dates with the work they depend on.

    RCR-26PRJ-61378 · Project Manager
    Plan task dependenciesBy Project Manager
  3. Check the baseline

    Check the task graph and retain the identified feasibility result.

    RCR-26PRJ-61378 · Project Manager
    Check the baselineBy Project Manager
  4. Authorize the work package

    Record the lead's decision after reviewing the checked plan and staffing.

    RCR-26PRJ-61378 · Delivery Lead
    Authorize the work packageBy Delivery Lead
    ApprovalDelivery Lead reviews scope and staffing, then manually records an Approved, Rejected or Returned work-package decision; the baseline feasibility result remains separate.
  5. Track delivery

    Keep task progress and actual work connected to the package plan.

    RCR-26PRJ-61378 · Project Manager
    Track deliveryBy Project Manager
  6. Review exceptions

    Turn overdue work, unverified fixes and open risk into an owned next action.

    RCR-26PRJ-61378 · Project Manager
    Review exceptionsBy Project Manager
Inside a record

Connect planning inputs and evidence

Open any project to see its issues, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Project name, Start date, End date and Owner.

  2. 2
    Issues

    Each line is linked to this project.

  3. 3
    Who works on it

    Admin, Delivery Lead and Project Manager, each with their own permissions.

  4. 4
    Process stages

    Scope the project and Plan task dependencies, with the role that acts.

  5. 5
    Approvals

    Authorize the work package, with who decides.

Active ProjectsRCR-26
Gantt Chart Planner · Projects

RCR-26

Riverside clinic renovation · Active

Log activity
1
Record details
Project nameRiverside clinic renovation
Start date01 Nov
End date10 Nov
OwnerNora Chen
2
Issues

RCR-26

Issue keyTitleSeverity
ISS-RCR-014Clinic panel access blockedCritical
ISS-EWM-021Racking layout conflicts with exitHigh
ISS-CPL-008Sign-in page misses screen reader labelMedium
Issues
6
3

Who works on it

  • AdminManage Organizations, team members, Users
  • Delivery LeadManage Projects, Risks, Milestones, review decisions
  • Project ManagerManage Projects, work packages, Tasks, schedule baselines…
4

Process stages

  • Scope the projectProject Manager, Delivery Lead
  • Plan task dependenciesProject Manager
5

Approvals

  • Authorize the work packageDelivery Lead
    Approved
Example screen with sample data
Approvals

Record the delivery commitment

Admin maintains organizations, team members and platform access. Resolve each person's operating identity before relying on an assigned-work view.

OverviewApprovals
Gantt Chart Planner · Overview

Approvals

Signed in as Delivery Lead

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • TE-28689Riverside clinic renovation
    Confirm warehouse racking planRequested by Leah Mensah
    Billable0dActions
  • TE-88905Riverside clinic renovation
    Survey clinic electrical roomsRequested by Lukas Berg
    Non-Billable2dActions
  • TE-41570Waterfront trail extension
    Train service desk leadsRequested by Jin Park
    Billable2dActions
  • TE-63813Harbor branch refit
    Map depot pedestrian routesRequested by Nora Chen
    Non-Billable3dActions

Who approves what

DecisionApprover
Authorize the work packageRecord the lead's decision after reviewing the checked plan and staffing.Delivery Lead
Approve work packagesDelivery Lead
2 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Gantt Chart Planner to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintain organization and team identity records and configure access for the delivery workspace.

  • Manage Organizations, team members, Users
  • View Projects, work packages, Tasks, schedule baselines, operation receipts, review decisions
Reports

Explain dates, workload and outcomes

Read schedule commitments, actual work and recorded decisions from their supporting delivery records.

Overview
Gantt Chart Planner · Overview

Gantt Chart Planner dashboard

This quarter

Time entries in view
6
Total hours
29
Billable
3
Non-Billable
3

Projects by status

How far records got this quarter

StageReachedStep
Planned43
Active1228%
On hold325%
At risk133%

Number of projects by status

Sample counts per stage

0
0Planned
-40Active
-60On hold
-20At risk
0Completed
Example screen with sample data
  1. 01Project delivery position

    Group Projects by Organization and Owner with Status, start date, end date, estimated hours, actual hours, logged hours and delivery progress percent.

  2. 02Work package hours

    Compare work package estimated hours with task estimate hours, task actual hours, hours variance and remaining hours while retaining the package's Project and Owner.

  3. 03Task dependency register

    List Tasks with task key, work package, start date, due date, depends on, Assignee and Status for dependency review.

  4. 04Baseline revision history

    Group schedule baselines by work package with Revision, Status, planned hours, locked at, decision at and technical revision.

  5. 05Team workload reference

    Show team member weekly capacity hours alongside assigned task count, assigned estimate hours, assigned actual hours and logged hours without treating undated assignment totals as a weekly allocation.

  6. 06Approved time by project

    Group time entries by Project, team member and work date, summing Hours where Status = 'Approved' and keeping Billable values separate.

  7. 07Milestone outcomes

    Group Milestones by Project and Owner with due date, Status and Notes to distinguish Pending, Met and Missed checkpoints.

  8. 08Risk exposure register

    List Risks with Category, Probability, Impact, probability score, impact score, Status, Owner and Mitigation alongside the recorded risk score and risk rating.

  9. 09Issue verification register

    List Issues with Severity, Status, reported date, Owner and reporter note to identify Fixed work awaiting verification.

Controls

Keep the checked plan identifiable

Each stage of project scope to controlled delivery names the role that acts and the status it records, so a change is never anonymous.

OverviewProject scope to controlled delivery
Gantt Chart Planner · Process

Project scope to controlled delivery

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
4
Tables touched
13
Check the baselineApproval
Project Manager
StatusDraft → Submitted
RecordsOperation receipts, Schedule baselines, Review decisions
Track delivery
Project Manager, QA Engineer, Developer
StatusPlanned → Active
RecordsWork packages, Projects, Tasks
Submit timeApproval
Developer
StatusDraft → Submitted
RecordsTeam members, Time entries, Projects
Project scope to controlled delivery
  1. Start
    Check the baselineDraft → Submitted
    Operation receipts
  2. Approval
    Authorize the work packageDelivery Lead
    Review decisions
  3. Step
    Track deliveryPlanned → Active
    Work packages
  4. Approval
    Submit timeDraft → Submitted
    Team members
  5. Step
    Triage issuesOpen → Triaged
    Operation receipts
Example screen with sample data
AI agent

Prepare schedule reviews with Proto

Ask Proto to prepare schedule reviews and explain delivery evidence within the team's authority.

It can

  • Project Manager: Summarize the task dates and predecessor references for a work package, then prepare the baseline submission for the intended revision.
  • Delivery Lead: Bring the checked schedule, staffing context and open risks together for a work-package decision, leaving the commitment judgment to the lead.
  • Developer: Show my assigned work and help prepare supported time entries against the correct project and task.
  • QA Engineer: List fixed issues awaiting verification and locate the evidence attached to each intended record.

Stays with a person

  • The assistant cannot invent a verified fix, decide that a milestone was met without evidence or make the lead's commitment judgment.
  • A dependency check establishes technical feasibility under its rules; the team still examines scope and staffing.
  • Assisted actions remain subject to the person's authority and the state of the records they affect.
  • Prepare identity and evidence access through Implementation before using assisted actions in the delivery cycle.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Gantt Chart Planner
  • Workforce identity
  • Calendar and planning sources
  • Document stores
  • Time sources
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 14 tables
14tables
  • Project schedules6
  • Task dependencies6
  • Schedule baselines7
  • Capacity and time7
  • Milestones and risks7
  • Issues and evidence7
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Choose the first commitment

    Select a project and work package with a clear outcome. Record the organization, dates, owner and delivery method before importing the detailed plan.

  2. Prepare team identity and access

    Admin establishes the team roster and authenticated-person mapping. Agree the responsibilities of Project Manager, Delivery Lead, Developer and QA Engineer using their actual operating identities.

  3. Build the task graph

    Load stable task keys, dates, estimates and assignees. Agree the predecessor notation, date boundaries and treatment of dependencies outside the immediate package.

  4. Check and authorize the plan

    Agree when a work package needs a recorded lead decision. Submit a baseline with its graph and inspect the feasibility result. Rehearse the agreed manual handoff, with Delivery Lead recording the decision after reviewing scope and staffing.

  5. Rehearse delivery evidence

    Update task progress, submit supported positive hours and run issue triage. Include invalid hours, a missing issue severity and a task fix that still needs verification.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Gantt Chart Planner.

All questions
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.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appGantt Chart Planner

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.