Work Packages Guide
A work package is a structured group of related project documents managed as a single deliverable lot. Use work packages when documents must be submitted, reviewed, and closed as a set — for example, a formal client submittal, a discipline-level package, or a handover stage. Work packages give document controllers a clear container for batch management, and project managers a progress view at the package level rather than individual documents.
When to use work packages
- Formal submittals — multiple documents requiring a single submission reference and response.
- Discipline packages — all structural or mechanical deliverables for a project phase.
- Handover lots — documents required for project closeout or asset handover.
- Review batching — routing multiple documents through the same review team in one action.
Creating a work package
- Go to the Work Packages tab.
- Select New package.
- Enter the required fields:
| Field | Required | Description |
|---|---|---|
| Package number | Yes | Auto-generated or manually entered reference identifier. |
| Title | Yes | Descriptive name of the package. |
| Description | No | Purpose, scope, or handover notes for the package. |
| Discipline | No | Primary discipline the package covers. |
| Responsible party | No | Team member accountable for the package's progress. |
| Target submission date | No | The expected date for formal issue to the client or approver. |
| Package type | No | Classifies the package (Submittal, Handover, Review Batch, etc.). |
- Save. The package is created with Draft status.
Package status lifecycle
| Status | Description | Typical next action |
|---|---|---|
| Draft | Being compiled. Documents may be added or removed. | Add documents, start workflows on individual documents. |
| Active | Construction or production is underway. | Monitor document review progress. |
| Submitted | Formally issued to the client, contractor, or approver. | Await responses. Track acknowledgement. |
| Closed | All required decisions received and recorded. | Archive or use for closeout evidence. |
Status transitions are logged in the package activity history with the acting user and timestamp.
Assigning documents to a package
Single document assignment
Open a document from the register and edit the Package / contract metadata field to assign it to a package.
Bulk assignment
- Select multiple documents in the register using checkboxes.
- Open the bulk actions menu and choose Assign to package.
- Select the target package.
- Confirm. The assignment is applied to all selected documents and logged in each document's activity history.
Removing documents
Open the package and select the document to remove. Use the Remove from package action. The document record is unaffected — only the package association is cleared.
Package as a review matrix dimension
The Review Matrix can include Work package as a routing dimension. This means a rule can be scoped to a specific package, sending documents in that package to designated reviewers automatically — useful when a package has a dedicated client review team separate from the standard discipline-level routing.
Package view and filtering
From the Work Packages tab:
- View all packages in the project with current status, document count, and responsible party.
- Click a package to see all assigned documents, each with their current status and active workflow state.
- Filter documents within a package by status, discipline, or document type.
- Use the Progress summary to see how many documents are Approved, Under Review, or still in Draft.
Related
- Document Register Guide — register metadata including the package field
- Transmittals Guide — formally issuing packages to recipients
- Review Matrix — routing work package documents automatically
- Work Packages tab — the tab-level view of all packages
Documents linked to a package appear in the register with the package reference. A document can appear in multiple packages but should only be formally submitted through one primary package.
Package-level review
Start a workflow at package level from the package detail view. All linked documents are routed together. This is more efficient than individual document workflows when the review team and timeline are identical.
Closeout
Before closing a package, confirm all linked documents have received the required responses and that the final status reflects the approver's decision. See Project closeout for the full closing process.