How Do You Forecast an Event's Outcome?
Event forecasting is predicting what an event will produce — before you approve the spend — so the decision to run it rests on an expected return, not a hope. A forecast turns “this should be worth it” into a number you can check afterward. That's the whole point: it makes an event a test with a stated expectation instead of a bet you evaluate emotionally once it's over.
Why forecast at all
Most events get approved on conviction. Someone believes in the conference, the room nods, the budget clears. Then — if the event gets measured at all — it's judged after the fact on whatever number was easiest to pull. Nobody ever wrote down what the event was supposed to do, so nobody can say whether it did.
That's the gap forecasting closes. Without a forecast, you can't tell a good outcome from a lucky one, or a genuinely bad event from a good event you simply predicted wrong. The retro has nothing to push against. A forecast is what gives the “prove” step something to prove against — it's the standard the actuals get marked to.
What to forecast (leading indicators, by intent)
Forecast the return the event's intent should produce — not a generic number. A pipeline event forecasts qualified meetings and sourced opportunities; a brand event forecasts reach and the right rooms; a developer event forecasts activations. Forecasting “revenue” for all of them is how you end up unable to forecast most of them.
And forecast the leading indicators, not just the lagging ones. Pipeline and revenue land months later — too late to check your forecast while it still matters. Meetings booked, ICP attendance, follow-ups scheduled, demos requested — those show up within days and tell you fast whether the event tracked to plan. Forecast the things you'll actually be able to mark against reality soon enough to learn from.
Put it on the record
A forecast you keep in your head is a wish. A forecast you write down before the event and mark against the actuals after is a learning loop — the single fastest way to get better at allocating an events budget.
The value isn't being right. It's the gap between forecast and actual. That gap is the most useful number a forecast produces: it tells you whether to trust your instinct next time, where you systematically over- or under-predict, and which event types you read well versus poorly. A team that forecasts on the record for a year knows things about its own portfolio that no amount of post-event reporting can teach.
Forecast accuracy is about calibration, not outcome
Here's the part most people get backwards: a forecast isn't graded on the event doing well — it's graded on the forecast being close.
Forecast 30 qualified meetings and get 30: an excellent forecast. Forecast 30 and get 90: a great event and a bad forecast — your instinct undershot by 3x, and that's a planning signal worth as much as the wins. It doesn't mean the event failed; it means your read of it was off, and next time you can plan and budget with a truer number. Calibration cuts both ways: a wildly beaten forecast and a wildly missed one are both telling you the same thing — recalibrate.
That's why forecast accuracy sits alongside an event's performance, not inside it. How the event did and how well you predicted it are two different questions, and a serious team wants both answers.
The common mistakes
- No forecast at all. The event gets approved on belief and judged on vibes; the retro has nothing to measure against.
- Forecasting only the lagging number. Revenue-only means you can't check the forecast until it's far too late to learn.
- Forecasting to justify. Padding a forecast to clear approval poisons the one number — the forecast-vs-actual gap — that would have made you smarter.
- Never marking forecast against actual. A forecast you don't reconcile is just a nicer-looking guess.
- Reading a beaten forecast as pure success. Blowing past your forecast is worth celebrating and recalibrating — the miss in your prediction is real information.
How Dott forecasts
Forecasting is the second phase of the loop:
Plan — set the intent and budget, so the forecast has something to be about.
Forecast — predict the return that intent should produce, on the record, before spend is approved.
Prove — capture what actually happened.
Score — mark the forecast against the actuals (that's forecast accuracy), show it alongside the event's proven outcomes, and roll it into the Dott Score — so the whole thing gets more calibrated every event.
The result isn't a crystal ball. It's a portfolio that gets measurably better at predicting itself — which is what lets you approve the next event on an expected return instead of a hope.
Key terms
- Event forecasting
- Predicting what an event will produce before the spend is approved, so the decision to run it rests on an expected return rather than a hope — and the outcome can be marked against the prediction afterward.
- Expected return
- The outcome an event is forecast to produce relative to its planned investment — the basis for deciding whether it's worth running before it runs.
- Forecast accuracy
- How close an event's forecast landed to what actually happened. A measure of calibration, not outcome: a forecast that gets wildly beaten was still a bad forecast, and that gap is a planning signal.
- The Dott Score
- A single 0–100 verdict for an event, layered from how well it was planned, how close the forecast landed to reality, and what the event actually proved — weighted by what the event was for. The shared scale that makes a portfolio comparable.
Frequently asked questions
How do you forecast an event before it happens?
Predict the return the event's intent should produce — qualified meetings for a pipeline event, reach for a brand event — and write it down before you approve the spend. Forecast leading indicators (meetings, attendance, follow-ups) you'll be able to check soon, not just lagging revenue.
Should you forecast revenue or leading indicators?
Both, but lead with the leading indicators. Revenue and pipeline are lagging — they arrive too late to check the forecast while it's actionable. Leading indicators show up within days and predict the lagging return, so they're what make a forecast a usable tool instead of a post-mortem.
How accurate does an event forecast need to be?
Accuracy is about calibration, not perfection. The goal isn't to nail the number — it's to close the gap between what you predict and what happens over time, so your reads get truer. A forecast that's consistently off in the same direction is more useful than an occasional lucky bullseye, because it tells you exactly how to adjust.
How is forecasting different from setting a goal?
A goal is what you want; a forecast is what you expect. Goals motivate; forecasts get marked against reality. Confusing the two is how forecasts get padded — and a padded forecast destroys the one number worth having.
How does forecasting connect to the Dott Score?
The forecast is what the actuals get measured against. Dott marks the two (forecast accuracy) and rolls it into the Dott Score, so an event that was planned well, predicted closely, and delivered scores higher than one that got lucky — and the whole portfolio gets more calibrated every cycle.
The standard
Forecasting isn't about being right. It's about making every event a test with a stated expectation — so the retro means something, the misses teach you, and the next event gets approved on an expected return instead of a feeling.
Dott. is the Event Portfolio Intelligence System. Plan → Forecast → Prove → Score.