Tasks and dependencies

Each Tasks line belongs to a work package. The coordinator assigns a line number, task name, planned hours, due date and any dependency. The Event Worker records actual hours and completion when the work is done. The parent package retains its own due date and budget, so the team can compare the task detail with the promised scope.

• Task line. Project Coordinator records a named task, line number, estimate and due date under a package.
• Dependency. Each dependency points to a task in that same package and is checked before baselining.
• Actual work. Event Worker enters actual hours and completion when the prerequisite work is done.

Agree how to write dependencies so that each one resolves to a task inside the same package. Before baselining, check for cycles and partial scope. Decide when a completed task can be corrected and who checks the reason. The task line revision must follow a controlled package change; changing a dependent line silently would weaken the baseline.

Agree how the coordinator identifies a dependency so workers can find the prerequisite line. Reject a cycle or a reference outside the package before the baseline is accepted. When a plan changes, carry dependent task lines into the new revision through the change decision. Workers should record actual hours on the task they performed, even when the estimate was different.

Walk through venue access before supplier load-in. Enter the venue access task first, then the supplier task that depends on it. Check that the dependency points to the intended line and that completion dates and actual hours reflect the work. Submit the package for review only after every required task and its dependencies are complete.

For a venue load-in, create an access task and a supplier arrival task that depends on access. The Event Worker checks the access completion before recording supplier work, then enters actual hours and completion dates for both. A Project Reviewer follows the dependency and checks that every required line is complete before accepting the package. If access was delayed, the due calendar shows the affected line for the coordinator to address.

• Task Due Calendar — See due task lines and their completion dates in the task calendar.
• Work Packages — Check the parent scope, owner, due date and current status before deciding.

Follow Deliver and document for the related decision path. Review the data model when mapping existing records, and use implementation to rehearse the first event cycle.