Questions, answered

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.