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

# Request a rule

> How to ask for a new alert rule, or a change to one that's here.

This catalogue grows through customer conversations. If you want a rule that isn't
here, or a change to one that is, we'd like to hear about it. Coverage on a new
chain counts too: if a rule exists for one network and you need it on another, we
extend it.

<Steps>
  <Step title="Tell us what you need">
    Describe what the rule should detect, the trigger condition, and which accounts
    or assets it applies to. The clearer the use case, the faster we can scope it.
    [Get in touch](https://www.range.org/get-in-touch) or talk to your Range contact.
  </Step>

  <Step title="We scope it">
    We review feasibility and where it fits in the catalogue. The outcome is a
    decision: it goes on the roadmap as **Planned**, needs more detail, or isn't a
    fit.
  </Step>

  <Step title="It ships">
    As the rule is built it moves **Planned → Building → Active**, and the catalogue
    is updated to match.
  </Step>
</Steps>

## What makes a good request

The more of these you can give us, the better (see [Conventions](/alerting/conventions)
for definitions):

* A one-line **Detects** summary in plain language.
* A concrete **trigger condition**.
* The **account types** it applies to.
* Any chains you specifically need it on.