1. Release Management
  2. Features
  3. Time and capacity
Feature · Time and capacity

Time and capacity

Review submitted hours and compare assigned work with weekly capacity.

OverviewTimesheets Awaiting Approval
Release Management · Time and capacity

Timesheets Awaiting Approval

Approval conditions

New
Entry numberTeam memberProjectTaskWork dateHours
TE-72727PRJ-9039TSK-191418 Oct11
TE-36393PRJ-6619TSK-508015 Oct7
TE-90889PRJ-1742TSK-320317 Oct8
TE-97496PRJ-9202TSK-705022 Oct1
TE-60941PRJ-8071TSK-634207 Oct9
6 of 6 records
PRJ-9039Time entries · TE-72727
Submitted
TaskTSK-1914
Work date18 Oct
Hours11
Example screen with sample data

What you can do

Time and capacity in daily work

A team member enters the work date, hours and project, with a task where the time belongs to specific work. The entry moves from Draft to Submitted. The Time Entry Approval workflow automatically approves a submitted entry with positive hours and writes a review decision and operation receipt. An invalid attempt is blocked and records a failed receipt. Team members carries weekly capacity and assigned and logged hour totals for planning.

How the work is organized

  • Owner. Developer or QA Engineer submits an entry with a work date, project and positive hours. The workflow approves a qualifying submitted entry automatically. Time Approver examines the decision and receipt afterward, especially when an attempted approval failed.
  • Record. Compare each person’s weekly capacity with assigned estimates and logged hours before assigning more work. An approved time entry records the hours worked; a failed receipt signals an attempted action that the team must inspect. Correct the source entry before resubmitting rather than treating the failed receipt as an approved hour.
  • Decision. Review the automatic decision and receipt before the Time Approver reports approved hours.

What to agree during setup

Agree who inspects approval results and failed receipts, and what descriptions help explain the work. Keep the project and task references aligned so package effort and project hours are meaningful. Weekly capacity and assigned estimates support a workload conversation; they do not automatically choose the next assignee.

Rehearse with a submitted entry for a real project and a failed attempt with nonpositive hours. Ask the Time Approver to trace both receipts to their entries, then compare the team member’s assigned effort and logged hours with weekly capacity.

Check the handoff on an actual case

A developer submits hours against a task in the current package. The workflow checks the submitted entry and records its approval when hours are positive. The Time Approver inspects the date, project, task, hours and resulting receipt. If the hours are zero, the approval is blocked and a failed receipt is available for review.

For the zero-hour attempt, the Time Approver checks the failed receipt and the source entry. The developer corrects the hours on the entry before submitting it again. The failed receipt remains part of the history and does not add approved time.

What your team sees

  • Timesheets Awaiting Approval — Find entries still marked Submitted and inspect their project, task and hours.
  • My tasks — Compare assigned work and due dates with the time recorded against a task.

Follow the work through

See plan and delivery, issue triage and release window review for the steps around this work.

What it keeps track of

Data model
Time entries
Hours booked by a team member against a task and project.
Team members
Delivery staff with role, practice and weekly capacity.
Tasks
Individual pieces of work assigned to a delivery team member.
Projects
Engagements delivered for an organization, with budget and schedule.
Review decisions
Recorded approval decisions on delivery subjects.
Operation receipts
Evidence that a delivery operation was executed.

Who uses it

Permissions
Time Approver
, Developer, QA Engineer and Project Manager.

Set up Release Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started