Comp plan launches fail in two phases. In the 90 days before launch, when someone realizes the plan document hasn't been signed by legal yet. In the 90 days after launch, when reps are still asking what their quota is because no one ever sent a formal communication. Both failures share one root cause: nobody built a working-backwards timeline with critical path dependencies.
This tool generates that timeline. Ten standard milestones mapped backwards from your effective date, adjusted for team size and plan complexity, with days-of-slack calculated per milestone against industry benchmarks. Any milestone showing negative slack means that phase is already compressed today — you're either doing it at double pace or skipping a critical step.
The ten milestones — and why each matters
Design + approval phase (T-90 to T-60)
Plan design finalized → Comp Committee approval → Legal/HR review. This is where most plans get scoped. Skipping Legal/HR review is the #1 source of post-launch disputes because nobody stress-tested clauses that seem obvious until a rep's lawyer reads them.
Build phase (T-60 to T-30)
Plan document drafted → SPM/calculator configured → Manager training. SPM configuration is the phase most likely to slip — every plan has edge cases that don't map cleanly to standard config. Allow more buffer here than you think you need, especially for complex plans.
Communication phase (T-30 to T-0)
Rep announcement → 1:1 plan reviews → Signed plan documents collected → Effective date. A signed plan document before the rep's first deal is both a legal and a trust requirement. Working deals under an unsigned plan is a dispute waiting to happen.
Post-launch (T+30)
30-day review. Check that calcs are running, statements are landing, and reps are asking the questions you expected. This is not technically a launch milestone — but teams that skip it learn about plan problems 60 days later when the first statement ships.
The day counts are observed from hundreds of comp plan launches. Simple plans (single-rate, single-quota, single-country, <30 reps) can compress to 60 days total. Complex plans (multi-product, multi-region, >100 reps) need 120+ days of runway. The tool scales the benchmarks by your team size and complexity selection — negative slack means you're attempting a compression the historical data says breaks 70%+ of launches in that phase.
Launch Timeline Builder
Tell us your effective date. We'll generate the working-backwards timeline.
ℹ️ How this tool works +
The question it answers: For my plan launch, what are the required milestone dates — and which ones are already compressed given how close today is to the effective date?
What to enter:
- Plan Effective Date — when the new plan takes effect (Day 0).
- Today's Date — used to calculate remaining slack against each milestone. Defaults to today.
- Number of Reps — affects training, 1:1, and signing time.
- Plan Complexity — Simple: single rate, single quota, single country. Moderate: 2-3 rates, territory rules, 1-2 countries. Complex: multi-product, multi-tier, multi-region, overlays.
- Geographic Scope — single-country or multi-country (adds lead time for Legal review in multi-country).
What you'll get back:
- A 10-milestone timeline with target date for each, working backwards from effective date.
- A days-of-slack calculation per milestone: positive = you have buffer, zero = on critical path, negative = already compressed today.
- An overall launch risk band based on how many milestones show negative slack.
- A risk-mitigation list with specific recommendations for any compressed milestones.
Defaults assume an effective date ~4 months out for a moderate-complexity 50-rep plan. Edit for your situation.
Benchmarks, ranges, and default values in this tool reflect Falcon's practitioner experience across consulting engagements. They are directional starting points, not substitutes for market survey data. For binding compensation decisions, validate key figures against Radford, Mercer, Carta, or WorldatWork survey data for your specific geography, industry, and company stage.
How to act on the timeline
All milestones with ≥7 days slack — On track
You have room. Resist the temptation to compress — use the buffer to run a second legal/HR review, pilot the rep communication with 2-3 managers before the formal rollout, or shorten the post-launch review to 14 days for tighter feedback.
1-2 milestones compressed — Selective remediation
Identify which milestones are compressed and compare them to the risk list. If the compression is in Build phase (SPM config, manager training), add resources or simplify scope. If it's in Communication phase, that's usually fixable by scheduling more hours rather than adding time.
3+ milestones compressed — Delay the launch
When multiple phases show negative slack, the real risk isn't any single milestone — it's that every milestone becomes first-try-only with no room for discovery. In our experience, compressed launches consistently produce significantly more post-launch disputes — we commonly observe 40%+ increases. Push the effective date 30 days if you can.
5+ milestones compressed — Not launchable on time
Either delay to a realistic date, or dramatically reduce plan scope. Launching a complex plan on a timeline this compressed is the most common path to the plan being quietly abandoned 6 months later. Better to ship a simpler plan on time than a complex plan that erodes trust from day one.
Every compressed launch has a meeting where someone says "let's just launch and fix things in the first 30 days." Launches that follow that logic produce disputes for 12+ months. The plan document becomes a living document no one trusts because it keeps getting re-issued. Fixing the timeline upfront is always cheaper than fixing it after launch.
Launching a new plan?
We help SalesOps teams build realistic launch timelines and execute them without slippage. Talk to us early — the best time is 6 months before effective date.
Book a 20-minute consultation →FAQ
The milestones are similar but compressed. Skip plan design if you're adjusting rates only; keep Legal/HR review and all of the communication milestones. A material change to an existing plan should still have 60+ days of runway to avoid surprises.
Start plan design in early Q3 of the prior year. Comp Committee approval by end of October. Plan document finalized mid-November. SPM config by early December. Rep announcements by mid-December. Signed plans by Dec 31. This gives ~120 days — the minimum realistic window for a moderate-complexity enterprise plan.
Managers are the first line of plan interpretation. If they don't understand the plan, their reps will get 40 different answers to the same question. Manager training is also where you find the plan's weak spots — managers will ask the questions reps will ask, and you'll fix them before launch.
Technically yes, but don't. The 30-day mark is when the first statement cycle completes for most plans — it's the earliest point you know whether the plan is working as designed. Missing this checkpoint means the first signal you'll get about plan problems is when the second cycle's disputes arrive.