Free template · Delivery forecast
Delivery forecast update template for Jira teams
“When will it be done?” deserves a range with odds, not a single date that everybody knows is wrong. This weekly delivery forecast update gives stakeholders a likely date, a safe date and the one decision you need from them.
Delivery forecast: [release or epic], week of [date]
1. In one sentence
[Likely by [date]; very likely by [date]. Changed since last week because [reason].]
2. Dates
| Confidence | Date | Last week |
|---|---|---|
| 50% (likely) | [date] | [date] |
| 85% (safe to promise) | [date] | [date] |
3. Inputs
Work items left: [number] (scope added this week: [number]). Items finished per week over the last [6] weeks: [numbers]. Method: [Monte Carlo on throughput / other].
4. Risks
- [Risk, impact on the dates, owner.]
5. Decision needed
[Cut scope / accept the date / add people], by [name], before [date].
Copied. Paste it into a new Confluence page.
How to use it in Confluence
- Click Copy the template, open a new Confluence page and paste: headings, lists and tables stay as they are.
- Replace the parts in [brackets] and delete what does not apply to you.
- To reuse it, save it as a space template: Space settings › Templates › Create template, then paste.
Three habits that keep forecasts honest
- Count items, not story points. Throughput from the work your team actually finished is easier to check and usually as accurate.
- Show what changed. A date that moves is normal; a date that moves without a reason loses trust.
- Promise the safe date. Plan with the likely date, commit to the 85% one.
Related: how to forecast a release date in Jira and Monte Carlo forecasting, explained simply.