---
title: "Get Started with Your Forecast with Templates"
canonical: "https://support.55degrees.se/space/SP/4456185859/Get%20Started%20with%20Your%20Forecast%20with%20Templates"
format: markdown
---
🧙‍♂️ To get started with your forecast, our **Forecast Templates** give you a **guided**, *simple* way to make <u>reliable</u> group forecasts without starting from scratch. 

Just pick a template that fits your needs, fill in a few details in an easy form, and get a ready-to-go group forecast. You can always switch to advanced settings if you want more control 😉

![Screenshot 2026-01-26 at 13.25.45.png](media://abe280e7-3b7c-4d52-89dd-9ef7eea99a43)

### What You Can Do with Templates

- Make consistent group forecasts quickly using tried-and-true defaults.
- Cut down setup mistakes and help new users get started easier.

> ℹ️ For full control over all options 👉 Create your forecast with the **Advanced setup **


### Available Templates

We started with templates for common portfolio forecasting cases. These are based on our [Group Forecast Recipe Book](https://support.55degrees.se/space/SPP/3964863219/Recipe+Book) (where these forecast are created from scratch using the Advanced Setup).

> ℹ️ Tip - Start with the template that fits your situation best. You can always tweak it after creating the forecast by **Editing** it or switch to Advanced mode for more detailed control.


### How to Create a Forecast Using a Template

Open Portfolio Forecaster and click ‘Create Group Forecast’. You’ll now see our the new forecast creation screen.

1. Pick a template. Each one has a description of when to use it and what info you’ll need to provide.
2. Fill in the template.   
**Name:** Give your Group Forecast a unique name.    
**Project or Board:** Choose the **data source** of your Parent Items.    
**Forecasted Item Type:** Choose the **Parent Item Type to be forecasted**.   
**Work Item Type:** Choose the **Child Item Type to be forecasted**.
3. Review your choices and generate the forecast. The app will create a group forecast based on the template and your inputs.

> ℹ️ **Defaults**: At the bottom of the page, you will see the default values included in the template
> ℹ️ 
> ℹ️ ![Screenshot 2026-07-02 at 16.27.02.png](media://bf5186a6-5dce-4666-bf0d-8fd84000305b)

#### How to Edit a Forecast

### Templates and Examples

> Macro (refined-tabs)
> 
> > Macro (refined-tab)
> 
> #### 📦 Full Epic Delivery in a Space/Board
> 
> ![Screenshot 2026-02-03 at 13.53.47.png](media://0c66475e-af2f-4733-8433-5945f058228c)
> 
> - The goal of the Full Epic Delivery is to Forecast when selected Epics will be fully done by teams in the chosen space or board.
> - Typical inputs would include a Space or Board, Epics, teams working on the board and a past throughput window.
> - The template is set to use past completed items per time period to run a Monte Carlo simulation; assumes normal work schedule with configurable days off.
> - This template offers the ability to
> 
> > ✅ This template offers the ability to use work items from a **different board or space for the historical throughput**. To do this, toggle the Throughput button and then select your Source and Issue types you want to use for the historical throughput.
> 
> ![epic-template.png](media://f4e302c6-d2ee-4e10-a9be-0d8e5e67873c)
> 
> **Example A: Deliver all Epics in Project X**
> 
> 1. Pick the Full Epic Delivery template and choose Project X’s board.
> 2. Filter for the Epics you want (or paste a saved filter). Pick all teams working on the board.
> 3. Choose a 90-day past window for throughput, then generate. Check percentile dates and capacity hotspots.
> 
> > ℹ️ Check out the Recipe: [https://support.55degrees.se/space/SPP/3964863402/Forecast+Full+Epic+Delivery+in+a+Jira+space+(or+board)](https://support.55degrees.se/space/SPP/3964863402/Forecast+Full+Epic+Delivery+in+a+Jira+space+(or+board))
> 
> > Macro (refined-tab)
> 
> #### 🤝 Single Team’s Work on Shared Epics
> 
> ![Screenshot 2026-02-03 at 13.53.30.png](media://21cdd221-a931-47f8-9a6e-18da8474c48b)
> 
> - The goal of the Single Team Work is to estimate delivery dates for the part of Epic work done by one team when Epics are shared.
> - Typical inputs would include a team, list or filter of shared Epics, team throughput or cycle time, percent of team time on these Epics.
> - The template is set to focus on team-specific throughput; lets you set percentage contribution per Epic to avoid overestimating capacity.
> 
> > ✅ This template offers the ability to break down your work more into segments using **Team or Label**. To do this, toggle the Breakdown button and then select your Breakdown Type and Value.
> 
> ![single-team-template.png](media://3d8fbc6b-8f48-43d7-afa6-f390201c06f4)
> 
> **Example B: One team on shared Epics**
> 
> 1. Pick the Single Team’s Work on Shared Epics template and select your team.
> 2. Choose the Epics and set your team’s percent contribution (like 40%).
> 3. Use your team’s past throughput; adjust calendar if needed. Generate and share confidence ranges with stakeholders.
> 
> > ℹ️ Check out the Recipe:[https://support.55degrees.se/space/SPP/3964863332](https://support.55degrees.se/space/SPP/3964863332)
> 
> > Macro (refined-tab)
> 
> #### 📈 Program-Level Work
> 
> ![Screenshot 2026-02-03 at 13.53.38.png](media://9288b089-b1b4-48b4-94c1-6f90e7e19aed)
> 
> - The goal of Program Level Work is to give a forecast across teams and Epics at the program level, combining team capacities and dependencies.
> - Typical inputs would include program scope (JQL/filter), teams involved, team calendars, past throughput per team, dependency info.
> - The template is set to add up team-level throughput; support staggered start dates and different schedules per team.
> 
> **Example C: Program-level cross-team plan**
> 
> 1. Pick the Program-Level Work template. Choose the program scope that covers all Epics.
> 2. Add teams involved and check their calendars. Map dependencies if you track them.
> 3. Generate the forecast. Check team contributions and overall delivery ranges; adjust scope or capacity to test ideas.
> 
> > ℹ️ Check out the Recipe: [https://support.55degrees.se/space/SPP/3964863247](https://support.55degrees.se/space/SPP/3964863247)

---

### When to Use the Advanced Setup

![Screenshot 2026-02-03 at 13.53.56.png](media://28601d0e-b6f6-4d2b-aab8-187135482955)

Use Advanced setup if you want to:

- Change distributions (like switching between throughput and cycle-time simulations).
- Set up complex scope rules (nested filters, exclusions).
- Adjust simulation settings (iterations, burn-in, confidence bands) beyond template defaults.
- Model advanced capacity cases (interruptions, work-in-progress limits, parallel work limits).


### Best Practices

> ℹ️ **Quick tips:**
> ℹ️ 
> ℹ️ - Use recent and relevant past data for your historical throughput. Try to avoid unusual disruption periods.
> ℹ️ - Choose your scope carefully. For Epic forecasts, make sure your Epics represent clear outcome chunks, not big, vague containers.
> ℹ️ - Match team calendars and days off to get realistic dates.


### FAQ

<details>
<summary>Can I save my own custom template?</summary>

Not yet. Right now, we focus on curated templates for common cases. But you can duplicate a forecast you made and tweak it for future use.
</details>

<details>
<summary>Can I switch from a template-created forecast to Advanced mode later?</summary>

Yes. Advanced mode is always available from the forecast settings, so you can fine-tune or go beyond the template defaults.
</details>

<details>
<summary>What if my scenario doesn’t match a template?</summary>

Choose Advanced setup to handle any unique or complex case. Or pick the closest template to save time, then customise.
</details>

<details>
<summary>How are dates determined in the forecast?</summary>

Dates come from Monte Carlo simulations using your chosen data (like throughput or cycle time), team calendars, and scope. The results show completion ranges based on percentiles, not single dates.
</details>

### Troubleshooting

| Question | Answer |
| --- | --- |
| I don’t see data for my team or project. | Make sure your data source includes completed items and you have permission to access them. |
| Confidence ranges seem too wide. | Try using a longer or more typical historical window, narrow your scope, or check for mismatched team calendars. |
| The forecast feels too optimistic. | Use higher percentiles when sharing (like 85th or 95th), check contribution percentages, and confirm dependency assumptions. |

---

### Related Resources

- [https://support.55degrees.se/space/SPP/3964863402/Forecast+Full+Epic+Delivery+in+a+Jira+space+(or+board)](https://support.55degrees.se/space/SPP/3964863402/Forecast+Full+Epic+Delivery+in+a+Jira+space+(or+board))
- [https://support.55degrees.se/space/SPP/3964863332/Forecast+a+Single+Team%E2%80%99s+Work+on+Shared+Epics](https://support.55degrees.se/space/SPP/3964863332/Forecast+a+Single+Team%E2%80%99s+Work+on+Shared+Epics)
- [https://support.55degrees.se/space/SPP/3964863247/Forecast+Program-Level+Work](https://support.55degrees.se/space/SPP/3964863247/Forecast+Program-Level+Work)