Tasks and hours

Tasks give a work package its line-level plan. Each line has a number, revision and parent package. A task can record its name, planned hours, actual hours, due date, completion date and dependency note. The Project Coordinator uses these fields to explain what is due, what has been done and which work still needs attention. The package carries the overall budget hours; task lines supply the detail for comparing the plan with work recorded.

A line number should remain stable as the team reviews the package. If a task changes, its revision helps distinguish an earlier description from the current one. The dependency note can describe related work, but the team should still check the task’s due and completion dates directly when deciding what is late.

• Line items. Each task belongs to one package and has a line number and revision.
• Effort. Planned and actual hours can be compared by task and rolled up beneath a package.
• Dates. Due and completion dates let the team identify tasks that require attention.

Decide how detailed a task should be. A line for an entire phase may hide the part that caused a delay, while tiny lines can make daily review harder. Set a shared practice for recording actual hours and completion dates. The coordinator should check task totals against the package’s budget hours when preparing a review, because the package budget and task plan answer related but different questions.

Agree how to use the dependency note. It is a text field that can help the team name a predecessor or site condition. A coordinator should review that note with the owner when changing a due date. The task line itself remains under its parent package, so moving work between projects starts with checking the package relationship.

For an exterior repair package, the coordinator adds lines for surface preparation and finishing. Each line receives planned hours and a due date. The owner later records actual hours and a completion date on the finished preparation line. If finishing remains open after its due date, the coordinator finds it in the due task view and can discuss the delay using the recorded line, rather than relying on a message thread.

Before submitting a certificate, the coordinator compares completed task lines with the package scope. If actual hours exceed the plan, the difference is visible at the task level. A reviewer can read the same task history while examining the package revision and attached evidence. This supports a concrete discussion about the work represented by the certificate without treating an hour total as a substitute for inspection.

• Tasks Due — Task lines with due dates, completion dates and recorded effort.
• Active Work Packages — The parent scopes and owners for the task work.

Follow package delivery and certificate review.