Nominal gates, evidence-opening windows, and risk-adjusted approval landingsLive current inputs
Date & Time
Week Number Milestone Calculator
Place evidence-bearing milestones on an ISO-week program, then quantify approval yield, review lead time, dependency lag, rework allowance, and the confidence buffer before the final gate.
Buffered final gate—
Nominal milestone span—
Expected total rework—
Dependency-lag burden—
First evidence opening—
Expected first-pass approvals—
Buffer coverage ratio—
Milestone confidence—
Milestone evidence rail
Nominal gates, evidence-opening windows, and risk-adjusted approval landings
Each milestone carries three aligned markers: evidence opens, nominal gate, and expected landing after dependency and rework burden. The final buffer is a separate protected zone.
Milestone assurance register
Every gate with its ISO label, evidence lead, expected rework, and buffer consumption
The register turns a decorative milestone list into a reviewable assurance plan.
| Milestone | Evidence opens | Nominal gate | Expected landing | First-pass yield | Risk days | Buffer left |
|---|
Milestone setup
Model the review system behind the dates
- Anchor milestone one to an approved ISO week.
- Set spacing from actual dependency cadence.
- Enter when evidence must be ready before each gate.
- Use observed first-pass approval and rework duration.
- Keep the final confidence buffer separate from task duration.
Assurance logic
A gate date is not an approval date
The nominal gate is when a decision is requested. Evidence must open earlier, while approval can land later because of handoff and rework risk.
Expected rework is a planning mean, not a promise about a specific milestone. The rail therefore shows both nominal and risk-adjusted positions instead of replacing one with the other.
Calculation method
Risk-adjust each gate without pretending rework is certain
Nominal gates use the entered spacing. Expected rework equals failure probability times rework duration; dependency lag accumulates between gates. The confidence buffer is then compared with the expected accumulated risk burden.
Detailed calculation process and general formulas
g_i = start + (i - 1) * 7se_i = g_i - Lr = (1 - p/100) * Ra_i = g_i + (i - 1)d + i*rcoverage = 7B / ((m - 1)d + m*r)Symbols, meanings, and units
- s
- nominal milestone spacingweeks
- L
- evidence opening lead before each gatedays
- p
- first-pass approval ratepercent
- R
- rework duration after a failed reviewdays
- B
- protected confidence buffer after the nominal final gateweeks
Gate-quality signals
Read the milestone system from four angles
Date spacing alone cannot explain review readiness.
Evidence horizon
—When preparation for the first decision must begin.
Approval yield
—Expected gates accepted on the first review.
Risk burden
—Expected rework accumulated across all gates.
Protected landing
—Final nominal gate plus the explicit confidence buffer.
Decision takeaway: Track evidence opening, nominal gate, and expected approval landing as three different dates.
Governance checks
Keep confidence assumptions observable
- Calculate approval rate from comparable gates.
- Measure rework until approval, not until resubmission.
- Do not hide dependency lag inside spacing.
- Escalate when expected risk consumes the protected buffer.
Milestone evidence
Sources for the approval assumptions
- Gate review history
- Evidence-completeness checklist
- Approval and resubmission timestamps
- Dependency acceptance logs
- Program baseline calendar
Practical applications
Decisions this calculator is designed to support
Product assurance gates
Six certification gates occur every three ISO weeks with an 82% first-pass approval rate.
What the result clarifies: The rail shows whether a two-week confidence buffer absorbs expected review friction.
Grant reporting milestones
Evidence must open four days before each sponsor review and handoffs add two days between stages.
What the result clarifies: The first evidence date reveals work that starts well before the published milestone.
Worked example
Current-input substitution and reconciliation
Model limitations
Expected rework is a probability-weighted planning value and cannot predict which gate will fail. Correlated failures, parallel reviews, hard holidays, and dependency networks require a more detailed schedule-risk model.
Week Number Milestone Calculator FAQ
Why separate nominal and expected landing dates?
The nominal date requests a decision; the expected landing includes average dependency and rework burden.
Is approval rate entered as a decimal?
No. Enter a percentage such as 82; the formula converts it to 0.82.
Can the buffer coverage exceed 100%?
Yes. That means the protected buffer is larger than the modeled expected risk burden.
Does expected rework mean every gate is delayed?
No. It is an average allowance across many comparable gates.