How Do You Score an Event?
Event scoring is the practice of reducing an event's planning quality, forecast accuracy, and proven outcomes to a single 0–100 verdict — the Dott Score — weighted by what the event was for, so unlike events become directly comparable. It replaces the usual mess — a different ad-hoc metric for every event, and no way to set two side by side — with one scale that every event carries. It's not a satisfaction survey and it's not a recap deck. It's the number that answers was this worth it, and which of our events earned the next dollar?
The problem it solves
Most events are graded on whatever was easiest to count. The conference gets measured on badge scans, the dinner on how the room felt, the webinar on registrations, the hackathon on tweets. Each number is real, and none of them are comparable. So when the year ends with thirty events and one budget, nobody can actually say which events earned their place — every event was justified on its own, run on its own, and remembered on its own.
The reflex, when a portfolio disappoints, is “we overspent.” It's almost never overspend. It's misallocation — money in the wrong events. You can't see that without a shared scale, because misallocation only shows up when you can line events up against each other and see that the dinner scored a 49 and the speaking slot scored a 95. Event scoring is that shared scale.
What a score is made of
A Dott Score isn't a single measurement — it's a layered read of the whole lifecycle, because an event can be strong in one phase and hollow in another. Three layers go in, and one verdict comes out:
Planning quality — did you set intent, budget, and a real target before the event, so there was a standard to hold it to? This is what stops “winging it” from ever producing a high score.
Forecast accuracy — how close did what you predicted land to what actually happened? Discipline between the forecast and the actuals, shown as context alongside the score.
Proof — what the event actually produced, captured as evidence rather than vibes. Dott calls this Proof of Effort, and it applies whether you attended or hosted.
The verdict — those layers resolve into one 0–100 Dott Score. It leans deliberately toward what actually happened over what was planned — proof outweighs the plan — because an event is judged on delivery, not on how good the brief looked.
We're not coy about the shape of it: the score blends planning and proof at roughly 40/60 in favor of proof. A score you can audit is worth more than one you have to trust.
Why one universal ROI number is the wrong tool
Here's the stance that makes Dott's scoring different: two events with different purposes should not be graded on the same curve.
A pipeline event lives or dies on evidence — qualified meetings, sourced opportunities, deals you can trace back. A brand event lives on execution and perception — did it land, did the right room see it, was it flawless. Score both on “pipeline generated” and you'll punish the brand play for doing exactly what it was supposed to do. Score both on “how did it feel” and the pipeline event escapes the one question that matters.
So Dott weights the score by the event's intent, chosen before the event runs. There are twelve intents in three families — Growth (pipeline, brand, product, thought leadership), People (relationship, networking, community, retention), and Operational (ecosystem, education, recruitment, fundraising) — and each one shifts which signals the score leans on. An event graded against the thing it was actually for produces a verdict you can trust — and a portfolio of such verdicts produces the only comparison that means anything.
This is why event scoring and event ROI aren't the same question. ROI asks what came back. Scoring asks what came back relative to what this event was for — and that's the version a portfolio can actually act on.
What it looks like in practice
Illustrative example
Picture a half-year — ten events, roughly $550K planned, spend landing almost exactly on plan. On the surface, a well-run portfolio. Scored, the story flips.
A marketing-engineering hackathon lands a 94 — it put the company at the center of an emerging category. A single speaking slot scores a 95 for a fraction of a booth's cost. Meanwhile a run of intimate exec dinners come in the high 40s and low 50s — each one felt lovely in the room and moved almost nothing measurable.
The budget wasn't too big. It was in the wrong events. That's the insight a pile of disconnected metrics structurally can't surface and event scoring exists to deliver: not did we spend too much, but did we spend it in the right places — with a score to prove it.
(Illustrative — not a real client result.)
What a score means
A Dott Score is a 0–100 verdict, and it behaves like a grade: the higher the number, the more the event delivered against what it was for. A score in the 90s is a template — repeat the model. A score in the middle means the breakdown is where the story is: strong plan and thin proof reads differently than the reverse. A low score isn't automatically a bad event — if the proof was never captured, the score is telling you the evidence is missing, not that the event failed. And a planned-but-unrun event doesn't get a score at all: Dott withholds the verdict until there's real proof, so no event ever wears a number it didn't earn.
Key terms
- Event Scoring
- Reducing an event's planning, forecast accuracy, and proof to one comparable 0–100 number, weighted by intent, instead of reading a different ad-hoc metric for every event.
- 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.
- Intent-weighted scoring
- The principle that two events with different purposes shouldn't be graded on the same curve: a pipeline play and a brand play earn their scores from different signals.
- Proof of Effort
- The concrete evidence of what an event actually produced, captured as artifacts rather than vibes — Dott's universal proof standard for both attending and hosting.
Frequently asked questions
How is an event scored?
On one 0–100 scale — the Dott Score — layered from planning quality, forecast accuracy, and proven outcomes, and weighted by the event's intent so a pipeline play and a brand play aren't graded on the same curve. Every event carries one, which is what makes a whole portfolio comparable.
Is a high score just a well-attended event?
No. Attendance is one possible piece of proof, not the score. An event can pack the room and score poorly if it produced nothing measurable against its intent — and a twelve-person dinner can score in the 90s if it did exactly what it was for.
What if we didn't capture much after the event?
Then the score is withheld or low by design — it's reflecting missing proof, not a failed event. The fix is to capture the evidence, not to lower the bar. Dott would rather show no verdict than a fake one.
Does event scoring replace event ROI?
It sharpens it. ROI asks what came back; scoring asks what came back relative to what the event was for, and puts it on a scale you can compare across every event.
Who is this for?
Anyone who owns an events budget and has to prove it was worth it — from a solo field marketer to a twenty-person events function.
The standard
The goal isn't a prettier recap. It's to make one question standard practice: before you run it, what's it for — and after you run it, what did it score? When that's just how serious teams work, event scoring isn't a feature anymore. It's the job.
Dott. is the Event Portfolio Intelligence System. Plan → Forecast → Prove → Score.