Format brief · source: organizer feed

Veto and pick-ban rate tracker enters beta for analysts

The desk opens a read-only public beta for analysts. The tracker surfaces veto and pick-ban rates from public organizer feeds. The desk does not endorse any third-party tracker that hides its source. The beta is opt-in and the data is sourced from the organizer feed.

Read the veto reading guide Match desk index

What changed

A read-only tracker built on the organizer feed

The tracker surfaces veto and pick-ban rates from public organizer feeds. The tracker is read-only. The desk does not accept user-submitted data. The desk does not infer pick intent from observer UI noise. The desk records what the organizer feed publishes and labels each row with the feed timestamp.

Veto rate

The veto rate is the share of vetoes cast against a map pool entry across a window. The rate is calculated per team, per cycle, per map pool entry. The desk publishes the rate with the feed timestamp and the window size.

Pick-ban rate

The pick-ban rate is the share of picks and bans against a map pool entry across a window. The rate is calculated per team, per cycle, per map pool entry. The desk publishes the rate with the feed timestamp and the window size.

Pool coverage

The pool coverage is the share of map pool entries that appear in the organizer feed. The coverage is calculated per cycle. The desk publishes the coverage with the feed timestamp.

Window size

The window size is the count of public series used to calculate the rate. The desk publishes the window size alongside the rate. A rate with a small window is labelled as such.

Source discipline

Why the desk does not endorse hidden-source trackers

A veto tracker is a useful tool. The desk uses trackers internally and publishes a tracker as a public beta. The desk does not endorse trackers that hide their source class. A tracker that does not name the feed, the window, the cycle or the team is a tracker that the desk cannot verify.

The desk's editorial standard applies to trackers as much as it applies to briefs. A tracker that does not publish its source class is a tracker that does not meet the desk's standard. The desk will not link to such a tracker from the public beta. The desk will not republish any rate that is sourced from such a tracker. The desk's tracker is built on the organizer feed and the team channel. The tracker inherits the desk's source hierarchy.

The tracker is also a presentation layer, not a prediction. The rate does not predict the next veto. The rate describes the prior vetoes. The desk labels the rate with the feed timestamp and the window size. The reader weighs the read against the next public series. The tracker is a starting point for analysis, not an ending point.

The desk will not interpolate or extrapolate the rate. If the organizer feed publishes a veto for a single series, the desk publishes the veto with a window size of one. The desk does not assume the rate will hold across the next cycle. The desk does not assume the rate will hold across the next region. The rate is the rate.

Pool entries

The first beta cycle, by pool entry

Pool entry A

Veto rate published for the active cycle. Window size: twelve series. The rate is labelled with the feed timestamp and the team. The desk does not infer regional fit.

Pool entry B

Pick-ban rate published for the active cycle. Window size: eight series. The rate is labelled with the feed timestamp and the team. The desk does not infer role fit.

Pool entry C

Pool coverage published for the active cycle. Window size: twenty-four series. The coverage is labelled with the feed timestamp. The desk does not infer meta fit.

How analysts use the tracker

Three reads the tracker is built for

The tracker is built for three reads. The team-cycle read, the pool-entry read, and the window-size read. Each read is a verification artefact, not a prediction.

The team-cycle read answers a single question: what did this team veto across this cycle? The desk publishes the rate per pool entry, per cycle. The reader can compare two cycles without re-reading the underlying feed. The team-cycle read is the most common use of the tracker.

The pool-entry read answers a single question: how often was this pool entry picked, banned or vetoed across the active cycle? The desk publishes the rate per team, per pool entry. The reader can compare two teams without re-reading the underlying feed. The pool-entry read is the second most common use.

The window-size read answers a single question: how many public series were used to calculate this rate? The desk publishes the window size alongside the rate. A rate with a small window is labelled as such. The reader should treat a rate with a small window as a snapshot, not a baseline.

What to watch next

Four things to verify before the next beta cycle

01Verify the organizer feed window size against the tracker

02Verify the team-channel confirmations against the tracker

03Verify the pool coverage against the active cycle

04Publish the next beta tracker update

FAQ

Veto tracker beta, plain answers

What is the veto tracker beta?

The veto tracker beta is a read-only public tracker that surfaces veto and pick-ban rates from public organizer feeds. The tracker is opt-in and the data is sourced from the organizer feed.

Does the tracker predict the next veto?

No. The tracker is a verification artefact, not a prediction. The desk labels the rate with the feed timestamp and the window size. The reader weighs the read.

Can the desk endorse a third-party tracker?

No. The desk only endorses trackers that publish their source class, their window size and their feed timestamp. A tracker that hides its source is a tracker that the desk cannot verify.

What happens if the organizer feed is delayed?

The desk publishes a correction as a stand-alone note. The tracker is updated in place with the revised rate. The reader can compare two rates without re-reading the underlying feed.

How analysts should weigh a small-window rate

Three rules for reading a rate with a small window

A rate with a small window is a snapshot. The desk publishes the window size alongside the rate. The reader should treat a rate with a small window as a starting point, not a baseline.

Rule one: do not extrapolate. A rate calculated across four series is a rate across four series. The desk does not infer that the rate will hold across the next cycle. The desk does not infer that the rate will hold across the next region. The rate is the rate.

Rule two: do not interpolate. A rate calculated across four series is not a midpoint between two larger windows. The desk does not infer a smoothed rate. The desk publishes the raw rate with the window size. The reader can decide whether the window size is large enough for the read.

Rule three: do not collapse. A rate that is calculated per team, per cycle, per pool entry is three labels, not one. The desk publishes each label separately. The reader can compare two teams, two cycles or two pool entries without re-reading the underlying feed.

The three rules are not new. The rules are the desk's editorial standard applied to tracker data. A tracker that does not follow the three rules is a tracker that the desk does not endorse. The desk's tracker follows the three rules.

The desk publishes the rules alongside the tracker. The rules are a stand-alone note that lists the three rules, the source hierarchy and the verification windows. The reader can compare two rates without re-reading the underlying rules.

The tracker and the analyst

How the tracker fits an analyst's daily read

An analyst who uses the tracker reads three labels per team per cycle. The veto rate, the pick-ban rate and the pool coverage. The three labels are not collapsed. The analyst can read each label separately. The analyst can compare two teams, two cycles or two pool entries without re-reading the underlying feed.

An analyst who uses the tracker also reads the window size. A rate with a window size of four is a snapshot. A rate with a window size of twelve is a baseline. The desk publishes the window size alongside the rate. The analyst decides whether the window size is large enough for the read.

An analyst who uses the tracker also reads the source class. The veto rate is sourced from the organizer feed. The pick-ban rate is sourced from the organizer feed. The pool coverage is sourced from the organizer feed. The desk does not infer a source class from a third-party tracker.

An analyst who uses the tracker does not need to re-verify the underlying feed. The desk has verified the feed against the team channel. The desk has published the verification timestamp. The analyst can use the verification timestamp to plan the next read.

An analyst who uses the tracker can also publish the read. The desk does not endorse any third-party read that hides its source. The desk publishes its own read with the source class and the verification timestamp. The analyst can compare two reads without re-reading the underlying source.