How can we help?

Initiative Features
🗓️ Managing Multiple Deployments with Impact Date Ranges

🗓️ Managing Multiple Deployments with Impact Date Ranges

🗓️ Managing Multiple Deployments with Impact Date Ranges

Many initiatives don’t follow a single go-live moment—they roll out in phases, with multiple deployments, staggered changes, and varying impacts across time. ChangePlan’s impact date range feature was designed specifically to support this reality.
By allowing you to define start and end dates for each individual impact, you can represent every phase of your initiative on the Change Impact heatmap.
 
notion image

✅ Why This Matters

If your initiative involves multiple deployments—whether by location, audience, function, or milestone—this feature gives you everything you need to:
  • Clearly show when each deployment will impact specific groups
  • Visually separate waves of change across the timeline
  • Accurately reflect real-world complexity in your rollout strategy
  • Ensure the Change Impact heatmap aligns with how change is actually experienced

🔧 How It Works

When creating or editing an impact:
  1. Open the Impact Details pop-up
  1. Select the "Choose Dates" option:
notion image
 
  1. Enter the Start Date and End Date to reflect the deployment window for that impact
Each impact will now appear on the heatmap across its defined timeframe, giving a true-to-life representation of when and where change occurs.

🧠 How to Handle Multiple Deployments

You don’t need to create separate initiatives for each deployment. Instead:
  • Add multiple impacts under a single initiative
  • Use different date ranges for each one
  • Assign each impact to the relevant group or audience
 
This allows you to:
  • Reflect a staggered deployment schedule (e.g. APAC → EMEA → North America)
  • Separate pilot phases from broader rollouts
  • Capture targeted releases (e.g. only one business unit at a time)

🔍 What You'll See on the Heatmap

Without Date Ranges
With Date Ranges
Impacts are tied to a single go-live date
Each impact appears across its actual timeframe
Overlapping deployments aren’t clearly visible
Each wave of change appears distinctly
Heatmap may look overly compressed or misleading
Heatmap shows a layered, accurate picture of deployment

🧪 Examples of Use

  • Multi-location ERP implementations: Different plants or regions go live in waves over 6 months
  • System upgrades by business unit: Finance in Q2, HR in Q3, Operations in Q4
  • Phased communications & training: Awareness in April, training in May, usage in June

💬 Final Thoughts

If you're managing initiatives with multiple deployments, this feature fully supports your needs. There’s no need to split the project into separate initiatives or request additional tooling.
Instead, simply use multiple date-defined impacts to model each deployment clearly and accurately—all in one place.
Need help applying this in your own initiatives? We’re here to help—reach out any time for setup guidance or a walkthrough.
Help Center