This page explains how a team chooses the confidence level at which it commits a release date in Release Management, Roadmaps & Product Portfolio for Jira, and what the P50, P85, and P95 levels mean. It is a neutral, factual reference for how the capability works; for the narrative behind the decision, see the related article linked below.

What a commitment confidence level is

Release Management, Roadmaps & Product Portfolio forecasts a release date as a band of three dates at three confidence levels, derived from Monte Carlo simulation against the team's actual Jira throughput rather than a single typed-in date. The commitment confidence level is the percentile a team decides to commit at — the point on that band it is willing to promise against.

The three levels

• P50 — the date the team would meet roughly half the time. Aggressive; suitable as an internal target, risky as an external promise. Comparable to the stretch or uncommitted end of a Program Increment objective.

• P85 — the date the team would meet roughly five times out of six. The level most SAFe teams treat as committable, and the app's default on-track threshold. It is the data equivalent of a confident fist-of-five vote.

• P95 — a conservative, high-certainty read. Appropriate when a missed date carries a high cost, such as a regulated launch, a contractual deadline, or a pre-announced event.

Choosing the level: match it to the cost of a miss

The percentile is chosen by the team, not computed by the app. The simulation places each date on the calendar; which one to commit to is expert judgment that depends on information only the team holds — how costly a miss is, who is relying on the date, and how much of the scope is still soft. A practical rule of thumb:

• Low cost of a miss (an internal demo slips a week) — commit at P50 and move quickly.

• Moderate cost (a difficult conversation with a customer or executive) — commit at P85, the honest default for most release commitments.

• High cost (penalties, compliance risk, or an advertised launch) — commit at P95 and protect it.

Why the chosen level has to stay live

A confidence level chosen once is only accurate at the moment it is chosen. Over the eight-to-twelve weeks of a Program Increment, scope changes, dependencies surface, and capacity shifts — and each of those erodes the margin that made the chosen level meaningful, without moving the date on the board. Release Management, Roadmaps & Product Portfolio recalculates the confidence percentage continuously against the committed date, tracking those three inputs in days, so a level committed at 85% that has drifted to (for example) 62% becomes visible while there is still time to renegotiate scope or move the date deliberately. See Keeping a committed release date honest for how scope, dependencies, and capacity are each tracked.

Where it runs

Confidence calculations run natively inside Jira Cloud on Atlassian Forge. No data is exported to an external service to perform the calculation.

Related

• Article: You Committed to the Date — But at What Confidence?

• Article: Your Release Date Reads "85% Confident." Here's How to Read It

• Article: Your Fist of Five Was Right on Day One. Is It Still Right on Day Thirty?

• Article: The three things that erode a committed release date

• Page: Live Confidence Bands: how they keep a PI confidence vote current

• Marketplace: Release Management, Roadmaps & Product Portfolio for Jira on the Atlassian Marketplace