Work Packages
Work Packages
Organise testing activities into work packages that group requests, allocations, and usage plans.
A work package groups related testing activities under one umbrella. It connects vehicle requests, allocations, usage plans, and documents so you can manage a test campaign as a single unit rather than tracking its pieces separately.
What a Work Package Contains
| Section | Description |
|---|---|
| General Information | Name, lead engineer, status, priority, dates, and description |
| Resources | Vehicles linked to this work package through allocations |
| Usage Plans | Scheduling for shifts and mileage tracking |
| Access Control | Restrict visibility to specific teams and users |
| Compliance & Requirements | Compliance checks and requirement tracking (PRO) |
| Documents & Reports | Uploaded files, test plans, specifications, and reports |
| Activity | Audit log with comments and change history |
When to Use Work Packages
Work packages are most useful when a testing activity has:
- Multiple vehicles or driver shifts to schedule
- Targets to track (e.g. mileage, hours, tests) over time
- Related requests that should be grouped together
- Documents or specifications that the team needs to reference
For simple one-off requests without scheduling, you can skip work packages and submit requests directly. See Key Concepts — Workflow Variations for details on how direct assignment and request-based flows differ.
Explore This Section
Creating Work Packages
Step-by-step guide to setting up a new work package
Work Package Details
Navigate the detail view — usage plans, requests, and documents
Related
- Usage Plans — scheduling shifts and tracking mileage within a work package
- Vehicle Requests — submitting requests that can be linked to work packages