Work packages

Give each delivery scope an owner, budget, due date, revision, and lifecycle state. The team uses record number, subject, owner, project, due date, and budget hours to keep that context together. Use a pilot package to check the record links and each role’s handoff.

• Plan. Project Coordinator records the package subject, project, owner, due date, budget hours, and starting revision.
• Baseline. The coordinator checks task dependencies and planned hours before freezing the baseline and starting execution.
• Change. A changed scope uses the current revision and preserves the earlier baseline and decisions for inspection.

The lifecycle board separates draft, planned, active, review, accepted, and cancelled work. It shows where a package sits, while the linked tasks and decisions explain why it may move. A receipt gives a guarded action a stable operation key so a retry can be reconciled against the same effect.

Agree who may set the budget and due date, what counts as a valid project counterparty, and how the coordinator confirms task dependencies. Assign an owner before asking for a baseline. Decide when a change needs a new task revision and an independent decision. Keep cancellation and correction procedures explicit so the earlier scope remains traceable instead of disappearing from the package history.

Project Coordinator compares the expected revision with the live package before changing scope. Keep the accepted baseline and earlier decisions available when a later correction or cancellation is needed.

Consider a level art package whose rigging task changes after the original plan. Project Coordinator opens the active package and checks its revision and frozen baseline. The new task plan must refer to the current package and valid dependency identities. A decision made against the older revision cannot approve this scope. The coordinator requests review of the changed package, and the reviewer inspects the new task and attachment evidence.

Repeat the change with the old revision. The stale request should leave the current package and its task rows intact. If the action outcome is uncertain, the coordinator uses its receipt and operation key before retrying. The prior baseline and review decision remain available to explain the change.

• Work Package Lifecycle Board — Scan package states by subject, owner, and project.
• Planned Work Packages — Check planned scope and due dates before baselining.

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.