> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spherecast.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Building consensus

> Agree the final demand number and push it down into supply planning

## What this page is for

**Consensus** is the final agreed demand number — the one that flows into supply planning and drives what your company makes and buys. This page covers how to set Consensus, how to collaborate on it, and how to freeze the plan so you can measure accuracy later.

> "Consensus" can be renamed per company. The default is used here.

## The main way to set Consensus: Push down

**Push down** copies one row of the ladder into Consensus in a single step. Open the **"Updating demand on …"** dropdown and pick the source. Each entry reads "X → Consensus":

| Push-down option                 | What it copies into Consensus           |
| -------------------------------- | --------------------------------------- |
| **Baseline → Consensus**         | The raw statistical forecast            |
| **Baseline Adj. → Consensus**    | Baseline plus included adjustment lines |
| *(each custom line)* → Consensus | That specific adjustment line           |
| **Targets → Consensus**          | The top-down goals                      |

### What happens when you confirm

A confirmation — **"Push down & trigger supply plan re-run"** — warns that the action **can't be undone**. If you haven't filtered to a specific product or channel, it also warns that you're updating **all** products and channels.

* For a **single product**, the push-down completes immediately.
* For a **broader scope**, it's **queued**, and you're notified in your inbox when it's done.

Pushing down always **triggers a supply-plan re-run** so supply planning works from the new number.

## Other ways to set Consensus

* **Inline edit** — S\&OP managers can type directly into Consensus cells.
* **Upload** — load Consensus values in bulk (see **[Import & export](/guide/demand-planning/import-export)**).

## Collaborating on the plan

* **Accept / Reject adjustments** in the sidebar. Adjustments are marked **Top down** or **Bottom up**, so you can see whether a change came from leadership goals or from the field. See **[Adjustments](/guide/demand-planning/adjustments)**.
* **Notes** — threaded comments per product and channel, so context lives next to the numbers.

## Freezing the plan: Snapshots

From the toolbar, take a **Snapshot** to freeze the current plan exactly as it stands. Snapshots are what later let you compare the forecast you committed to against what actually sold. See **[Forecast accuracy](/guide/demand-planning/forecast-accuracy)**.

## Step by step: agree and push down Consensus

1. Work through and **Accept** the adjustments that belong in the plan.
2. Confirm Baseline Adj. reflects those accepted changes.
3. Open the **"Updating demand on …"** dropdown and choose **Baseline Adj. → Consensus**.
4. Read the confirmation. If you meant to cover everything, proceed; otherwise cancel and filter first.
5. Confirm **Push down & trigger supply plan re-run**.
6. Take a **Snapshot** so you can measure accuracy later.

## Example

After the review meeting, a planner has accepted three adjustments for the Retail channel. Baseline Adj. now reads 13,500 cases for March. They filter to Retail, choose **Baseline Adj. → Consensus**, and confirm. Because the scope is broad, the job is queued; an inbox notification confirms it finished. Supply planning re-runs against 13,500 cases, and the planner takes a snapshot to check accuracy next quarter.

> **Tip:** Push down is one-way and can't be undone. Filter to the exact scope you intend before confirming — the warning about "all products and channels" is there for a reason. Consensus then flows into **[Supply planning](/guide/supply-planning/overview)**.