Conservative sales forecast: build a defensible downside case

A conservative sales forecast is an explicit downside scenario based on documented risks to volume, price or timing. Build it alongside the base forecast, reconcile the difference, and compare both with actual results; lowering a number deliberately does not make it more accurate.

1. Freeze the base and define the decision

Start with the current approved base workbook and preserve its date. State what management needs to decide: staffing, purchasing, discretionary spending or a contingency action. Define the sales period and whether the forecast measures orders, delivered sales or recognized revenue.

The SBA's business plan guidance calls for clearly explained financial projections and detailed quarterly or monthly projections in the first year. Apply that discipline here: a reviewer should be able to see which assumptions changed and why.

Export one row per customer, product and period, with region, quantity, net unit price, forecast version and revenue. Include a stable customer ID so renaming an account does not create an apparent gain or loss. If the base already weights uncertain opportunities, document that before applying another downside adjustment. The sales forecast categories guide explains that separate classification question.

2. Attach each risk to the rows it affects

Create an assumption register with affected customer or region, risk, evidence, changed input, owner and review date. For example, a customer's written notice of reduced orders is stronger evidence than an unexplained regional discount.

Competitive pressure can affect price and demand differently. The SBA's market research guide treats demand, market saturation and pricing as separate questions. Keep them separate in the assumptions sheet as well, so a price reduction does not silently become a volume reduction.

Specify which risks can happen together. A delayed shipment moved into a later month should leave the current month and enter the later one. A cancellation should leave both. Use a forecast bridge for a detailed account-level explanation when the changes are numerous.

3. Calculate the downside by customer and region

An illustrative US distributor sells a standardized service package. Its quarter has these base quantities and prices. The downside assumes reduced customer orders in each region and an additional price concession for Redwood Stores.

Put those columns in A:G, with Harbor in row 2. Add H for downside quantity, I for downside price, J for downside sales, and K for the change from base. In E2:

=C2*D2

In H2:

=C2*F2

In I2:

=D2*G2

In J2:

=H2*I2

In K2:

=J2-E2

Fill down through row 4. Enter factors as percentages. The calculations produce:

The downside is $37,400 below $240,000, or 15.6% lower, rounded to one decimal place. Redwood's revenue is 80 × 85% × $1,000 × 95% = $64,600. Do not add its volume and price reductions together; the reduced price applies to the packages still sold.

4. Prove the change and compare actuals

Separate the volume effect at base prices from the price effect on downside quantities. This ordering keeps their interaction in the price effect and avoids an unexplained residual.

With the same layout, calculate the volume effect in L2 and fill down:

=(H2-C2)*D2

Calculate the price effect in M2 and fill down:

=H2*(I2-D2)

Use Excel's SUM function for the total check:

=SUM(E2:E4)+SUM(K2:K4)-SUM(J2:J4)

The total check must be zero: $240,000 − $34,000 − $3,400 − $202,600 = $0. Reconcile each region's total to its customer rows before combining the regions.

Suppose Redwood later records these actual sales:

Actual sales are $70,000 − $64,600 = $5,400 above the downside. Keep the base comparison too: exceeding a downside case does not prove the original plan was achieved. Review the evidence at the sales forecast meeting, with an owner for each assumption still unresolved.

Where it goes wrong

• One haircut across everything. It hides which accounts and risks actually explain the exposure.
• The same risk counted twice. Removing uncertain orders and then cutting their revenue again overstates the downside.
• Incompatible assumptions. A capacity constraint and a demand collapse may not justify independently multiplying every row by both reductions.
• Timing treated as permanent loss. Shifted revenue should appear in the receiving period when delivery remains supported.
• A moving base. Overwriting the original forecast prevents a fair test of the decision management made.

For an operation without sales history, use the new business sales forecast to establish explicit starting assumptions before building a downside.

Compare your base and downside files in Covirage

Bring the base forecast, downside workbook and actual sales export to Covirage, with matching customer and period fields. Covirage maps the columns, and its tools compute and check the supplied comparisons; the external AI model explains the differences with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See forecast analysis for the questions this supports in a sales review.

Covirage is not affiliated with Microsoft.