Work packages

A Project Coordinator records the subject, owner, project, due date and budget hours for each package. The package begins in Draft. Planning adds task lines and dependencies; baselining checks the revision and moves the package through Planned into Active. The record number lets the team refer to the same scope during delivery and review.

• Draft scope. Project Coordinator gives the package a subject, record number, owner, project, due date and budget hours.
• Baseline. Task lines and dependencies are checked against the current revision before the package becomes Active.
• Delivery decision. Event Worker completes tasks; Project Reviewer decides the submitted package revision from shared evidence.

Agree what belongs in one package, who may revise it and what evidence a reviewer needs at the end. Put venue preparation and supplier coordination in separate packages when their owners or acceptance decisions differ. Budget hours are a planning limit; actual hours live on Tasks, where the worker records what happened.

Agree when a venue deliverable needs its own package rather than a task in a larger one. Keep the package owner distinct from the independent reviewer. Decide who can change future unaccepted scope after a late supplier request, and require a review decision before revising dependent task lines. The record number should stay recognizable across handoffs.

Pick a package whose due date is close. Check its project, owner, task lines and budget before moving it forward. When a late venue change arrives, prepare a successor revision and retain earlier acceptance and attached evidence. A reviewer decision on the change should precede revisions to future unaccepted work.

Use a venue setup package due before the event. The Project Coordinator opens its task lines and confirms the planned hours fit the budget before baselining. If a supplier changes the setup plan after work starts, the coordinator prepares a successor revision and asks the Project Reviewer to decide the change. The worker’s completed hours and existing attachments stay with the earlier work. The next worker sees the current revision and which tasks remain.

• Work Package Board — See packages grouped by their current status, with owner and due date visible.
• Work Packages — Check the parent scope, owner, due date and current status before deciding.

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