Work package
Group deliverables that hold together.
The output of the package is verifiable.Structured template · MOD-13
Marketing roadmap to download: fields and controls
Decision question
In which order should initiatives run without hiding the critical dependencies?
Editable CSV file
The template’s required fields.
This file is used to approve the sequence, the buffers and the milestone gates. The related guide page explains the method. Here, the scope is limited to the columns, checks and example needed to complete the deliverable.
Milestone
Set a dated decision.
The milestone is not merely an activity.Dependency
Connect prerequisites and consequences.
The upstream owner is named.Buffer
Protect the uncertain paths.
The buffer is not hidden inside tasks.Example structure
A concrete reading before completing the file.
| Work package | Milestone | Date | Gate criterion |
|---|---|---|---|
| Framing | Brief approved | 5 September | Mandate signed |
| Production | Kit ready | 25 September | QA completed |
Checks before use
- Deliverable work packages
- Decision milestones
- Visible dependencies
- Explicit buffers
Counter-example
Completing “Work package” without satisfying “The output of the package is verifiable.” creates a present but unacceptable deliverable. The row must remain blocked until corrected.
Editable resource
Download the template and retain its history.
Editable CSVDownload the marketing roadmap↓Review the example and acceptance criteriaOriginal planning template. The example values are neither a benchmark nor an automatic recommendation. Adapt units, thresholds and ownership to the scope that was actually decided.
Template traceability
Editorial revision of this page.
Revision 1.1
- Reviewed on 22 August 2026
- Editorial owner: Marketing Plan in Action
- Counter-example, blocking check and visible history added.
- This revision describes the page; the CSV retains its own version field when present.
Explore the method