> ## Documentation Index
> Fetch the complete documentation index at: https://apidoc.cufinder.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Magnitude buckets

> How we rank signal strength so you can filter ruthlessly.

Not every change carries the same weight. A 2% headcount bump is noise. A 40% jump is a story. Magnitude buckets let you separate the two.

For any signal driven by a quantitative change, CUFinder computes the percentage delta between snapshots and sorts it into one of four buckets:

| Bucket     | Condition                   |
| ---------- | --------------------------- |
| `low`      | 1% ≤ \|delta\_pct\| \< 5%   |
| `moderate` | 5% ≤ \|delta\_pct\| \< 15%  |
| `high`     | 15% ≤ \|delta\_pct\| \< 30% |
| `hyper`    | \|delta\_pct\| ≥ 30%        |

## Why buckets matter

A raw event stream is a firehose. Magnitude buckets turn it into a prioritized queue.

<CardGroup cols={2}>
  <Card title="Filter the noise" icon="filter">
    Ignore every `low` blip and only review `high` and `hyper` events when you are time-constrained.
  </Card>

  <Card title="Scale by company size" icon="building">
    The percentage basis means a single hire at a 10-person company buckets far higher than one hire at a 5,000-person company, exactly as it should.
  </Card>

  <Card title="Rank your queue" icon="list-numbers">
    Sort a day's signals by magnitude to work the strongest events first.
  </Card>

  <Card title="Tune your alerts" icon="bell">
    Set alert thresholds per signal: maybe `hyper` only for headcount, but `moderate` and up for funding.
  </Card>
</CardGroup>

## Categorical and scored signals

Some signals are not percentage-based and are handled differently.

<AccordionGroup>
  <Accordion title="Inherently high-signal events" icon="star">
    Events like `employee_size_band_upgrade`, `first_job_in_function`, and `name_change_drastic` are categorically meaningful and are treated as high-signal regardless of a raw percentage. Crossing a size band, for example, requires sustained net hiring, so it rarely fires on noise.
  </Accordion>

  <Accordion title="Continuous scores" icon="gauge">
    `momentum_score` and `risk_score` are not bucketed events. They are continuous, decaying scores recomputed nightly, designed to be sorted and ranked rather than bucketed. See the [composite signals](/buying-signals/signals/composite-signals).
  </Accordion>
</AccordionGroup>

<Tip>
  A good starting policy: alert on `high` and `hyper` for everything, then widen to `moderate` for the handful of signals that map directly to your buyer.
</Tip>

<Card title="Browse the full signal index" icon="list-details" href="/buying-signals/concepts/signal-index" horizontal>
  Every signal, its category, and what it means, in one table.
</Card>