> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.robaws.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How does the forecast in the project planning work?

At the top of the [project planning](https://support.robaws.com/en/article/project-planning-wfhgep/) there are two rows with the **forecast**: **Workdays** shows how many employees you need per day, and **Financial** shows per month what you expect to invoice and what has already been invoiced. Robaws calculates those figures itself, based on the phases of your projects and quotations. Below you can read how, so you know what to fill in to get a correct forecast.

| A phase only counts if it has a start and an end date, and if the project or quotation has a status from **Project statuses** or **Quotation statuses** in the [settings](https://support.robaws.com/en/article/project-planning-settings-18og10y/#2-settings). If you leave those empty, all projects and quotations count.

## Workdays: how many employees per day?

In the **Workdays** field of a phase you fill in the **total number of workdays**: the number of employees multiplied by the number of days they work on that phase. You do that on the project (**Planning** tab, sub-tab **Project planning**) or on the quotation (**Financial planning** tab).

Robaws divides that total by the number of days from Monday to Friday between the start and the end date of the phase, and rounds up. That is the number of employees per day for that phase. If several phases run on one day, Robaws adds them up.

*Example: a phase runs from Monday to Friday, but you work on it for 3 days with 3 employees. You fill in 9 for Workdays (3 × 3). Robaws divides that by 5 workdays: 1.8, rounded up to 2 employees per day.*

* Saturday and Sunday do not get a figure, but a grey cell.
* Robaws does not subtract public holidays and [leave periods](https://support.robaws.com/en/article/entering-leave-periods-and-public-holidays-in-the-dayplanning-18enur3/). If you plan across a leave period, adjust your end date or your workdays.
* Preferably fill in whole numbers. Decimal numbers are allowed, but make the forecast less clear.

|| If a quotation is linked to a project and both are in the project planning, Robaws counts the workdays of both. In that case, fill in the workdays on only one of the two.

## Financial: forecast and realised

The financial forecast comes from the **financial planning of your quotations**. Per quotation phase you choose in the **Invoice** column how you invoice that phase. That determines the amount of the **Forecast**:

| Invoice | Forecast of the phase |
| ---- |
| Percent | The percentage you fill in, of the total of the quotation. |
| Fixed price | The fixed amount you fill in. |
| Final invoice | What remains of the total of the quotation, after the previous phases. |
| None | Nothing. |

As soon as you link an invoice to a quotation phase, its amount goes to **Realised**. How to invoice a phase is explained in [Financial planning on a quotation and project](https://support.robaws.com/en/article/financial-planning-on-a-quotation-and-project-1kfw4dy/#2-financial-planning-on-a-quotation).

* Robaws counts per **calendar month**. A phase counts in full in the month of its **end date**; the amount is not spread over the duration.
* All amounts are excluding VAT.
* An invoice that has not been booked yet also counts towards Realised.

||| The forecast only comes from quotations. Phases on a project do not contribute an amount, not even if you took them over from the quotation. If the status of your quotation changes to a status that is not in **Quotation statuses**, for example after approval, it disappears from the financial forecast. If you want to keep following it up, also add that status to **Quotation statuses**.