Capacity Planning Dashboard brings project commitments, work-package schedules and individual task assignments into a common planning discussion. Delivery leads maintain each person's role, practice and weekly capacity, while project managers organize work into packages with dates and hour budgets.
Projects in one list
| Project code | Project name | Organization | Owner | Start date | End date | |
|---|---|---|---|---|---|---|
| PRJ-BRANCH-26 | North branch service rollout | Crestline Distribution Group | Tariq Hassan | 14 Oct | 23 Oct | |
| PRJ-PORTAL-26 | Customer portal refresh | Juniper County Services | Kiran Iyer | 15 Oct | 18 Oct | |
| PRJ-WHOUSE-26 | Warehouse intake redesign | Silver Vale Utilities | Mara Novak | 20 Oct | 28 Oct | |
| PRJ-REPORT-26 | Quarterly reporting migration | Pinehurst Learning Network | Rosa Delgado | 19 Oct | 23 Oct | |
| PRJ-FIELD-26 | Field scheduling upgrade | Morrow Retail Cooperative | Oliver Chen | 03 Nov | 12 Nov |
Delivery Lead approves, rejects or returns the project scope under the review policy agreed during setup.
Every feature works on the same records. Pick one to see the screen your team works in.
Put project ownership, dates and delivery decisions beside the commitments that consume team time.
Approval conditions
| Project code | Project name | Organization | Owner | Start date | End date | |
|---|---|---|---|---|---|---|
| PRJ-BRANCH-26 | North branch service rollout | Morrow Retail Cooperative | Felipe Costa | 02 Nov | 10 Nov | |
| PRJ-PORTAL-26 | Customer portal refresh | Pinehurst Learning Network | Mara Novak | 27 Oct | 02 Nov | |
| PRJ-WHOUSE-26 | Warehouse intake redesign | Juniper County Services | Elise Lambert | 03 Nov | 09 Nov | |
| PRJ-REPORT-26 | Quarterly reporting migration | Morrow Retail Cooperative | Noah Mensah | 22 Oct | 24 Oct | |
| PRJ-FIELD-26 | Field scheduling upgrade | Crestline Distribution Group | Felipe Costa | 30 Oct | 06 Nov |
Use weekly capacity, role and practice alongside dated task demand when deciding who can take on work.
Team members
| Id | Name | Role | Practice | Weekly capacity hours | Assigned task count | |
|---|---|---|---|---|---|---|
| MS-2026-031 | Amina Farouk | Delivery Lead | Delivery Management | 9 | 22 | |
| MS-2026-032 | Oliver Chen | Project Manager | Engineering | 9 | 35 | |
| TM-041 | Rosa Delgado | Business Analyst | Quality Assurance | 2 | 34 | |
| TM-042 | Kiran Iyer | Developer | Design | 14 | 7 | |
| TM-043 | Elise Lambert | QA Engineer | Data & Analytics | 8 | 12 |
Organize project work into owned delivery blocks with dates, hour budgets and visible task demand.
Tasks
| Task key | Title | Project | Work package | Assignee | Priority | |
|---|---|---|---|---|---|---|
| TASK-2026-301 | Map branch intake workflow | Quarterly reporting migration | Crew scheduling rules | Tariq Hassan | Low | |
| TASK-2026-302 | Build portal account view | Invoice workflow modernization | Reporting data migration | Mara Novak | Medium | |
| TASK-2026-303 | Review warehouse scan steps | Invoice workflow modernization | Invoice approval routing | Kiran Iyer | High | |
| TASK-2026-304 | Validate migrated sales report | Customer portal refresh | Reporting data migration | Elise Lambert | Critical | |
| TASK-2026-305 | Test field schedule conflicts | Customer portal refresh | Crew scheduling rules | Felipe Costa | Low |
Keep each assignment, estimate and delivery state visible as work moves through the task board.
Tasks
| Task key | Title | Work package | Project | Priority | Start date | |
|---|---|---|---|---|---|---|
| TASK-2026-301 | Map branch intake workflow | Invoice approval routing | Customer portal refresh | Low | 18 Oct | |
| TASK-2026-302 | Build portal account view | Reporting data migration | Support knowledge base launch | Medium | 25 Oct | |
| TASK-2026-303 | Review warehouse scan steps | Invoice approval routing | Support knowledge base launch | High | 01 Nov | |
| TASK-2026-304 | Validate migrated sales report | Crew scheduling rules | Warehouse intake redesign | Critical | 02 Nov | |
| TASK-2026-305 | Test field schedule conflicts | Crew scheduling rules | Warehouse intake redesign | Low | 29 Oct |
Record hours against the person and project, then examine validation results before using the effort evidence.
Approval conditions
| Entry number | Team member | Project | Task | Work date | Hours | |
|---|---|---|---|---|---|---|
| TE-89185 | Felipe Costa | Support knowledge base launch | Map branch intake workflow | 31 Oct | 14 | |
| TE-86297 | Rosa Delgado | Regional onboarding program | Reconcile invoice approval paths | 24 Oct | 7 | |
| TE-94425 | Felipe Costa | Invoice workflow modernization | Map branch intake workflow | 23 Oct | 1 | |
| TE-10505 | Mara Novak | Support knowledge base launch | Build portal account view | 30 Oct | 10 | |
| TE-27278 | Oliver Chen | Field scheduling upgrade | Draft support article templates | 25 Oct | 13 |
Give issues, overdue work and resource risks a clear owner before they change the delivery plan.
Verified waits for the QA engineer
| Issue key | Title | Project | Owner | Severity | Reporter note | |
|---|---|---|---|---|---|---|
| ISS-2026-141 | Branch intake form misses region | Customer portal refresh | Felipe Costa | Critical | Seen during branch pilot on Tuesday | |
| ISS-2026-142 | Portal session expires too early | Warehouse intake redesign | Yuki Sato | High | Occurs after ten minutes of inactivity | |
| ISS-2026-143 | Scanner skips damaged cartons | Warehouse intake redesign | Elise Lambert | Medium | Three cartons failed the scan test | |
| ISS-2026-144 | Report totals differ by week | Invoice workflow modernization | Yuki Sato | Low | Mismatch appears in week 39 totals | |
| ISS-2026-145 | Double booking on shared crews | Invoice workflow modernization | Yuki Sato | Critical | Reproduced with two shared crews |
Capacity baseline to reviewed delivery ships ready to use. One step needs a named approval before the work moves on: Approve delivery scope (Delivery Lead).
Delivery Lead agrees weekly capacity and reviews the dated work for a consistent planning period.
Project Manager organizes the commitment into owned packages with dates, hour budgets and tasks.
Delivery Lead records the project scope decision before the manager commits the team to active delivery.
Agree the person, estimate and dates for each task against the team's existing commitments.
Submitted time is checked for positive hours and an eligible state, with decision and operation evidence recorded.
Review remaining work and resource concerns before agreeing the next period's assignments.
Open any project to see its issues, the roles that work on it, its process stages and its approvals on one page.
Project name, Organization, Owner and Start date.
Each line is linked to this project.
Admin, Delivery Lead and Project Manager, each with their own permissions.
Capture project demand and Outline work packages, with the role that acts.
Approve delivery scope, with who decides.
North branch service rollout · Active
| Issue key | Title | Project |
|---|---|---|
| ISS-2026-141 | Branch intake form misses region | Field scheduling upgrade |
| ISS-2026-142 | Portal session expires too early | Regional onboarding program |
| ISS-2026-143 | Scanner skips damaged cartons | Regional onboarding program |
Human scope and delivery review decisions are separate from the automatic validation of submitted time. Explain both paths before the first operating cycle.
Signed in as Delivery Lead
| Decision | Approver | |
|---|---|---|
| Approve delivery scopeDelivery Lead records the project scope decision before the manager commits the team to active delivery. | Delivery Lead | |
| Approve Projects, work packages | Delivery Lead | |
| Approve Tasks, Milestones | Project Manager |
Everyone opens Capacity Planning Dashboard to the work that is theirs. Pick a role to see what it starts with.
Maintains user access and the organization and personnel records used to identify delivery work.
Owns capacity assumptions and authorizes the project scope the team is prepared to deliver.
This is the first screen this role sees.
Time entries · Delivery Lead
| Entry number | Team member | Project | Task | Work date | Hours | |
|---|---|---|---|---|---|---|
| TE-89185 | Felipe Costa | Support knowledge base launch | Map branch intake workflow | 31 Oct | 14 | |
| TE-86297 | Rosa Delgado | Regional onboarding program | Reconcile invoice approval paths | 24 Oct | 7 | |
| TE-94425 | Felipe Costa | Invoice workflow modernization | Map branch intake workflow | 23 Oct | 1 | |
| TE-10505 | Mara Novak | Support knowledge base launch | Build portal account view | 30 Oct | 10 | |
| TE-27278 | Oliver Chen | Field scheduling upgrade | Draft support article templates | 25 Oct | 13 |
Plans assignments and coordinates time, milestones and exception follow-through for delivery work.
This is the first screen this role sees.
Time entries · Project Manager
| Entry number | Team member | Project | Task | Work date | Hours | |
|---|---|---|---|---|---|---|
| TE-89185 | Felipe Costa | Support knowledge base launch | Map branch intake workflow | 31 Oct | 14 | |
| TE-86297 | Rosa Delgado | Regional onboarding program | Reconcile invoice approval paths | 24 Oct | 7 | |
| TE-94425 | Felipe Costa | Invoice workflow modernization | Map branch intake workflow | 23 Oct | 1 | |
| TE-10505 | Mara Novak | Support knowledge base launch | Build portal account view | 30 Oct | 10 | |
| TE-27278 | Oliver Chen | Field scheduling upgrade | Draft support article templates | 25 Oct | 13 |
Maintains assigned task progress, records work time and raises issues with supporting evidence.
This is the first screen this role sees.
Time entries · Developer
| Entry number | Team member | Project | Task | Work date | Hours | |
|---|---|---|---|---|---|---|
| TE-89185 | Felipe Costa | Support knowledge base launch | Map branch intake workflow | 31 Oct | 14 | |
| TE-86297 | Rosa Delgado | Regional onboarding program | Reconcile invoice approval paths | 24 Oct | 7 | |
| TE-94425 | Felipe Costa | Invoice workflow modernization | Map branch intake workflow | 23 Oct | 1 | |
| TE-10505 | Mara Novak | Support knowledge base launch | Build portal account view | 30 Oct | 10 | |
| TE-27278 | Oliver Chen | Field scheduling upgrade | Draft support article templates | 25 Oct | 13 |
Examines fixes and delivery evidence, records verification outcomes and books time against assigned work.
This is the first screen this role sees.
Time entries · QA Engineer
| Entry number | Team member | Project | Task | Work date | Hours | |
|---|---|---|---|---|---|---|
| TE-89185 | Felipe Costa | Support knowledge base launch | Map branch intake workflow | 31 Oct | 14 | |
| TE-86297 | Rosa Delgado | Regional onboarding program | Reconcile invoice approval paths | 24 Oct | 7 | |
| TE-94425 | Felipe Costa | Invoice workflow modernization | Map branch intake workflow | 23 Oct | 1 | |
| TE-10505 | Mara Novak | Support knowledge base launch | Build portal account view | 30 Oct | 10 | |
| TE-27278 | Oliver Chen | Field scheduling upgrade | Draft support article templates | 25 Oct | 13 |
Read capacity, assigned demand and delivery effort with a consistent period and clear ownership.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 32 | ||
| Active | 7 | 22% | |
| On hold | 1 | 14% | |
| At risk | 1 | 100% |
Sample totals per stage
Group active people by practice and role with their weekly capacity and total assigned estimates for the planning discussion.
Group tasks by assignee and project with their start and due dates, estimates and states to identify unfinished work overlapping the review period.
Compare each work package's hour budget with its task estimates and actual hours, alongside the delivery window and state.
Show each project's estimated, actual and logged hours with the recorded hour variance, owner, end date and state.
Group recorded hours by person, project, work date and billable classification, keeping Submitted and Approved time separate.
Group issues by project, severity, owner and state to show unresolved work and fixes awaiting verification.
Review each project's milestone due dates, owners and notes with the Pending, Met or Missed outcome.
Review resource risks with their probability, impact, owner, mitigation and current state.
Group review decisions by project and subject, then resolve operation receipt references separately to trace attempted actions and their results.
See how Capacity Planning Dashboard fits your kind of team.
Balance client-project commitments with the people, task demand and delivery evidence behind them.
Make internal project commitments and resource concerns visible across business requests.
Coordinate task demand and verification work as product delivery commitments move between people.
Each stage of capacity baseline to reviewed delivery names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to help configure the planning cycle and examine the evidence behind team commitments.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 13 tablesStart with one team and one process, then add the rest once the basics are running.
Select a real project and review period. Define weekly capacity assumptions and identify the Delivery Lead responsible for accepting scope.
Load organizations, people and project records. Reconcile identity details and configure access before assigning work through personal screens.
Prepare work packages and tasks with owners, dates and estimates. Check project links and explain how the team will handle work that spans planning periods.
Submit a valid time entry and an invalid zero-hour entry. Triage an Open issue with severity and a case without it, then inspect the operation results.
Have the Delivery Lead return and then approve project scope. Have the Project Manager record a delivery decision after examining task, milestone and verification evidence.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Capacity Planning Dashboard for your business. Start with a real project, its work packages and the people assigned to the next planning period. Rehearse scope review, time validation and an issue that needs follow-through.
Each team member has weekly capacity hours alongside their role, practice and active state. Agree the baseline with the Delivery Lead and keep it current when the person's working arrangement changes.
First select a consistent planning period and inspect unfinished tasks whose dates overlap it, including work due later. Clarify undated assignments and agree the effort for tasks spanning periods with their owners. Use that discussion to compare the period's commitment with weekly capacity.
A project contains work packages with dates and hour budgets. Tasks belong to a package and carry the assignee, estimate and delivery state used in the capacity discussion.
Configure the Delivery Lead's scope-review responsibility during setup. Record the project decision and notes so the manager can explain why the commitment was accepted, rejected or returned for revision.
The time action checks that the entry is still Submitted and its hours are positive. A valid entry becomes Approved with decision and execution evidence. Invalid attempts are blocked and recorded for investigation.
It moves an eligible Open issue with severity to Triaged and records an operation receipt. Missing severity or an issue that is no longer Open blocks the action and records the failed attempt.
The queue brings together overdue tasks and milestones, fixed-but-unverified issues and leading open risks. It shows the owner, age and a direct path to the affected record.
Use them to identify the relevant delivery group and discuss assignments with the person and their lead. Agree any additional skills-assessment connection separately with the team responsible for it.
Agree connections for personnel, leave, existing task tools or financial handoffs with the systems that own those records. Use the connections page to settle field ownership and reconciliation before live use.
Start free, then use Proto to change fields, steps and approvals before your team goes live.