Upstream object
Name the prerequisite.
A verifiable output is expected.Structured template · MOD-14
Dependency map to download: fields and controls
Decision question
Which upstream delay could prevent a downstream initiative from starting or delivering?
Editable CSV file
The template’s required fields.
This file is used to secure, bypass or rephase a dependency before it blocks the roadmap. The related guide page explains the method. Here, the scope is limited to the columns, checks and example needed to complete the deliverable.
Downstream object
Identify what depends on the prerequisite.
The link is direct.Required date
Fix the downstream need date.
It precedes the dependent start.Fallback
Prepare a degraded mode.
Its cost and limit are visible.Example structure
A concrete reading before completing the file.
| Upstream | Downstream | Required date | Fallback |
|---|---|---|---|
| Offer approval | Messages | 12 September | Restricted version |
| Pricing | Sales training | 20 September | Provisional range |
Checks before use
- Direct link
- Required date
- Upstream owner
- Documented fallback
Counter-example
Completing “Upstream object” without satisfying “A verifiable output is expected.” 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 dependency map↓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