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.
- Construction Project Tracker
- Features
- Work packages
Work packages
Track site scope through an owner, due date, budget hours and status.
OverviewPackages Due×
Construction Project Tracker · Work packages
New
Packages Due
Work packages
| Record number | Subject | Counterparty | Due at | Status | |
|---|---|---|---|---|---|
| WP-59701 | Draft wp-729 | PRJ-9391 | 06 Oct | Draft | |
| WP-14134 | Planned wp-677 | PRJ-8467 | 08 Oct | Planned | |
| WP-24669 | Active wp-344 | PRJ-6409 | 08 Oct | Active | |
| WP-20469 | Review wp-575 | PRJ-3717 | 11 Oct | Review | |
| WP-87269 | Accepted wp-942 | PRJ-7714 | 14 Oct | Accepted |
6 of 6 records
Draft wp-729Work packages · WP-59701
DraftCounterpartyPRJ-9391
Due at06 Oct
What you can do
Give delivery scope a stable record
A work package is the daily unit of delivery in Construction Project Tracker. It has a record number, subject, organization, project, owner, due date and budget hours. Its revision and baseline revision help the team identify which version of the work is under discussion. The status can move through draft, planned, active, review, accepted or cancelled. The Project Coordinator uses the package to connect task lines, attachments, certificates and reviewer decisions.
The package should be specific enough for its owner to explain the work and the reviewer to inspect its evidence. A vague subject makes a certificate hard to assess. A due date and budget hours give the Operations Overview useful signals, but they do not replace the task lines that explain how effort was planned and recorded.
How the work is organized
- Ownership. One named team member owns each package under the relevant organization and project.
- Lifecycle. Status, start date, accepted date and revisions show where the scope stands.
- Linked work. Tasks, certificates, attachments, decisions and operation receipts refer back to the package.
What to agree during setup
Choose a rule for package subjects and record numbers, then decide when a coordinator may move a draft to planned work. The team should also agree what evidence is needed before a package enters review. An accepted package should have its task progress checked against the work actually delivered. Cancelled scope should remain visible as a record, because the related tasks and attachments explain the history.
Agree who may change the owner and what happens to a package when its project changes. The owner is a team member rather than a free-text name, which lets the coordinator keep a consistent assignment. The package’s organization, owner and project should describe the same job before certification begins. The revision is especially important once a reviewer decision references a particular source revision.
Check the handoff on an actual case
A coordinator opens a work package for a concrete pour at an active site. The record names the project, assigns a site owner, gives the work a due date and sets budget hours. The owner records task lines for preparation and placement. When the work is ready for inspection, the coordinator moves the package to review and collects the relevant evidence attachments. The Project Reviewer sees the package revision alongside the certificate and any existing decision record.
If the pour is delayed, the coordinator can find it from its due date and status in the active list. If work is cancelled, the package is marked cancelled rather than disappearing from the project history. If the team agrees that completed work is accepted, it records the accepted date on the package. These choices make the package a usable handoff record for the next operating cycle.
What your team sees
- Work Package Board — Scope grouped by its current delivery status.
- Packages Due — Packages whose due dates need attention.
Follow the work through
See package delivery and certificate review.
What it keeps track of
Data model- Work packages
- Planned delivery scope with owner, lifecycle status and due date.
- Projects
- Client projects and sites that work packages are delivered against.
- Organizations
- Construction delivery organizations that own projects and work packages.
- Team members
- Named staff belonging to an organization, linked to platform identities.
- Tasks
- Line items of work under a work package with planned and actual hours.
- Progress certificates
- Certified work progress submitted for reviewer approval.
- Record attachments
- Evidence files attached to a work package.
- Review decisions
- Independent reviewer decisions on a work package revision.
- Operation receipts
- Durable receipts for guarded operations with retry-stable keys.
Who uses it
Permissions- Project Coordinator
- Prepares and updates packages.
- Project Reviewer
- Examines reviewed revisions.
- Auditor
- Reads the authorized history; App Administrator maintains the project and membership context.
Set up Construction Project Tracker your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.