Suppose your order forecast counts 100 distinct orders due for delivery over the next four weeks. One economic headline sounds encouraging, another points to a weaker market, and you have a staffing decision on Friday. Which number should the team use?
Start by keeping three decisions separate. You can hold the current base, show what would happen in a separate downside scenario, or revise the base when you have new evidence about the orders it contains. Put the reason beside whichever number you give the team.
Set the decision before reading another headline
Choose one line in the forecast. Write down the product, customer segment, delivery window and unit. If the line counts distinct orders, keep that unit throughout. If it counts items, reconcile the quantities on each order line. Ten orders and ten items describe different things. Decide whether the window refers to orders placed or orders due for delivery and stick with that choice.
Write down what this number will be used for, who can revise it and when they need to decide. Save the current forecast and its order extract with the same as-of cutoff. If you compare two extracts later, keep the delivery window fixed or show separately which orders moved across it. That makes a change in bookings easier to distinguish from a change in the dates you counted.
Check what each signal can tell you
Give each signal a short record. Write down what was observed, whose activity it represents, the dates it covers, the release date, the unit and any revision or timing limits. Then write one sentence about how it might reach your segment. If you cannot name that connection, use the signal to frame a question for the sales team.
A historical example
The Bank of Canada’s Q3 2026 survey reported stronger average sentiment. Interviews with about 100 firms ran August 6 to September 2, mostly before trade talks broke down. The Bank released the survey on October 19. Bank of Canada’s October 19 survey
In its October 30 release, Statistics Canada reported that seasonally adjusted real GDP across all industries was essentially unchanged in August 2026 from revised July. August was preliminary. Statistics Canada’s October 30 GDP release
One describes surveyed expectations. The other estimates national output for an earlier month. Neither supplies your order count.
Check what changed in your own order book
Open the earlier and current versions of the order extract. Match each change to an order ID and a dated record. A customer’s confirmation can change an order’s status. A cancellation can remove it. A new delivery date can move it outside the window without cancelling it. Keep those events separate so you can explain how they affect the line you plan to revise.
If a provisional order becomes confirmed, check whether the base already included it. Move it between categories if it was already counted. Before you add a replacement, check its order ID, eligible segment and delivery window. Treat a rumour, an undated note or an unresolved quantity as an open item. Write down who can resolve it and when you will check again.
Work three outcomes on the same forecast
This business, its records and all of the numbers below are fictional. A supplier is planning deliveries for one product to its regional distributor accounts in Weeks 1–4. Its saved base is 100 distinct orders, with 80 confirmed and 20 provisionally counted. Each order counts once. The forecast owner keeps the segment, window and other assumptions fixed while the team checks changes.
Hold the base at 100. At the first cutoff, the team has mixed economic headlines and no new dated order evidence. The earlier order extract still supports the same categories. The forecast owner keeps 100 and asks the sales lead to check whether any account has moved an approval or delivery date.
Show a separate scenario at 80. Before the next cutoff, the sales lead learns that an approval delay could affect the provisional group. The group’s status remains open. If none of the 20 provisional orders converts and all 80 confirmed orders hold, the scenario is 80. Keep the base at 100 in this step and label 80 with its assumptions and cutoff. Give operations the scenario if it needs to test what it could defer. The scenario does not estimate the chance of the delay.
Revise the base to 88 when the evidence changes. At the later cutoff, dated records show cancellations of 12 distinct confirmed orders, C01 through C12. Four orders already in the provisional group, P01 through P04, have confirmed in the same delivery window. The confirmed count is 80 minus 12 plus 4, or 72. The provisional count is 20 minus 4, or 16. The revised base is 72 plus 16, or 88. The four confirmations move between categories. The 12 cancellations explain the whole reduction from 100 to 88.
Keep the earlier 80 scenario with its original cutoff and assumptions. If someone wants a downside scenario after the cancellations, check the new order book and label the new calculation with the later date. That gives the team a record of which evidence was available when it made each decision.
Copy the decision record into your review
Input and purpose. Record the eligible segment, product, order unit and delivery window. Name the decision it feeds and the person accountable for the forecast input.
Cutoffs and supporting records. Save the previous extract and current version. Attach the dated cancellation, confirmation or schedule evidence by order ID. Flag changes to the counting window.
Signal and relevance. Keep the external observations and what each can help you investigate. Note the local evidence you need to act on that question.
Base and scenario. Record the previous base, any separately dated scenario with its assumptions, and the revised base if applicable. Show which changes affected the total and which only moved orders between groups.
Open item and next check. Give each gap a named owner and a date or event for follow-up. Record who will transfer an approved change to the forecast.
In the fictional file, the forecast owner logs the earlier 100 base and 80 scenario, then updates the Week 1–4 order input to 88 at the later cutoff. The dated records for C01–C12 and P01–P04 stay with the updated extract. The sales lead checks the remaining 16 provisional orders at the next cutoff or when their customer confirmations arrive.
A separate note in the same file says an account might cancel confirmed order C27. There is no dated cancellation at the cutoff. The forecast owner keeps C27 in the confirmed group, asks the sales lead for the customer’s dated instruction and sets a review for the next order extract. If C27 later cancels, it gets its own event and is checked against the then-current version. It has no effect on the 88 in this example.
When the input is settled, transfer it once into the forecast and let that model carry the consequences. If you need to connect the new order number to revenue, costs and cash timing, see how to build a business-sale forecast a buyer can follow.
For general information and education, not legal, tax, investment or valuation advice. Examples are illustrative and do not predict your business’s value, financing terms or sale outcome. Consult qualified advisers about your situation.
Subscribe to Deal Flow Canada for practical owner guides and Canadian deal updates.


