Package planning

Step by step

1. Project scope Admin

   Admin confirms the research organization, its funded project and the active team member who will own the package. Research Coordinator checks that the project belongs to the chosen organization.

   • Confirms project and owner context.
   • Updates Organizations, Projects, Team members

2. Package plan Package Owner

   Package Owner records the package subject, number, due date, budgeted hours and owner. The package begins as Draft and can move to Planned after the plan is checked.

   • Records scope, hours, due date and revision.
   • Updates Work packages

3. Task dependencies Package Owner

   Package Owner adds task lines with planned hours, dates and predecessor details. Research Coordinator examines the sequence and capacity before work begins.

   • Connects planned effort and predecessor lines to the package.
   • Updates Tasks, Work packages

4. Baseline check Research Coordinator

   Research Coordinator checks the current revision, task dependencies and scope. When the plan is ready, the package moves from Planned to Active and the started date identifies the handoff into execution.

   • Checks revision and records the operating outcome.
   • Updates Work packages, Tasks, Operation receipts

Admin

Establishes organization context; Package Owner prepares the plan; Research Coordinator checks the handoff; Operations Analyst follows exceptions.