The Dott Score Methodology

This is the complete method behind the Dott Score — published in full, weights and all, and versioned. Most event scores are a black box: a number with no way to check what's behind it. We think a score you can't inspect isn't a standard. So here is exactly how every event is measured — the components, the weights, the formula, and the rules for when a score is shown at all. If you want to reproduce a Dott Score by hand, this page has what you need.

Version 1.0 · Updated August 12, 2026

What the Dott Score is (and isn't)

What this covers (scope)

This methodology scores external events — the ones you attend or host (conferences, dinners, field events, sponsorships, roadshows). Internal events — kickoffs, offsites, all-hands — are a separate discipline with their own signals (team alignment, not pipeline), and they get their own model when that surface ships. Everything below is the external-event method, version 1.0.

The model at a glance

Dott scores an event across the four phases every event moves through: Plan → Forecast → Prove → Score. Those roll up into a small set of scores:

Every score is decomposable: the headline is always backed by the component breakdown, so you can see exactly which part is strong or weak. The score never asks you to trust an aggregate on faith.

The Dott Score (Combined)

The Combined Score is:

The Pre-Event Score (planning discipline)

The Pre-Event Score turns “did you plan this like an investment” into a number out of 100. It's eight signals, each worth a fixed share:

The same standard applies whether you're a solo operator or a 20-person team. When no team is assigned and your headcount is one or unset, Dott expects exactly one retro — yours — and counts you, the operator, as the assigned team. Nothing is waived; the expectation is re-based to the people who actually exist.

The Post-Event Score (delivery + proof)

The Post-Event Score measures what the event produced, across four components:

What's different about Dott: the weight on each of these four components changes based on the event's intent. A pipeline event and a community event are both scored out of 100, but not on the same priorities. That's the intent-weighted matrix.

Intent weighting: the matrix

Evidence is intent-specific

Generic “proof” is weak proof. So the Evidence component isn't one checklist — each intent has its own short registry of what actually proves success for that kind of event, plus a shared slot for supporting links. A pipeline event proves itself with opportunities and pipeline influenced; an adoption event with activations and integrations built; a community event with the connections and advocates it created. You're scored against the evidence that's relevant to your intent, not a one-size-fits-all list.

When a score is shown (the withhold gate)

A Dott Score is withheld until the event has actually run and produced proof. A planned-but-unrun event shows its Pre-Event Score — never a provisional Dott Score. This is on purpose, and it's one of the most important rules on this page: a low number that really means “we don't have the data yet” is worse than no number, because it reads as “this event was bad.” Dott refuses to blend a missing half into a misleading total. Incomplete is not the same as poor, and the score treats them differently.

Forecast accuracy is calibration, not outcome

Efficiency compares each forecast you made (budget, meetings, outcomes, and so on) to what actually happened, as a proportional accuracy. One deliberate design choice worth stating plainly: beating your forecast still counts as forecast error. If you predicted 10 meetings and got 30, that's a great outcome — and a calibration miss. Efficiency rewards accurate forecasting, not optimism, because a forecast you can trust is worth more to a portfolio than a lucky surprise. It's a measure of how well you predict, held separately from how well you did — which is exactly why it sits next to the Dott Score rather than inside it.

How to read a score (bands)

Dott reports scores as bands, not letter grades — a grade implies a precision a single event's data rarely supports, and a band communicates the honest resolution of the signal. The bands run from a strong, repeatable result down through mixed and below-bar to a missed event, with distinct states for a score that's withheld (no post-event data yet) or incomplete:

How the score resists gaming

An open method invites the obvious question: can't you just game it? The score is built so that gaming it means doing the work it measures. The planning checklist is only 40% of the total; the 60% that decides the headline requires real evidence artifacts and real retro responses you can't fabricate by checking boxes; and the withhold gate means that until the event has actually happened and produced proof, there's no Dott Score to inflate at all. The most you can “game” is a partial planning score on an event that then shows no headline number. In practice, the only way to raise your Dott Score is to run a more disciplined event — which is the point.

What we don't publish (and why)

We publish the method in full. We do not publish the accumulated benchmark data — the distributions that let Dott say “this event scored in the top quartile of pipeline events like it.” That's not obfuscation; it's the difference between the method (a standard, which should be open) and the data (which is earned event by event, and which we'll never fabricate to look bigger than it is). The method is yours to inspect. The comparative baselines are built over time.

Versioning

This methodology is versioned, and it will change. v1.0is dated and public. When we refine a weight, add an intent, or adjust a rule, we publish it as a new version with a short note on what changed and why. That's not a walk-back — it's how an honest standard evolves. A method that never changed would mean we stopped learning; a method that changed quietly would mean you couldn't trust it. This one changes in the open.

A note on what this is for

The Dott Score is decision-support, not a guarantee. It's built to make event investment legible — to help you compare events, defend a budget, and see where to put the next dollar — not to promise an outcome. Use it the way an investor uses a rating: as a rigorous, transparent input to a decision that's still yours to make.

Key terms

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.

Plan · Forecast · Prove · Score

The four-phase loop every event runs through. The first three are discipline; the fourth is the verdict.

Pre-Event Score

The planning half of the Dott Score — a 0–100 measure of planning discipline, taken before the event runs: was there an intent, a hypothesis, a budget, a target, and an owner before the first dollar moved.

Post-Event Score

The proof half of the Dott Score — a 0–100 measure of delivery and evidence after the event: did the retros come in, how thoroughly, how the team rated it, and what concrete proof exists — weighted by the event's intent.

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.

The withhold gate

Dott's rule that no Dott Score is shown until an event has actually run and produced post-event proof. A planned-but-unrun event shows its Pre-Event Score instead — incomplete is not the same as poor.

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.

Frequently asked questions

The standard