These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- PM with AI Scheduling
- Features
- Work packages
Work packages
Keep contracted delivery scope, budget hours and acceptance together.
OverviewPackages due for review×
PM with AI Scheduling · Work packages
New
Packages due for review
Acceptance waits for the delivery lead
| Record number | Subject | Status | Revision | Owner | Due at | |
|---|---|---|---|---|---|---|
| WP-32513 | Review wp-956 | Review | 170 | 14 Oct | ||
| WP-28306 | Review wp-565 | Review | 360 | 21 Oct | ||
| WP-85875 | Review wp-272 | Review | 200 | 17 Oct | ||
| WP-21887 | Review wp-300 | Review | 670 | 13 Oct | ||
| WP-61802 | Review wp-100 | Review | 860 | 23 Oct |
6 of 6 records
Review wp-956Work packages · WP-32513
ReviewRevision170
Due at14 Oct
What you can do
Work packages
Project Coordinator opens a package for a project, gives it a record number and subject, sets a due date and budget hours, and assigns a team owner. The package revision changes as the team plans and delivers. Planned, Active and Review describe distinct phases. Accepted records a completed outcome, while Cancelled records stopped work. A baseline revision keeps the accepted planning point visible when a later change is considered.
How the work is organized
- Scope record. Put the intended delivery in the subject and link the proper project.
- Ownership. Assign the staff member accountable for progress and review handoff.
- Revision. Confirm the current package revision before any guarded change.
What to agree during setup
Agree who may create packages, who may change budget hours and when a draft becomes planned. Set a rule for due dates that the team can apply consistently. Decide how a coordinator records a scope correction without changing previously accepted work. The delivery lead should check package ownership and the linked project before execution begins.
Check the handoff on an actual case
A coordinator opens a package for a project and assigns an owner. Task planning reveals more work than the initial budget hours allowed. The coordinator discusses the change before setting the package to planned. Once the owner starts delivery, the lead compares actual task hours with the package budget. At review, the reviewer sees the same package revision and attached evidence. Acceptance records that revision rather than treating a changed package as the one reviewed.
Treat each package as a decision boundary for delivery. Its subject tells the team what is being delivered, while the owner and due date identify who must move it forward and when. The budget hours give the coordinator a reference point before accepting a proposed schedule. A reviewer should be able to open the package and see which revision was submitted, what task work remains, and which files support the handoff. If the package is changed while a decision is pending, bring the current revision back to the reviewer. The lead can then use Accepted only for work that actually passed the review, while cancelled future work keeps a distinct status.
What your team sees
- Active work packages — Follow work from planning through review.
- Work package board — Compare lifecycle positions without hiding the owner.
- Accepted packages — Revisit the accepted scope and baseline.
Follow the work through
Follow work packages in the operating process. Review the data model when mapping project, package and evidence records.
What it keeps track of
Data model- Work packages
- Contracted units of delivery with lifecycle, budget hours and accepted baseline.
- Projects
- Client projects that work packages are delivered against.
- Organizations
- Client and delivery organizations that own projects and work packages.
- Team members
- Named delivery staff with their organization membership and platform identity.
- Tasks
- Scheduled task lines inside a work package with planned and actual hours.
Who uses it
Permissions- Project Coordinator
- Prepares scope; Team Member executes; Delivery Lead tracks it; Project Reviewer makes the independent decision.
Set up PM with AI Scheduling your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.