1. Capacity Planning Dashboard
  2. Process
  3. Task delivery and recorded time
Process · Task delivery and recorded time

Task delivery and recorded time

Follow assigned work into recorded hours and inspect the automatic validation outcome.

Step by step

  1. Begin the assignment Developer

    Developer or QA Engineer opens the assigned task, checks the work package and agreed dates, and moves Backlog work into progress when it starts.

    • Record Backlog → in progress when work starts
    • Updates Tasks, Work packages
  2. Record the work Developer

    The team member records a time entry with the work date, positive hours, person and project. Add the task link where the entry belongs to a particular assignment and describe the work performed.

    • Prepare dated hours with the intended links
    • Updates Time entries, Team members, Projects, Tasks
  3. Submit for validation Developer

    The team member changes the Draft entry to Submitted. The time action checks that the hours are positive and the entry remains Submitted, then records Approved together with decision and operation evidence.

    • Validate Submitted time and record Approved or a failed attempt
    • Updates Time entries, Review decisions, Operation receipts
  4. Investigate a failed attempt Project Manager

    Project Manager reads the failed receipt when the hours or entry state fail the guard. Correct the source record under the team's procedure before trying the eligible action again.

    • Explain and correct the blocked submission
    • Updates Time entries, Operation receipts
  5. Review effort in context Project Manager

    Project Manager compares time with task progress and estimates. Discuss remaining work with the assigned person before changing the package schedule or accepting another commitment.

    • Compare the work evidence before revising commitments
    • Updates Tasks, Projects, Work packages, Time entries

Where it usually breaks

And how to keep it from happening.

  • The entry has no positive hours. Check the quantity before submission and inspect the failed attempt when the guard blocks it.
  • The action is repeated on an ineligible state. Confirm the current entry state rather than treating another attempt as another approval.
  • Recorded time is read without progress context. Inspect the task outcome and remaining work before revising the plan.
Developer
, QA Engineer, Project Manager, Delivery Lead.

Set up Capacity Planning Dashboard your way.

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

How to get started