Tasks and hours

Track execution work, dependencies, due dates, and actual effort within the package. The team uses task name, planned hours, actual hours, dependencies, and completion date to keep that context together. Use a pilot package to check the record links and each role’s handoff.

• Task plan. Project Coordinator puts each task under its package with a line number, planned hours, due date, and dependency text.
• Execution. Contributor records actual hours and a completion date against the task being performed.
• Review. The coordinator checks that task revisions and evidence still match the package before requesting delivery review.

A task row is part of package scope, not a separate project. Its dependency text must identify a task in the same plan; a cycle cannot become a workable baseline. Planned and actual hours let the team compare effort, while completion evidence tells the reviewer what finished.

Agree how task names and dependency identities are written, who may revise a task after the baseline, and when actual hours are entered. Decide which completion evidence is required for each type of work. A due date alone does not establish completion; the completion date and linked evidence should support the handoff. Recheck the parent package revision after a changed plan.

Contributor records effort on the task within its parent package. Project Coordinator checks dependency identities and the current task revision before accepting a changed plan.

Consider an animation task that depends on rigging in the same package. Project Coordinator records both tasks and checks that the dependency points to the rigging task, with no return link that would create a cycle. Contributor enters actual hours while working and marks the rigging task complete with evidence before animation is treated as ready. The package’s budget hours remain a planning boundary, not a substitute for task-level effort.

Repeat the case with a dependency pointing to a task in another package. Correct the dependency before baselining. Then revise the animation task after the package enters review: the coordinator should bring the revised plan back to the Independent Reviewer rather than relying on a decision against the older source revision.

• Open Tasks by Due Date — See due task work with its parent package and recorded effort.
• Active Work Packages — Open the parent scope before changing task hours or completion.

Follow planning, execution, and delivery review for the handoffs that connect these records. The data model shows the exact references to migrate and verify. Set up a pilot through implementation before broadening the team.