# Publish and correct a forecast in the forecasting app

The forecasting app builds a month-by-month revenue forecast from a merchant's own sales and ad history. It separates the revenue into three forces: the organic growth trend, seasonal patterns and the impact of ad spend. This article covers the loop that matters most: correct the months the model learns from, plan your budgets, and let the result publish to MixShift so your reports and Claude read the same forecast.

The app is open to every organization. Sign in once at build.mixshift.ai and open it from there. See [Sign in once at build.mixshift.ai and open your apps](/knowledge-base/shared/getting-started/sign-in-once-and-open-your-apps).

## Correct a forecast

1. **Pick a merchant.** Only merchants with both sales and ad history are listed.
2. **Open the Data tab.** It shows the months behind the model: what the database holds, plus your corrections, budgets and notes. Only complete, final months train the model, at least 6 and ideally 18 or more.
3. **Fix what the account could not supply.** Months with missing ad spend, gaps or a figure you know is wrong are yours to enter or correct. Click a cell and type the value. To go back, restore the source value.
4. **Leave out a month that should not count.** Choose **Ignore** to keep a month out of the model, and **Include** to put it back. If the app flags a month, it explains why in the Note column.
5. **Plan budgets.** Edit any future month in the **Table**, or set targets and allocation in the **Planner**. Budgets are set on the revenue side, so the ad budget column on the Data tab is read only.
6. **Read the result.** The model retrains after each change. The **Charts** and **History** tabs show the forecast, its range and what drives it.

To work in bulk, you can download a merchant's months as a spreadsheet, edit it and upload it. The app shows a preview of every figure that differs before it stores anything.

## How a forecast gets published

There is no Publish button. The app sends a merchant's forecast to MixShift on its own, a short while after the last change and once a day. To see where a merchant stands, open **Published to MixShift** in the Export menu. It tells you one of these:

- **Not published.** MixShift holds no forecast for this merchant yet, so reports and skills have none to read.
- **Unpublished changes.** The forecast changed after the last send. Reports and skills read the earlier one until the next send.
- **Published** with a date. Reports and skills are reading this forecast, and nothing entered in the app has changed since.
- **Last send did not land.** The message says when it failed and why. The copy reports read is older than the one in the app.

Only a merchant read from the warehouse can be published, not the demo and not an uploaded file.

## Where the published forecast shows up

- **Forecast Max** in Claude serves the forecast your team published, with its corrections, before it computes one. See [Get a forecast with Forecast Max](/knowledge-base/intelligence/how-to/get-a-forecast).
- **Monthly Report Max** reads published forecasts. See [Run Monthly Report Max](/knowledge-base/intelligence/how-to/run-monthly-report-max).
- The [Forecasting reference](/knowledge-base/intelligence/reference/forecasting) describes what the service serves.

## Read it as a baseline

The forecast is not a target to hit. It is a baseline that makes anomalies visible: a beat is worth understanding, and a miss deserves a closer look. Nearer months are firmer, and one-off peaks such as Prime Day are not modeled, so they show up as a beat and widen the range.

## Tell us what is missing

Use **Feedback** in the bar at the top of the app. A person at MixShift reads every note and replies to you personally. **Help** in your name menu opens the in-app guide.

## Related

- [Get a forecast with Forecast Max](/knowledge-base/intelligence/how-to/get-a-forecast)
- [Forecasting reference](/knowledge-base/intelligence/reference/forecasting)
- [Intelligence overview](/knowledge-base/intelligence)