Tasks and delivery

Task lines give a package its working detail. Each line has a number and revision under its parent package. The task name, planned hours, actual hours, due date, completion date and dependency text help the owner explain both the plan and what the crew finished. The operations overview compares planned and actual task hours by project and shows overdue tasks by owner.

The parent package remains the decision record. A completed task can support delivery review, but it does not accept the whole package. The owner should check every relevant task before putting the package into review, especially when a dependency is unfinished or a line was added in a later revision.

• Sequence. Package Owner records line numbers and dependencies so the work order is understandable to the team.
• Progress. Actual hours and completion dates show completed tasks separately from lines still awaiting work.
• Attention. Public Works Manager uses the overdue queue and project hours to decide which owner needs follow-up.

A due task may belong to a package whose overall due date is later. Review both dates before escalating a delay. The completion date provides an audit trail for work performed; the actual hours alone do not show when the task finished.

Decide how to name recurring task lines, how to write dependencies in the available text field and when a task is considered complete. Set a practice for revising task lines after a package has started. Agree which owner records field hours and which manager checks an unusually large difference between planned and actual hours. Keep the parent package and its task lines on the same scope revision during a correction.

Rehearse a package with a blocked predecessor and one late task. The manager should see the delay without treating the dependent line as complete. Review how cancelled future work is separated from tasks already executed.

For a bridge approach repair, enter surface preparation before paving as dependent task lines. Set planned hours and dates. Complete preparation with its actual hours, leave paving unfinished, and inspect the open-task list and operations overview. The package owner should be able to explain the remaining dependency. When paving finishes, record its actual hours and completion date, then attach the delivery evidence before review.

• Open Tasks — Task lines needing attention with due date, hours and parent package.
• All Tasks — The full line history for a package and its revisions.
• Overdue Work Packages — Parent commitments that need a manager’s attention.

See plan and activate work and review delivery.